HP 3PAR Recovery Manager Software - Manual (Page 70)

EXAMPLE
The following rescans the SQLserverA with instanceB
HpRmCli Sql rescan -s SQLserverA -i instanceB .
NOTE: In SQL 2012, by default, sysadmin role is not selected for NT account. For HP 3PAR
Recovery Manager for SQL to work, user has to explicitly configure the sysadmin role.
HpRmCli Sql restore
SYNTAX
HpRmCli Sql restore -s <SQL Server> [-i <instance>] [-d <database>] <-t
timestamp> [-ts <target server>] [[-M <masterServer>]|
[-dp]|[-be]][-clonedb <database name>] [-a <altLocation>] [-snap]
[-norecovery] [-f] [-noemail]
NOTE: When performing -pointofFailure option, always use the latest version of a virtual
copy to complete the restoration successfully.
Any type of restore operation on the secondary node in Availability Group is not supported.
DESCRIPTION
You can use the HpRmCli Sql restore command to perform 3 different types of restore:
•
Media Restore - Using an existing backup entry, Recovery Manager for Microsoft SQL Server
issues a restore request to the backup software in use (Symantec NetBackup, HP Data Protector
or Symantec Backup Exec). The image associated with this backup entry is then restored to
the location you specify. If you do not specify an alternate location, data is restored to
SystemDrive:\3parSnapshot
by default.
•
File Copy Restore - Using an existing virtual copy, Recovery Manager for Microsoft SQL Server
mounts the copy, extracts the database files, and copies the files back to their original locations.
Because the files are copied over one by one, File Copy Restore is a relatively slow but reliable
way of restoring data.
•
Volume Restore - Using an existing virtual copy, Recovery Manager for Microsoft SQL Server
removes the existing VLUNs, promotes the virtual copy back to its base volume, and recreates
the VLUNs back to the host. Volume Restore is relatively fast. However, you should not perform
this restore if the base volumes you are promoting contain data from other instances or
databases.
NOTE: For more information about performing an instance-level file copy restore in Failover
Cluster environment, see “Restoring an SQL Instance in an Failover Cluster Environment Using File
Copy Restore” (page 79) .
NOTE: For more information about performing a volume restore in Failover Cluster environment,
see “Restoring a Volume in Failover Cluster Environment Using Volume Restore” (page 79) .
PARAMETERS
The following options are supported:
-s <SQL server> The SQL server to which the database belongs.
-i <SQL instance Optional. The SQL server instance to which the database
belongs. If not specified, MSSQLSERVER is used as the
default.
-d database(s) The database name of database level virtual copy or
multiple databases of a instance level virtual copy.
70 Using the Recovery Manager CLI