HP 3PAR Application Software Suite for Microsoft Exchange - Manual (Page 37)

How Recovery Manager Policies Work
The Recovery Manager policy-setting feature allows you to:
•
Specify and configure either a numeric-based or expiration-based policy
•
Specify a retention time during which the mailbox database/storage group and its virtual
copies cannot be removed (if you have an HP 3PAR Virtual Lock license)
NOTE: Modifications you make to an existing policy are not retroactive. Virtual copies created
under a previous policy (whether numeric or expiration-based) retain the policy setting under which
they were created.
In addition, when you switch policy type, the system retains the virtual copies that exist at the time
of the policy change as follows:
•
If you switch from an expiration-based policy to a numeric-based policy, the system does not
remove the expiration dates from the existing virtual copies, and these existing virtual copies
expire according to their set expiration date.
•
If you switch from a numeric-based policy to an expiration-based policy, the system does not
apply expiration values to the existing virtual copies. These existing virtual copies continue to
reside on the system until you manually delete them or manually set an expiration time for
each individual virtual copy.
Numeric-Based Policies
If you specify a numeric-based policy, you can modify the maximum number of virtual copies
allowed per mailbox database/storage group.
•
By default, Recovery Manager allows you to create a maximum of 10 virtual copies per
mailbox database/storage group.
•
The numeric-based policy also enables you to set Recovery Manager to automatically remove
the oldest virtual copy for each mailbox database/storage group, after the maximum limit of
virtual copies is reached, before creating a new virtual copy. If you do not choose to
automatically remove virtual copies when required in order to create a new virtual copy, you
must manually delete old virtual copies before you can create new copies.
•
(for Exchange 2007) If a single backup server is managing active and passive nodes, the
maximum virtual copy count specified in the policy is enforced on a per-node basis. Therefore,
the backup server can contain twice the maximum number of virtual copies.
NOTE: A virtual copy must be unmounted to be removed. If the oldest virtual copy for which
retention time has elapsed is mounted (and the maximum limit has been reached), Recovery
Manager displays an error message and cancels creation of the new virtual copy.
To create a new virtual copy after the maximum limit of virtual copies is reached, you must unmount
the oldest virtual copy.
Expiration-Based Policies
If you choose an expiration-based policy, you can use the Task Manager to set Recovery Manager
to automatically remove virtual copies after a specified period of time has elapsed.
If you specify an expiration time for a remote virtual copy:
•
If HP 3PAR Remote Copy Software is set up in asynchronous periodic mode, Recovery Manager
sets the expiration time for the remote virtual copy on the backup server only, not for the virtual
copy created on the primary server.
•
If Remote Copy is set up in synchronous mode, Recovery Manager sets the expiration time for
both the virtual copy on the primary server and the remote virtual copy on the backup server.
For more information, see the HP 3PAR Remote Copy Software User’s Guide.
Setting the Recovery Manager Policy 37