Policy-Based Management (Policy Domain)

Policy-Based Management:

Policy Management is used to centrally manage the backup-archive client data. Policies are created by the TSM administrator and stored in the database on the TSM server.

Policy Domain –

It is a way to group TSM clients depending how you want to treat their data.

1. Policy domains are a collection of one or more client nodes.

2. Policy domains are a collection of one or more policies.

3. Policy domains are stored in the TSM database.

4. Policy domain names may be from 1 to 30 characters.

5. There is no limit to the number of defined policy domains.

Def Domain domain_name

Policy set  – 

It allows us to group management class and assign one of them as default to policy domain. There are multiple policy set within a policy domain but only one will be active in the domain. Active policy set contains one or more management classes and their associated copy group.

Any changes that are made under policy set, let it be management class or copy group. In order to validate and activate those changes, we use policy set.

1. There can be only one active policy set per policy domain.

2. There may be any number of inactive policy sets.

3. The policy set is stored in the server database.

4. Policy set names may be from 1 to 30 characters.

5. A policy set is a collection of management classes.

6. A policy set contains one default management class.

Def Policy domain_name policy_name

Managemnt Class- 

It acts as a interface b/w client data and copy group.

1. Represents a business requirements policy or service level agreement.

2. Associated with a backup copy group and archive copy group.

3. Default management class does not require a backup copy group or an archive copy group.

4. Management class information is stored in the server database.

5. Management class names may contain 1 to 30 characters.

6. Can contain a backup copy group, an archive copy groups, both copy groups or no copy groups.

Def mgmtclass domain_name policy_name mgmt_name

Copy Group – 

1. Copy groups contain the parameters that control the generation and expiration of backup and archive data.

2. There are two types of copy groups: backup and archive.

3. Each management class can contain up to two copy groups. If there are two copy groups, they will be:
   

4. One for backups

5. One for archives

6. All copy groups are named STANDARD

7. Backup Copy Group – which holds rules for backup data.

8. Archive Copy Group – which holds rules for Archive data.

Back up copy group consist of 4 parameters-:

1. Version exist

2. Retention extra

3. Version delete

4. Retention only

Version exist – Suppose it is 4 It specifies how many version of a file we need to keep.

Retention Extra – Suppose it is 10 Lets us take scenario that version 4 is not getting modified so version 1 will start counting from the day when it became inactive and will we deleted after 10 days.

Version delete – Suppose it is 2 It means how many inactive version of the file we need to keep if in case the main file gets deleted from the client.

TSM makes all the version of the file inactive as soon as the main files gets deleted from the client.

Retention only  –  Suppose it is 40. We are continuing with the same scenario, suppose the main is deleted from client. Then we are left with 2 inactive file. According to “Retention extra” 1st version will be deleted after ten days. But “Retention only” says that for how many days we need to keep last inactive version.

For archive copy group we specify only Ret version parameter

In Case of Backup copy group:

Def Copygroup domain_name policy_name mgmt_name Standard Type=backup destination=Pool Name Version exist =number retention exist =Number Version delete =number Retention Only=number

*EOD

#PolicyDomain #TSMDomain

IBM Tivoli Storage Manager Training

Book Now