Administrator's Reference

UPDATE COPYGROUP (Update a Copy Group)

Use the UPDATE COPYGROUP command to update a defined backup or archive copy group.

You can use this command to modify selected parameters for the specified copy group. If you do not explicitly update a parameter, it remains unchanged.

The UPDATE COPYGROUP command will fail if a copy storage pool name is specified 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 for each form is defined separately below.

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 for Updating a Backup Copy Group

>>-UPDate COpygroup--------------------------------------------->
 
   (1)
>-------domainname--setname--classname--STANDARD---------------->
 
>---+------------------+--+---------------------------+--------->
    '-Type--=--Backup--'  '-DESTination--=--poolname--'
 
>---+--------------------------+-------------------------------->
    '-FREQuency--=--freqvalue--'
 
>---+------------------------------+---------------------------->
    '-VERExists--=--+-verevalue-+--'
                    '-NOLimit---'
 
>---+-------------------------------+--------------------------->
    '-VERDeleted--=--+-verdvalue-+--'
                     '-NOLimit---'
 
>---+-----------------------------+----------------------------->
    '-RETExtra--=--+-retevalue-+--'
                   '-NOLimit---'
 
>---+----------------------------+--+------------------------+-->
    '-RETOnly--=--+-retovalue-+--'  '-MODE--=--+-MODified-+--'
                  '-NOLimit---'                '-ABSolute-'
 
>---+-----------------------------------+----------------------><
    '-SERialization--=--+-SHRSTatic--+--'
                        +-STatic-----+
                        +-SHRDYnamic-+
                        '-DYnamic----'

1	You must update at least one copy group attribute in this command.

Parameters for Updating a Backup Copy Group

domainname

Specifies the name of the policy domain in which the copy group is defined. This parameter is required.

setname

Specifies the name of the policy set in which the copy group to be updated is defined. This parameter is required.

classname

Specifies the name of the management class to which the copy group belongs. This parameter is required.

STANDARD

Specifies the name of the copy group. The name of the copy group must be STANDARD.

Type=Backup

Specifies that you want to update a backup copy group. This parameter is optional.

DESTination=poolname

Specifies the name of the primary storage pool in which backup data is to be stored. This parameter is optional. You can only specify one storage pool as the destination for a copy group.

FREQuency=freqvalue

Specifies the minimum number of days that must elapse between successive backups. ADSM does not perform a backup unless the specified number of days has elapsed since the last backup. You can specify a value from 0 to 9999, inclusive.

Backup frequency works in conjunction with the MODE parameter, which is described later.

VERExists=verevalue

Specifies the maximum number of different backup versions to retain for files that currently exist on the client file system. This parameter is optional.

If the maximum number of versions allowed is 5, and backup processing creates a sixth version, ADSM deletes the oldest backup version from server storage. Possible values are:

verevalue: Specifies the number of backup versions to retain for files that currently exist on the client file system. You can specify a value from 1 to 9999, inclusive.
NOLimit: Specifies that you want ADSM to retain all backup versions.

VERDeleted=verdvalue

Specifies the maximum number of backup versions to retain for files that have been deleted from the client file system after being backed up to the server. This parameter is optional. ADSM ignores this parameter if the file still resides on the client node.

If the client file is deleted, during the next backup ADSM changes the active backup version to inactive and erases the oldest versions that are in excess of the number specified by this parameter. The expiration date for the remaining versions is determined by the values specified for the RETEXTRA and RETONLY parameters. Possible values are:

verdvalue: Specifies the number of backup versions to retain for files that have been deleted from the client file system after being backed up to the server. You can specify a value from 0 to 9999, inclusive.
NOLimit: Specifies that you want ADSM to retain all backup versions for files that are deleted from the client file system after being backed up to the server.

RETExtra=retevalue

Specifies how many days ADSM retains a backup version after that version becomes inactive. A version of a file becomes inactive when the client stores a more recent backup version, or when the client deletes the file from the workstation and then runs a full incremental backup. The value of this parameter determines which versions are deleted during inventory expiration processing. This parameter is optional. Possible values are:

retevalue: Specifies the number of days to retain all backup versions other than the active version. You can specify a value from 0 to 9999, inclusive.
NOLimit: Specifies that you want ADSM to retain all backup versions, other than the most recent version, indefinitely (that is, inventory expiration processing does not affect the backup versions). The most recent version of a file that exists on the client workstation is retained indefinitely or until the user deletes the file on the workstation. If the user deletes the file on the workstation, the file is rolled off using the value specified for the VERDELETED parameter.
If the NOLIMIT value is specified, extra backup versions are deleted during backup processing under control of the VEREXISTS or VERDELETED parameters.

RETOnly=retovalue

Specifies the retention time, in days, that ADSM retains the last copy it has of a file that has been deleted from the client file system. This parameter is optional. Possible values are:

retovalue: Specifies the number of days to retain the last remaining inactive copy of a file. You can specify a value from 0 to 9999, inclusive.
NOLimit: Specifies that the last remaining inactive copy of a file be kept indefinitely.

If you specify NOLIMIT, only backup versions are deleted under control of the VEREXISTS or VERDELETED parameters.

MODE=mode

Specifies whether a file should be backed up based on changes made to the file since the last time it was backed up or regardless of whether it has changed. This parameter is only used by incremental backup. This parameter is optional. Possible values are:

MODified

Specifies that the file is backed up only if it has changed since the last backup. A file is considered changed if any of the following is true:

The date last modified is different
The file size is different
The file owner is different
The file permissions are different

ABSolute

Specifies that the file is backed up regardless of whether it has been changed.

SERialization=serialvalue

Specifies whether a file or directory can be in use during a backup operation and what the server should do if it is in use. This parameter is optional.

Attention: Be careful about choosing a management class that contains a copy group that specifies SERIALIZATION=SHRDYNAMIC or SERIALIZATION=DYNAMIC.

If you choose a management class that allows a file to be backed up while it is in use, the backup version stored on the server might be a fuzzy backup. A fuzzy backup is a backup version that may not accurately reflect what is currently in the file. It might contain some, but not all, changes. If that is not acceptable, be sure to choose a management class that allows ADSM to create a backup version only if the file is not being used.

If a file is restored that contains a fuzzy backup, the file might not be usable, depending on the file's application.

Possible values are:

SHRSTatic

Specifies that a file or directory must not be backed up while being modified. The server attempts to perform a backup as many as four times, depending on the value specified for CHANGINGRETRIES specified in the client user options file. If the file or directory is in use during the backup process, the server will not back it up.

STatic

Specifies that a file or directory must not be modified during backup. If the file or directory changes during the backup attempt, it is not backed up.

Platforms that do not support the STATIC option default to SHRSTATIC. The STATIC option is not supported on the DOS platform.

SHRDYnamic

Specifies that if the file or directory is being modified during a backup attempt, the server will back it up on its last try even though the file or directory is in use.

DYnamic

Specifies that a file or directory is backed up on the first attempt by the server, regardless if the file or directory is in use during the backup process.

Syntax for Updating an Archive Copy Group

>>-UPDate COpygroup--------------------------------------------->
 
   (1)
>-------domainname--setname--classname--STANDARD---------------->
 
>---Type--=--Archive---+---------------------------+------------>
                       '-DESTination--=--poolname--'
 
>---+--------------------+--+---------------------------+------->
    '-FREQuency--=--Cmd--'  '-RETVer--=--+-retvvalue-+--'
                                         '-NOLimit---'
 
    .-MODE--=--ABSolute---.
>---+---------------------+------------------------------------->
    '-MODE--=--ABSolute---'
 
>----+-----------------------------------+---------------------><
     '-SERialization--=--+-SHRSTatic--+--'
                         +-STatic-----+
                         +-SHRDYnamic-+
                         '-DYnamic----'

1	You must specify at least one optional parameter on this command.

Parameters for Updating an Archive Copy Group

domainname

Specifies the name of the policy domain in which the copy group is defined. This parameter is required. The maximum length of this name is 30 characters.

setname

Specifies the name of the policy set in which the copy group belongs. This parameter is required. The maximum length of this name is 30 characters.

classname

Specifies the name of the management class to which the copy group belongs. This parameter is required. The maximum length of this name is 30 characters.

STANDARD

Specifies the name of the copy group. The name of the copy group must be STANDARD.

Type=Archive

Specifies that you want to update an archive copy group. This parameter is required.

DESTination=poolname

Specifies the name of the storage pool where the archive files are to reside. This parameter is optional. You can only specify one storage pool as the destination for a copy group.

FREQuency=Cmd

Specifies that a file is archived. The copy frequency must be CMD. This parameter is optional. A file is archived only when specified in an ARCHIVE command or when selected for archive using the graphical user interface.

RETVer=retvvalue

Specifies the number of days to retain an archive copy that is bound to this management class. The value of this parameter determines whether a copy is deleted during inventory expiration processing. This parameter is optional.

retvvalue: Specifies the number of days to retain an archive copy. You can specify a value from 0 to 9999, inclusive.
NOLimit: Specifies that an archive copy is maintained indefinitely (that is, inventory expiration processing does not affect the archive copy).

MODE=ABSolute

Specifies that the file is archived regardless of whether it has been changed since the last archive request. This parameter is optional.

SERialization=serialvalue

Specifies whether a file can be in use during an archive operation and what the server should do if it is in use. This parameter is optional.

Attention: Be careful about choosing a management class that contains a copy group that specifies SERIALIZATION=SHRDYNAMIC or SERIALIZATION=DYNAMIC.

If you choose a management class that allows a file to be archived while it is in use, the archive copy stored on the server might be a fuzzy copy. A fuzzy copy is an archive copy that may not accurately reflect what is currently in the file. It might contain some, but not all, changes. If that is not acceptable, be sure to choose a management class that allows ADSM to create an archive copy only if the file is not being used.

If a file is restored that contains a fuzzy copy, the file might not be usable, depending on the file's application.

Possible values are:

SHRSTatic

Specifies that a file must not be archived while being modified. The server attempts to perform an archive as many as four times, depending on the value specified for CHANGINGRETRIES specified in the client user options file. If the file is in use during the archive process, the server will not archive.

STatic

Specifies that a file must not be modified during archive. If the file changes during the archive attempt, it is not archived.

Platforms that do not support the STATIC option default to SHRSTATIC. The STATIC option is not supported on the DOS platform.

SHRDYnamic

Specifies that if the file is being modified during an archive attempt, the server will archive it on its last try even though the file is in use.

DYnamic

Specifies that a file is archived on the first attempt by the server, regardless if the file is in use during the archive process.

Examples

Task 1

Update an archive copy group named STANDARD in the EMPLOYEE_RECORDS policy domain, VACATION policy set, ACTIVEFILES management class. The archive destination is BACKUPPOOL where the archive copies are kept for 190 days.

Command:: update copygroup employee_records vacation activefiles standard type=archive destination=backuppool retver=190

Task 2

Update a backup copy group named STANDARD in the EMPLOYEE_RECORDS policy domain, VACATION policy set, ACTIVEFILES management class. The backup destination is BACKUPPOOL, with a minimum interval of seven days between backups, regardless of whether the files have been modified. Retain up to two active backup versions.

Command:: update copygroup employee_records vacation activefiles standard type=backup destination=backuppool frequency=7 verexists=2 mode=absolute

Related Commands

Table 225. Commands Related to UPDATE COPYGROUP

Command Description
ASSIGN DEFMGMTCLASS Assigns an existing management class as the default for a specified policy set.
COPY MGMTCLASS Creates a copy of an existing management class.
DEFINE COPYGROUP Defines a copy group for backup or archive processing within a specified management class.
DEFINE MGMTCLASS Defines a management class within the policy domain and policy set specified.
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 one or more management classes.

Command	Description
ASSIGN DEFMGMTCLASS	Assigns an existing management class as the default for a specified policy set.
COPY MGMTCLASS	Creates a copy of an existing management class.
DEFINE COPYGROUP	Defines a copy group for backup or archive processing within a specified management class.
DEFINE MGMTCLASS	Defines a management class within the policy domain and policy set specified.
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 one or more management classes.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]