QR Policies

Topics | How To | Related Topics

  This feature/product/platform is on Extended Support in this release. See Deprecated Features, Products, and Platforms for more information.


Deleting QR Policies


The QR Policy associated with a subclient determines how the volumes in that subclient will be snapped and copied to QR Volumes. When creating a QR Policy, a snapshot engine and copy manager are selected.

The QR Policy also includes a built-in retention policy that defines how long QR Volumes will be retained after creation. Stale QR Volumes are automatically deleted (and their resources returned) each time the Data Aging administration job runs on the CommServe. To prevent QR Volumes from being pruned, you can specify an infinite retention policy. To prevent an individual QR Volume from being pruned, you can set the In Use flag on the QR Volume Properties screen. 

note.gif (292 bytes)
  • QR Volumes that are scheduled for incremental updates are never pruned.
  • If you are creating a QR Policy for use with ONTAP SnapVault or OSSV SnapVault, review the respective overview first.
  • Review Recovery Points before creating a QR Policy for use with Recovery Points.

Deleting QR Policies

When a QR policy is deleted, all the QR Volume information associated with the QR policy will be removed from the CommServe database. Therefore, once the QR policy is deleted, the QR Volumes associated with the QR policy cannot be recovered. Note that a QR Policy cannot be deleted if there are any Data Aging or recovery jobs running on this QR Policy.

A QR Policy cannot be deleted if it is associated with a subclient. If you want to delete a QR Policy that is associated with a subclient, then you must do the following:

You may decide to delete a QR policy if:

Back to Top