Quick Start
The TSM default policy specifies how TSM manages client files. For
example, it specifies that TSM retains up to two backup versions of any file
that exists on the client (see Installation and Setup Results for details). Two versions may be enough for most
clients. However, if some clients need the last ten versions to be
kept, you can do either of the following:
- Create a new policy domain and assign these clients to that domain
(described in this section).
- Create a new management class within the default policy domain.
Then the include-exclude lists for all the affected clients must be
updated.

| Storing Directly to Tape
Under the default policy, client files are stored directly to disk.
You can also define policies for storing client files directly to tape.
In a copy group, simply name a tape pool as the destination. Note,
however, that if you store directly to tape, the number of available tape
drives limits the number of client nodes that can store data at the same
time.
|
To create a new policy, you can start by copying the policy domain,
STANDARD. This operation also copies the associated policy set,
management class, and copy groups. You then assign clients to the new
domain.
- Copy the default policy domain, STANDARD, to the new policy domain,
NEWDOMAIN.

|
copy domain standard newdomain
|

|
- Select Policy Domains.
- Select STANDARD domain.
- From Operations, select Copy Policy Domain.
- Enter the domain information and Finish.
|
This operation copies the policy domain, and all associated policy sets,
management classes, and copy groups. Within the policy domain named
NEWDOMAIN and the policy set named STANDARD, you have:
- Management class named STANDARD
- Backup copy group named STANDARD
- Archive copy group named STANDARD
For our example, you update only the backup copy group.
- Update the backup copy group by specifying that ten versions of backed up
files are to be kept.

|
update copygroup newdomain standard standard standard -
type=backup verexists=10
|

|
- Expand Policy Domains, Policy Sets, and then
Management Classes.
- Select Backup Copy Groups.
- From Operations, select the desired copy group.
- From Operations, select Update Copy Group.
- Enter the copy group information and Finish.
|
- Validate and activate the STANDARD policy set in NEWDOMAIN.

|
validate policyset newdomain standard
activate policyset newdomain standard
|

|
- Expand Policy Domains and then Policy Sets.
- Select NEWDOMAIN STANDARD policy set.
- From Operations, select Validate Policy Set and then
Finish.
- From Operations, select Activate Policy Set and then
Finish.
|

| The following conditions result in warning messages during
validation:
- A destination storage pool is not a defined storage pool.
- The default management class does not contain a backup or archive copy
group.
- The current ACTIVE policy set names a management class that is not defined
in the policy set being validated.
- The current ACTIVE policy set contains copy groups that are not defined in
the named policy set.
- A management class specifies that a backup version must exist before a
file can be migrated from a client node, but the management class does not
contain a backup copy group.
|
- Assign client nodes to the NEWDOMAIN policy domain by either updating
existing client nodes or registering new nodes. For example, to update
client node mercedes, do either of the following:

|
update node mercedes domain=newdomain
|

|
- Expand Clients.
- Select Client Nodes.
- Select the desired node.
- From Operations, select Update this Node.
- Enter the node information and Finish.
|
TSM will now keep up to ten versions of backed up files for client node
mercedes because it is assigned to the NEWDOMAIN policy
domain.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]