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.
You cannot delete the ACTIVE policy set or objects that are part of that
policy set.
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 come with the server. However, all STANDARD policy objects are restored whenever you reinstall the server. If you reinstall the server after you delete the STANDARD policy objects, the server issues messages during processing of a subsequent DSMSERV AUDITDB command. The messages may include the following statement: "An instance count does not agree with actual data." The DSMSERV AUDITDB command corrects this problem. If necessary, you can later delete the restored STANDARD policy objects.
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 TEST policy set, enter:
delete copygroup engpoldom test mceng type=backup
delete copygroup engpoldom test standard type=backup
delete copygroup engpoldom test mceng type=archive
delete copygroup engpoldom test standard type=archive
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 TEST policy set, enter:
delete mgmtclass engpoldom test mceng
delete mgmtclass engpoldom test 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.
Authorized administrators can delete any policy set other than the ACTIVE policy set. For example, to delete the TEST policy set from the ENGPOLDOM policy domain, enter:
delete policyset engpoldom test
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.
The ACTIVE policy set in a policy domain cannot be deleted. You can replace the contents of the ACTIVE policy set by activating a different policy set. Otherwise, the only way to remove the ACTIVE policy set is to delete the policy domain that contains the policy set.
You can delete a policy domain only if the domain 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. Move any client nodes to another policy domain, or delete the nodes.
For example, to delete the STANDARD policy domain, perform the following steps:
query node * domain=standard
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 and Directories Are Associated with a Management Class.
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.