Tchater maintenant avec le support
Tchattez avec un ingénieur du support

QoreStor 7.5.2 - Command Line Reference Guide

Introduction to the QoreStor Command Line Reference Guide Introducing QoreStor Managing QoreStor
Alerts Commands Authenticate Commands Email_alerts Commands OST RDA SAML sc_manager command Stats Storage Group commands System User Anomaly Detection Bandwidth Throttling
Managing QoreStor Storage Operations
Cloud_tier Connection Container iSCSI NDMP Object_container Object_direct Performance_tier Replication Seed Schedule VTL
Maintaining QoreStor About us

container --update --name <name> [--no_of_drives <1–60>]

Description

Updates the specified container.

Syntax

container --update --name <name>
	[--no_of_drives <1-60>]
	[--cloud_replication <yes|no>] 
       [--veeam_overwrite_protect]
       [--rb_retention_period <7 days to 30 days>]
	[--immutable_file_stat] 
 	[--locked_file_stat]

Where

--name                     Name of the container. Valid values are  [a-z,A-Z,0-9,'-' and '_' for non-VTL containers]  and maximum of 32 characters.
--no_of_drives             Number of Drives (applicable to FC containers only)
--cloud_replication        <yes|no>
--veeam_overwrite_protect  DMA vendor 'veeam' specific control to tune the container behavior, such as protecting its data files(only .vbk and .vib) against mutable file operations like overwrite, truncate, append, and rename.
--immutable_file_stat      Updates immutable file stat
--locked_file_stat        Updates locked file stat.

Result

The FC service will be restarted for this change to take effect, Do you want to continue? (yes/no) [n]? y
Successfully updated Container FC1's number of drives as 32.

NOTE: --veeam_overwrite_protect option enables the CIFS overwrite protection for Veeam forward incrementals that is applicable to only CIFS containers. Once enabled this is irreversible option. To enable this option, recycle-bin should also be enabled because unlinked files are also to be protected.

container --delete --name <name> [--delete_files]

Description

Deletes the files and the existing container on which the files reside in a QoreStor when using the --name option with --delete_files command.

Syntax

container --delete --name <name> [--delete_files]

Where

--name           Name of container.
--delete_files   Deletes the files in the container.

Result

WARNING: All the data in the container acme4 will be deleted!

Do you want to continue? (yes/no) [n]? y
Please enter the administrator password:
Container "default_ost" marked for deletion. Please run "maintenance --filesystem --reclaim_space" to recover the storage space.

NOTE: Be aware that it may take a fair amount of time for the QoreStor file and container deletion processes to complete and update the system status. For details on deleting the files within an OST container, see container --delete_files.

container --marker [--enable <Auto | CommVault | Networker | TSM | ARCserve | HP_DataProtector | Unix_Dump | BridgeHead>] [--disable <Auto | CommVault | Networker | TSM | ARCserve | HP_DataProtector | Unix_Dump | BridgeHead>] --name <name>

Description

Enables or disables a marker type or an automatic marker setting type (Auto) on an existing container in the QoreStor. To enable or disable the automatic marker setting type on an existing container, substitute Auto in place of a specific marker type (for example, Networker in the CLI command.

Syntax

container --marker [--enable <Auto|CommVault|Networker|TSM|ARCserve|HP_DataProtector|Unix_Dump|BridgeHead|TiNa|Acronis>]
	[--disable <Auto|CommVault|Networker|TSM|ARCserve|HP_DataProtector|Unix_Dump|BridgeHead|TiNa|Acronis>]
	--name 		<name>

Where

--enable   	Enable marker of given type.
--disable   	Disable marker of given type.
--name      	Name of container.

Result

Marker updated successfully.

Other Examples

Disables amarker on an existing container in the QoreStor:

container --marker --disable--name acme99
Marker updated successfully.

container --cloud_policy

Description

Cloud policy for a replication primary container.

Syntax

container --cloud_policy [--age_of_file <1 hours to 70 years (in hours)>]
	[--incl_file_ext <file extension list>]
	[--excl_file_ext <file extension list>]
	[--incl_file_regex <file regex pattern>]
	[--excl_file_regex <file regex pattern>]
	[--incl_dir <include directory list>]
	[--excl_dir <exclude directory list>]
	[--stub_excl_dir <exclude directory list>]
	[--stub_excl_file_regex <file regex pattern>]
	[--stub_excl_file_ext <file extension list>]
	[--on_prem_reten_age <1 hours to 70 years (in hours)>]
	[--reset <incl_file_ext|incl_file_regex|excl_file_ext|excl_file_regex|incl_dir|excl_dir|stub_excl_dir|stub_excl_file_ext|stub_excl_file_regex>] 
 	[--enable_locking <[--lock_type <Governance|Compliance>]>]


--name <name>

Where:

--stub_excl_dir          Comma separated list of directories in which files under those directories that should be excluded from stubbing. (Ex: /excl_dir1/,.excl_dir2))
--stub_excl_file_regex   | separated list of regular expressions skips the files to be stubbed.(Ex: .jpg|.gz)
--stub_excl_file_ext     Comma separated list of file extensions of files to be excluded from stubbing.(Ex: .jpg,.gz)
--reset                  reset incl_file_ext, excl_file_ext, incl_dir excl_dir. stub_excl_dir, stub_excl_file_ext or stub_excl_file

For RDA containers to enable cloud lock for a container use:


[--enable_locking <[--lock_type <Governance|Compliance>]>]

For Object Container use:
container --cloud_policy --enable_locking --name <name of Object container>

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation