HP 3PAR Recovery Manager Software User Manual

Page 50

Advertising
background image

NOTE:

If the servers are configured in a shared volume environment such as a Microsoft cluster

environment, see the following sections for more information on performing a restore in a Failover
Cluster environment:

“Restoring an SQL Instance in an Failover Cluster Environment Using File Copy Restore”
(page 79)

“Restoring a Volume in Failover Cluster Environment Using Volume Restore” (page 79)

Alternatively, you can use CLI commands to promote the virtual copy to its parent base volume.
For more information, see the HP 3PAR Command Line Interface Administrator’s Manual.

TIP:

Volume restore is the fastest method.

NOTE:

Any type of restore operation on the secondary node in Availability Group is not supported.

Restoring an Instance or a Database with Volume Restore

WARNING!

DO NOT perform a volume restore if the base volume to which you are promoting

the virtual copy contains files for other instances or databases.

The volume restore feature promotes the virtual copy to the base volume and overwrites all data
on the volume. If you perform a volume restore on a volume that hosts files for multiple instances
or databases, the operation deletes all data not contained in the promoted virtual copy.

NOTE:

An SQL data restore failure can occur when an SQL server service is explicitly stopped

outside of Recovery Manager Software for Microsoft SQL and the disk path itself is not available
for the system in a standalone setup.

1.

Schedule downtime for the SQL Server service; HP 3PAR Recovery Manager for SQL
automatically stops and starts the SQL Server service during a restore.

2.

Under the Virtual Copy Management node in the node tree pane, right-click the timestamp for
the virtual copy you want to use for the restore, and select Restore Using

→Volume.

3.

To confirm that you want to continue with the restore process, select the Click to continue
checkbox.

4.

Click OK.

The virtual copy completely overwrites the instance or the database. The instance or the
database is now restored.

NOTE:

If the secondary replica node in the Microsoft SQL Server 2012 Availability Group

configuration becomes inaccessible during the restore process, then the user must manually
join the databases back to the Availability Group .

Restoring an Instance or a Database with File Copy Restore

The file copy restore feature enables you to restore a specific instance or a database from a virtual
copy. Unlike the volume restore feature, the file copy restore feature does not overwrite the entire
volume.
1.

Schedule downtime for the SQL Server service; HP 3PAR Recovery Manager for SQL
automatically stops and starts the SQL Server service during a restore.

2.

Under the Virtual Copy Management node in the node tree pane, right-click the timestamp of
the virtual copy you want to use for the restore, and select Restore Using

→File Copy.

NOTE:

The Vendor Restore Method field of the File Copy Restore dialog box automatically

displays Virtual Copy (File Copy).

50

Using the Recovery Manager GUI

Advertising