HP 10400 Application Software Suite for Microsoft SQL Media LTU manual RMSql restore, AltLocation

Page 60

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]

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 re-creates 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.

NOTE: For more information about performing a volume restore in an MSCS environment, see Restoring a Volume in an MSCS Environment Using Volume Restore.

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>

Optional. The database from which to create a virtual

 

copy. If not specified, an instance-level restore is performed

 

by default.

-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.

-M <masterServer>

Optional. (Media Restore only) The Symantec NetBackup

 

master server name. Valid only if the backup software in

 

use is Symantec NetBackup.

 

Optional: If not specified, the current server name is used

 

as the default.

-a <altLocation>

Optional. An alternate location to which to restore the

 

data. If not specified, data is restored to

 

<SystemDrive>:\3parSnapshot by default.

60 Using the Recovery Manager CLI

Image 60
Contents User’s Guide Documentation Contents Configuring Backup Software Using the Recovery Manager GUIUsing the Recovery Manager CLI Recovery for Microsoft SQL ServerRemote Copy for Recovery Manager Troubleshooting Event MessagesIntroduction Related DocumentsTypographical Conventions Advisories Overview of Recovery Manager System RequirementsWindows Server Requirements Additional System RequirementsRecovery Manager Requirements Running Recovery Manager on a Japanese OSFeatures Supported Features Not Supported Microsoft Volume Shadow Copy ServiceSupported VSS Components How HP 3PAR VSS Software Works with Microsoft SQL ServerRecovery Manager Layout Overview of Recovery Manager Installation and Deinstallation Upgrading to Recovery Manager 4.2.0 for SQLPre-Installation Steps Installing Recovery Manager Verifying the Installation Understanding the RegistryDeinstalling Recovery Manager Configuring Recovery Manager Configuring the SQL DatabaseConfiguring Recovery Manager Configuring Recovery Manager Policies Configuring Mount FunctionalityGrouping Volumes into Autonomic Groups Testing SQL Connectivity Volume SetsConfiguring the Host Computer and the HP 3PAR Storage System Troubleshooting SQL ConnectivityFormatting Partitions on a New HP 3PAR Vlun Windows ServerConfiguring Backup Software Setting Up Symantec NetBackupOverview Before You BeginConfiguring HP Data Protector Setting Up the HP Data Protector Backup SpecificationSetting Up HP Data Protector Cell Manager Access RequirementsUsing Your Backup Software Using Symantec NetBackupUsing HP Data Protector RM installation location\log\nbulog\databasetimestamp.logUsing the Recovery Manager GUI Overview of the Recovery Manager GUIOpening the Recovery Manager GUI Closing the Recovery Manager GUIUpdating Registration after Server Modification Setting the Recovery Manager Policy How Recovery Manager Policies WorkUnregistering a SQL Server Instance Setting Recovery Manager Policies Retention Time RestrictionsConfiguring Email Notifications Modifying the Policy for a Virtual CopyDeleting Email Configurations Creating Virtual CopiesHow Virtual Copy Creation Works Manually Creating a Virtual CopyCreating Remote Virtual Copies Scheduling Automatic Virtual CopiesAutomating Tasks Scheduling Automated Tasks with Task SchedulerMounting a Virtual Copy Managing Automated Tasks with Task ManagerManually Creating Backups at the Instance or Database Level Unmounting a Virtual CopyBacking Up a Virtual Copy Scheduling Automatic Backups of an Instance or Database Removing a Backup from the Repository Restoring Instances, Databases, and VolumesCreating a Backup of a Virtual Copy Restoring an Instance or Database with Volume Restore Restoring an Instance or Database with File Copy RestoreRestoring an Instance or Database from a Backup Analyzing and Synchronizing the RepositoryRemoving a Virtual Copy Viewing Event Message DescriptionsUsing the Recovery Manager CLI Recovery Manager for SQL Server Command Line Interface CLIRecovery Manager Commands RMSql analyze RMSql analyze -s SQL server -sync -fSQL Server SyncRMSql backup Example RMSql create RMSql create -s SQLServer -d test RMSql create -s SQLVirtualServer -d testUsing the Recovery Manager CLI RMSql deletebackup RMSql deletebackup -s server1 -d db1 -tRMSql display RMSql display -s server1RMSql listbackup RMSql mount RMSql policy Database virtual copy limitInstance virtual copy limit Retain timehHdD RMSql policy -n 5 -s SQL serverRMSql policy -exp 30d -s SQL server Recovery Manager Commands RMSql portconfig RMSql portconfig -n number -s WindowsHostRMSql portconfig -n RMSql portconfig -n 9999 -s WindowsHostRMSql remove RMSql remove -s SQL server -t timestampRMSql report RMSql report -s WindowsHost -output OutputDirectoryWindowsHost RMSql report -s Grampus -output c\MyReportRMSql repository RMSql repository -a alter location -rRMSql repository -a d\3parvv RMSql restore SystemDrive\3parSnapshot by defaultAltLocation Norecovery RMSql restore -s server1 -d testdb -tRMSql restore -snap -s server1 -d testdb -t SnapUsing the Recovery Manager CLI RMSql setvc RMSql setvc -s server1 -t 020409162103 -exp 2h RMSql setvc -s server1 -t 020409162103 -exp 30dRMSql timeconfig RMSql timeconfigRMSql timeconfig -prt RMSql timeconfig -bktRunning Recovery Manager as a Scheduled Job Scheduling an Automated Task in WindowsRMSql unmount RMSql unmount -s SQL server -t timestampFor example Recovery for Microsoft SQL Server Microsoft SQL Server Recovery ModelsRecovering Data with HP 3PAR Recovery Manager Preparing for the Recovery ProcessRecovering All Data with Point-of-Failure Recovery Performing a Point-of-Failure Recovery Recovering All Data with Point-of-Failure Recovery Remote Copy for Recovery Manager How Remote Copy WorksSetting Up Remote Copy Setting Up Remote Copy Volume Groups Setting Up a Remote Copy Volume Group for DatabasesSupport for Remote Copy Modes and Policies Support for GeoCluster for Microsoft WindowsRecovering a SQL Database from a Remote Copy Backup Server Setting Up a Remote Copy Volume Group for InstancesServer Virtualization Environments VMWare and EgeneraTroubleshooting Installpath\NetBackup\db\ Installpath\NetBackup\db\altnames\No.RestrictionsEvent Messages Event ID Event ID Event ID Event ID Provcfg conn -syncrc Yes