Table of Contents
Advertisement
tsm: ATLANTIC>
verexists=7 verdeleted=2 retextra=30 retonly=60 dest=TAPEPOOL
ANR1530I Backup copy group STANDARD defined in policy domain STANDARD, set
STANDARD, management class TDP_CLASS.
tsm: ATLANTIC>
retver=365 destination=tapepool
ANR1535I Archive copy group STANDARD defined in policy domain STANDARD, set
STANDARD, management class TDP_CLASS.
The following parameters in the backup copygroup should be left as the defaults
because they are not used by the TDP module: FREQUENCY, MODE, and
SERIALIZATION. Make sure to activate the policy set that contains the new
management class you just defined. Example 21-2 activates the policy set
STANDARD in domain STANDARD.
Example 21-2 Activate a policy set
tsm: ATLANTIC>
Do you wish to proceed? (Yes (Y)/No (N)) y
ANR1514I Policy set STANDARD activated in policy domain STANDARD.
If you choose to use a non-default management class, you will need to add an
include statement in the client options file (dsm.opt for Windows, dsm.sys for
UNIX) that is used by the data protection node, as shown in Example 21-3. This
include statement binds the backup objects to the management class you have
defined.
Example 21-3 Include statement in the client options file
include * TDP_CLASS
21.2.2 Defining a new policy domain
Rather than define a separate management class in an existing policy domain,
you can also define a new policy domain where the default management class
has the required settings. This method allows the default management class to
be utilized for the data protection backups. There is no concern over an include
statement not being recognized during the backup process. We recommend
setting up the management class for the data protection clients in this way.
define copygroup STANDARD STANDARD TDP_CLASS type=backup
define copygroup STANDARD STANDARD TDP_CLASS type=archive
activate policyset STANDARD STANDARD
Chapter 21. Data Protection configuration on the server
683
Advertisement
Table of Contents
