Example: Sample policy objects

Sample policy objects are used to show an example procedure for creating a policy domain with two policy sets.

Figure 1 shows the policies for an engineering department.

The domain contains two policy sets that are named STANDARD and TEST. The administrator activated the policy set that is named STANDARD. When you activate a policy set, the server makes a copy of the policy set and names it ACTIVE. Only one policy set can be active at a time.

The ACTIVE policy set contains two management classes: MCENG and STANDARD. The default management class is STANDARD.

Figure 1. An example of policy objects defined for an engineering department

To create the sample policy, ENGPOLDOM, complete the following steps:

Copy the STANDARD policy domain to the ENGPOLDOM policy domain by entering the following command:
```
copy domain standard engpoldom
```
ENGPOLDOM now contains the standard policy set, management class, backup copy group, and archive copy group.
Update the policy domain ENGPOLDOM with the following changes:
- Extend the backup retention grace period to 90 days
- Extend the archive retention grace period to two years
- Specify an active-data pool that is named engactivedata as the destination for active versions of backup data that belongs to nodes assigned to the domain
Issue the following command:
```
update domain engpoldom description='Engineering Policy Domain'
backretention=90 archretention=730 activedestination=engactivedata
```
To create the TEST policy set in the ENGPOLDOM policy domain, copy the STANDARD policy set and name the new policy set TEST by issuing the following command:
```
copy policyset engpoldom standard test
```

Update the description of the policy set named TEST:

update policyset engpoldom test
description='Policy set for testing'

Define a new management class that is named MCENG by issuing the following command:
```
define mgmtclass engpoldom standard mceng
```

Update the description of the MCENG management class with the UPDATE MGMTCLASS command:

update mgmtclass engpoldom standard mceng
description='Engineering Management Class for Backup and Archive'

Define a backup copy group that belongs to the MCENG management class in the STANDARD policy set belonging to the ENGPOLDOM policy domain that can complete the following tasks:
- Let users back up changed files, regardless of how much time has elapsed since the last backup, by using the default value 0 for the Frequency parameter (frequency parameter not specified)
- Retain up to four inactive backup versions when the original file resides on the user workstation, by using the Versions Data Exists parameter (verexists=5)
- Retain up to four inactive backup versions when the original file is deleted from the user workstation, by using the Versions Data Deleted parameter (verdeleted=4)
- Retain inactive backup versions for no more than 90 days, by using the Retain Extra Versions parameter (retextra=90)
- If there is only one backup version, retain it for 600 days after the original is deleted from the workstation, by using the Retain Only Version parameter (retonly=600)
- Prevent files from being backed up if they are in use, by using the Serialization parameter (serialization=static)
- Store files in the ENGBACK1 storage pool, by using the Destination parameter (destination=engback1)
Issue the following command:
```
define copygroup engpoldom standard mceng standard
destination=engback1 serialization=static
verexists=5 verdeleted=4 retextra=90 retonly=600
```
Define a STANDARD archive copy group to the MCENG management class in the STANDARD policy set belonging to the ENGPOLDOM policy domain that can complete the following tasks:
- Allow users to archive a file if it is not in use (serialization=static)
- Retain the archive copy for 730 days (retver=730)
- Store files in the ENGARCH1 storage pool (destination=engarch1)
Issue the following command:
```
define copygroup engpoldom standard mceng standard
type=archive destination=engarch1 serialization=static
retver=730
```
Assign the STANDARD management class as the default management class for the TEST policy set in the ENGPOLDOM policy domain by issuing the following command:
```
assign defmgmtclass engpoldom standard standard
```
Validate the STANDARD policy set in the ENGPOLDOM policy domain by issuing the following command:
```
validate policyset engpoldom standard
```
Examine any messages that result and correct the problems.
Activate the STANDARD policy set by issuing the following command:
```
activate policyset engpoldom standard
```

After you create and activate a new policy domain, you can assign client nodes in one of two ways:

To assign an existing client node to the new policy domain, use the UPDATE NODE command. For example, to assign client node APPCLIENT1 to the ENGPOLDOM policy domain, issue the following command:
```
update node appclient1 domain=engpoldom
```
To create a new client node and associate it with an existing policy domain, use the REGISTER NODE command. For example, create a node, NEWUSER, and assign it to the ENGPOLDOM policy domain by issuing the following command:
```
register node newuser newuser domain=engpoldom
```