Defining Policy Domains; Defining Policy Sets; Defining Management Classes - IBM E16RMLL-I - Tivoli Storage Manager Implementation Manual

7.1.1 Defining policy domains

The sample configuration consists of two policy domains: for servers and for
workstations, respectively. The typical nature of the data found on each type of
machine makes this a logical division of resources and follows the administrative
boundaries used by many customers. Example 7-1 defines these policy
domains, using the define policy command.
Example 7-1 Recommended policy domains
tsm: ATLANTIC>
archretention=365
ANR1500I Policy domain SERVER defined.
tsm: ATLANTIC>
backretention=30 archretention=100
ANR1500I Policy domain WORKSTN defined.

7.1.2 Defining policy sets

We recommend defining one policy set for each of the policy domains, as shown
in Example 7-2. We use the define policyset command.
Example 7-2 Defining a policy set per domain
tsm: ATLANTIC>
Nodes"
ANR1510I Policy set SERVER defined in policy domain SERVER.
tsm: ATLANTIC>
Nodes"
ANR1510I Policy set WORKSTN defined in policy domain SERVER.

7.1.3 Defining management classes

We have defined four management classes for each domain in the sample
configuration. These management classes are used to categorize the domain
data:
DATA: This is the default management class for each domain. It is used for
most of the data in the environment.
DIRECTORY: Directory objects are assigned to this class. Binding directories
to a special management class allows us to properly set their expiration rules
and control their final storage repository.
SPECIAL: This management class is used to store files that are being
modified during backup. An application log file could be bound to this
272
IBM Tivoli Storage Manager Implementation Guide
define domain server description="Server Nodes" backretention=100
define domain workstn description="Workstation Nodes"
def policyset server server description="Policy Set for Server
def policyset server workstn description="Policy Set for Workstation