UPDATE COPYGROUP (Update a defined archive copy group)

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

Read syntax diagramSkip visual syntax diagramUPDate COpygroupdomain_namepolicy_set_nameclass_name STANDARDType=Archive DESTination=pool_nameFREQuency=CmdRETVer=daysNOLimitMODE=ABSoluteRETMin=daysSERialization=SHRSTaticSTaticSHRDYnamicDYnamic

Parameters

domain_name (Required)
Specifies the policy domain to which the copy group belongs.
policy_set_name (Required)
Specifies the policy set to which the copy group belongs. You cannot update a copy group in the ACTIVE policy set.
class_name (Required)
Specifies the management class to which the copy group belongs.
STANDARD
Specifies the copy group, which must be STANDARD. This parameter is optional.
Type=Archive (Required)
Specifies that you want to update an archive copy group. This parameter is required.
DESTination
Specifies the primary storage pool where the server initially stores the archive copy. This parameter is optional. You cannot specify a copy storage pool as the destination.
FREQuency=Cmd
Specifies the copy frequency, which must be CMD. This parameter is optional.
RETVer
Specifies the number of days to keep an archive copy. This parameter is optional. Possible values are:
days
Specifies the number of days to keep an archive copy. You can specify an integer from 0 to 30000.
Tip: To help ensure that your data can be recovered after a malware incident, such as a ransomware attack, specify a value of at least 30 days.
NOLimit
Specifies that you want to keep an archive copy indefinitely.

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.

MODE=ABSolute
Specifies that a file is always archived when the client requests it. The MODE must be ABSOLUTE. This parameter is optional.
RETMin
Specifies the minimum number of days to keep an archive copy after it has been archived. This parameter is optional. The default value is 365.
SERialization
Specifies how the server processes files that are modified during archive. This parameter is optional. Possible values are:
SHRSTatic
Specifies that the server does not archive a file that is being modified. The server attempts to perform an archive as many as four times, depending on the value specified for the CHANGINGRETRIES client option. If the file is modified during the archive attempt, the server does not archive the file.
STatic
Specifies that the server does not archive a file that is being modified. If a file is modified during the archive attempt, the server does not archive the file.

Platforms that do not support the STATIC option default to SHRSTATIC.

SHRDYnamic
Specifies that if the file is being modified during an archive attempt, the server archives the file during its last attempt even though the file is being modified. The server attempts to archive the file as many as four times, depending on the value specified for the CHANGINGRETRIES client option.
DYnamic
Specifies that the server archives a file on the first attempt, regardless of whether the file is being modified during archive processing.
Important: Be careful about using the SHRDYNAMIC and DYNAMIC values. IBM Spectrum Protect uses them to determine if it archives 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, set SERIALIZATION to SHRSTATIC or STATIC so that IBM Spectrum Protect creates an archive copy only if the file is not being modified.
Tip: Be cautious when selecting retention values for primary storage pools that are of type RECLAMATIONTYPE=SNAPLOCK. Volumes in these types of storage pools cannot be deleted until after their retention dates have passed.

Example: Update multiple elements of a copy group

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