Unregistering a sql server instance, Setting the recovery manager policy, How recovery manager policies work – HP 3PAR Application Software Suite for Microsoft SQL Licenses User Manual

Page 29: Numeric-based policies, Expiration-based policies, Numeric-based policies expiration-based policies

Advertising
background image

Unregistering a SQL Server Instance

To remove a server instance from the list of registered servers:
1.

Right-click the MS SQL Server node.

2.

Select Register Server.

3.

Uncheck the Register checkbox for the server instance you are deleting.

4.

Click OK.

Setting the Recovery Manager Policy

Recovery Manager applies policy settings at the instance level; therefore, each instance can have
its own policy. In addition, you can configure individual virtual copies with their own policy settings.

How Recovery Manager Policies Work

The Recovery Manager policy-setting feature allows you to:

Specify either a numeric-based or expiration-based policy for each instance and database on
a selected SQL server

Specify a retention time during which the instance or database and its virtual copies cannot
be removed (if you have a 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.

Numeric-Based Policies

If you specify a numeric-based policy, you can modify the maximum number of virtual copies
allowed per database and per instance. By default, Recovery Manager allows you to create a
maximum of 10 virtual copies per database and 10 virtual copies per instance.

The numeric-based policy also enables you to set Recovery Manager to automatically remove the
oldest virtual copy for each database and instance, 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.

NOTE:

A virtual copy must be unmounted to be removed. If the oldest virtual copy is mounted,

a new virtual copy is not created until the oldest copy is unmounted.

Expiration-Based Policies

If you choose an expiration-based policy, you can 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 Remote Copy is set up in asynchronous periodic mode, Recovery Manager sets the expiration
time for the remote virtual copy on the Remote Copy 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 Remote Copy
backup server.

For more information, see the HP 3PAR Remote Copy Software User’s Guide.

The expiration-based policy option is only available if your HP 3PAR Storage System is running
HP 3PAR InForm Operating System Software 2.3.1 or above.

Unregistering a SQL Server Instance

29

Advertising