Administrator's Guide

Deleting Policy

You cannot delete the ACTIVE policy set or objects that are part of that policy set.

When you delete a policy object, you also delete any objects belonging to it. For example, when you delete a management class, you also delete the copy groups in it.

Task	Required Privilege Class
Delete policy domains	System
Delete any policy sets, management classes, or copy groups	System or unrestricted policy
Delete policy sets, management classes, or copy groups that belong to policy domains over which you have authority	Restricted policy

You can delete the policy objects named STANDARD that ADSM provides. However, all STANDARD policy objects are restored whenever you reinstall the ADSM server. If you reinstall the server after you delete the STANDARD policy objects, ADSM issues messages during processing of a subsequent DSMSERV AUDIT DB command. The messages indicate that "an instance count does not agree with actual data." The DSMSERV AUDIT DB command corrects this problem. If necessary, you can later delete the restored STANDARD policy objects.

Deleting Copy Groups

You can delete a backup or archive copy group that does not belong to a management class in the ACTIVE policy set.

For example, to delete the backup and archive copy groups belonging to the MCENG and STANDARD management classes in the SUMMER policy set, enter:

delete copygroup engpoldom summer mceng type=backup

delete copygroup engpoldom summer standard type=backup

delete copygroup engpoldom summer mceng type=archive

delete copygroup engpoldom summer standard type=archive

Deleting Management Classes

You can delete a management class that does not belong to the ACTIVE policy set.

For example, to delete the MCENG and STANDARD management classes from the SUMMER policy set, enter:

delete mgmtclass engpoldom summer mceng

delete mgmtclass engpoldom summer standard

When you delete a management class from a policy set, the server deletes the management class and all copy groups that belong to the management class in the specified policy domain.

Deleting Policy Sets

Authorized administrators can delete any policy set other than the ACTIVE policy set. For example, to delete the SUMMER policy set from the ENGPOLDOM policy domain, enter:

delete policyset engpoldom summer

When you delete a policy set, the server deletes all management classes and copy groups that belong to the policy set within the specified policy domain.

Deleting Policy Domains

You can delete a policy domain that has no client nodes registered to it. To determine if any client nodes are registered to a policy domain, issue the QUERY DOMAIN or the QUERY NODE command.

For example, to delete the STANDARD policy domain, perform the following steps:

1. Request a list of all client nodes assigned to the STANDARD policy domain by entering:

   query node * domain=standard
   

2. If client nodes are assigned to the policy domain, remove them in either of the following ways:

   • Assign each client to a new policy domain. For example, enter the following commands:

     update node htang domain=engpoldom
     

     update node tomc domain=engpoldom
     

     update node pease domain=engpoldom
     

     If the active policy set in ENGPOLDOM does not have the same management class names as in the active policy set of the STANDARD policy domain, then backup versions of files may be bound to a different management class name, as described in "How Files Are Associated with a Management Class".

   • Delete each node from the STANDARD policy domain.

3. Delete the policy domain by entering:

   delete domain standard
   

When you delete a policy domain, the server deletes the policy domain and all policy sets (including the ACTIVE policy set), management classes, and copy groups that belong to the policy domain.