Use this command to update a backup or archive copy group. To allow clients to use the updated copy group, you must activate the policy set that contains the copy group.
Note: | The UPDATE COPYGROUP command fails if you specify a copy storage pool as a destination. |
The UPDATE COPYGROUP command takes two forms, depending upon whether the update is for a backup copy group or for an archive copy group. The syntax and parameters for each form are defined separately.
Use this command to update a defined backup copy group.
Privilege Class
To issue this command, you must have system privilege, unrestricted policy privilege, or restricted policy privilege for the policy domain to which the copy group belongs.
Syntax
>>-UPDate COpygroup---domain_name--policy_set_name--class_name--> >-----+-----------+---+------------------+----------------------> '-STANDARD--' '-Type--=--Backup--' >-----+---------------------------+---+---------------------+---> '-DESTination--=--pool_name-' '-FREQuency--=--days--' >-----+----------------------------+----------------------------> '-VERExists--=--+-number--+--' '-NOLimit-' >-----+-----------------------------+---------------------------> '-VERDeleted--=--+-number--+--' '-NOLimit-' >-----+---------------------------+-----------------------------> '-RETExtra--=--+-days----+--' '-NOLimit-' >-----+--------------------------+---+------------------------+-> '-RETOnly--=--+-days----+--' '-MODE--=--+-MODified-+--' '-NOLimit-' '-ABSolute-' >-----+-----------------------------------+-------------------->< '-SERialization--=--+-SHRSTatic--+--' +-STatic-----+ +-SHRDYnamic-+ '-DYnamic----'
Parameters
If a backup causes the limit to be exceeded, the server expires the oldest backup version that exists in server storage. Possible values are:
The number of backup versions to retain is controlled by this parameter until versions exceed the retention time specified by the RETEXTRA parameter.
If a user deletes a file from the client file system, the next backup causes the server to change the active backup version of the file to inactive and expire the oldest versions in excess of this number. The expiration date for the remaining versions is determined by the retention time specified by the RETEXTRA or RETONLY parameter. Possible values are:
If you specify NOLIMIT, the server deletes extra backup versions based on the VEREXISTS parameter (when the file still exists on the client file system) or the VERDELETED parameter (when the file no longer exists on the client file system).
If you specify NOLIMIT, the server retains the last remaining backup version forever, unless a user or administrator deletes the file from server storage.
The MODE value is used only for full incremental backup. This value is ignored during partial incremental backup or selective backup.
Platforms that do not support the STATIC option default to SHRSTATIC.
Attention: Be careful about using the SHRDYNAMIC and DYNAMIC values. These values allow the server to back up a file or directory while modifications are occurring. As a result, the backup version might be a fuzzy backup. A fuzzy backup does not accurately reflect what is currently in the file or directory because it contains some, but not all, modifications. If a file that contains a fuzzy backup is restored, the file may or may not be usable, depending on the application that uses the file. If a fuzzy backup is not acceptable, be sure to use a serialization value that allows the server to create a backup version only if the file or directory is not being modified (SHRSTATIC or STATIC).
Examples
Task
Update the backup copy group (STANDARD) in the EMPLOYEE_RECORDS policy domain, VACATION policy set, ACTIVEFILES management class. Change the destination to DISKPOOL, with a minimum interval of seven days between backups, regardless of whether the files have been modified. Retain up to three backup versions while a file still exists on a client file system.
update copygroup employee_records vacation activefiles type=backup destination=diskpool frequency=7 verexists=3 mode=absolute
Use this command to update a defined archive copy group.
Privilege Class
To issue this command, you must have system privilege, unrestricted policy privilege, or restricted policy privilege for the policy domain to which the copy group belongs.
Syntax
>>-UPDate COpygroup---domain_name--policy_set_name--class_name--> >-----+-----------+---Type--=--Archive--------------------------> '-STANDARD--' >-----+---------------------------+---+--------------------+----> '-DESTination--=--pool_name-' '-FREQuency--=--Cmd--' >-----+-------------------------+---+--------------------+------> '-RETVer--=--+-days----+--' '-MODE--=--ABSolute--' '-NOLimit-' >-----+-----------------------------------+-------------------->< '-SERialization--=--+-SHRSTatic--+--' +-STatic-----+ +-SHRDYnamic-+ '-DYnamic----'
Parameters
If you specify NOLIMIT, the server retains archive copies forever, unless a user or administrator deletes the file from server storage.
The value of the RETVER parameter can affect the management class to which the server binds an archived directory. If the client does not use the ARCHMC option, the server binds directories that are archived to the default management class. If the default management class has no archive copy group, the server binds directories that are archived to the management class with the shortest retention period.
Platforms that do not support the STATIC option default to SHRSTATIC.
Attention: Be careful about using the SHRDYNAMIC and DYNAMIC values. These values allow the server to archive a file while modifications are occurring. As a result, the archive copy might be a fuzzy backup. A fuzzy backup does not accurately reflect what is currently in the file because it contains some, but not all, modifications. If a file that contains a fuzzy backup is retrieved, the file may or may not be usable, depending on the application that uses the file. If a fuzzy backup is not acceptable, be sure to use a serialization value that allows the server to create an archive copy only if the file is not being modified (SHRSTATIC or STATIC).
Examples
Task
Update the archive copy group (STANDARD) in the EMPLOYEE_RECORDS policy domain, VACATION policy set, ACTIVEFILES management class. Change the destination to TAPEPOOL. Keep archive copies for 190 days.
update copygroup employee_records vacation activefiles standard type=archive destination=tapepool retver=190
Table 278. Commands Related to UPDATE COPYGROUP
Command | Description |
---|---|
ACTIVATE POLICYSET | Validates and activates a policy set. |
ASSIGN DEFMGMTCLASS | Assigns an existing management class as the default for a specified policy set. |
COPY MGMTCLASS | Creates a copy of a management class. |
DEFINE COPYGROUP | Defines a copy group for backup or archive processing within a specified management class. |
DEFINE MGMTCLASS | Defines a management class. |
DELETE COPYGROUP | Deletes a backup or archive copy group from a policy domain and policy set. |
DELETE MGMTCLASS | Deletes a management class and its copy groups from a policy domain and policy set. |
EXPIRE INVENTORY | Manually starts inventory expiration processing. |
QUERY COPYGROUP | Displays the attributes of an existing copy group. |
QUERY MGMTCLASS | Displays information about management classes. |