HP 3PAR Recovery Manager Software for Microsoft SQL Server Licenses - Manual (Page 57)

EXAMPLE
The following registers the SQLserverA with instanceB RMSql rescan -s SQLserverA -i
instanceB
.
RMSql restore
SYNTAX
RMSql restore -s <SQL server> [-i <instance>] [-d <database>]-t
<timestamp> [-ts <target server>] [-M <masterServer>] [-a <altLocation>]
[-snap] [-noemail] [-norecovery] [-clonedb] [-dp] [-pointofFailure]
NOTE: When performing -pointofFailure option, always use the latest version of a virtual
copy to complete the restoration successfully.
DESCRIPTION
You can use the RMSql 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 or HP Data
Protector). 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 an MSCS
environment, see “Restoring a SQL Instance in an MSCS Environment Using File Copy Restore”
(page 66) .
NOTE: For more information about performing a volume restore in an MSCS environment, see
“Restoring a Volume in an MSCS Environment Using Volume Restore” (page 66) .
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.
-t <timestamp> The timestamp for the virtual copy to restore.
-ts <target server> Optional. (Symantec NetBackup Media Restore only) The
target server for the restore request. If not specified, the
current server name is used as the default.
Recovery Manager Commands 57