HP 10400 Application Software Suite for Microsoft SQL Media LTU manual

Page 69

1.Schedule downtime before performing the restore.

2.If you are performing a restore on a standalone SQL production server in a non-clustered environment:

•If you are performing a file copy or volume restore on an instance: Stop the SQL Server service for the instance, perform a standard file copy restore or volume restore, and start the SQL Server service.

•If you are performing a volume restore on a database: Stop the SQL Server service, perform a standard volume restore, and start the SQL Server service.

•If you are performing a file copy restore on a database: Perform a standard file copy restore. (Do NOT stop and start the SQL Server service.)

For more information about performing a standard restore using the Recovery Manager GUI, see “Using the Recovery Manager GUI” (page 27). For more information about performing a standard restore using the CLI RMSql restore command, see “Using the Recovery Manager CLI” (page 42).

If you are performing the restore in an MSCS (clustered) environment, you must follow the instructions provided in one of the following sections, depending on the type of restore you are performing:

•“Restoring a SQL Instance in an MSCS Environment Using File Copy Restore” (page 69)

•“Restoring a Volume in an MSCS Environment Using Volume Restore” (page 69)

Restoring a SQL Instance in an MSCS Environment Using File Copy Restore

To perform a file copy restore on a SQL instance in an MSCS environment:

1.Schedule downtime. Recovery Manager automatically takes the SQL Server Agent and SQL Instance Service offline.

2.Locate the instance-level virtual copy you want to use to restore the SQL instance.

3.Run the RMSql restore command on this virtual copy. For more information on Recovery Manager CLI commands, see “Using the Recovery Manager CLI” (page 42).

Restoring a Volume in an MSCS Environment Using Volume Restore

To perform a volume restore on a SQL server in an MSCS environment:

1.Schedule downtime. Recovery Manager automatically takes the relevant SQL services offline.

2.Log onto your backup server and perform a volume restore. To perform a volume restore, use either the RMSql restore command or the Recovery Manager GUI.

For more information about performing a restore using the Recovery Manager GUI, see “Using the Recovery Manager GUI” (page 27). For more information about performing a restore using the CLI RMSql restore command, see “Using the Recovery Manager CLI” (page 42).

Recovering All Data with Point-of-Failure Recovery

Point-of-failure recovery is useful if you cannot afford to lose any data in the event of a system failure.

Recovering All Data with Point-of-Failure Recovery 69

Page 68 Page 70
Image 69
Page 68 Page 70
Contents User’s Guide Documentation Contents Using the Recovery Manager GUI Configuring Backup SoftwareRecovery for Microsoft SQL Server Using the Recovery Manager CLIRemote Copy for Recovery Manager Troubleshooting Event MessagesIntroduction Related DocumentsTypographical Conventions Advisories System Requirements Overview of Recovery ManagerWindows Server Requirements Additional System RequirementsRunning Recovery Manager on a Japanese OS Recovery Manager RequirementsFeatures Supported Microsoft Volume Shadow Copy Service Features Not SupportedHow HP 3PAR VSS Software Works with Microsoft SQL Server Supported VSS ComponentsRecovery Manager Layout Overview of Recovery Manager Installation and Deinstallation Upgrading to Recovery Manager 4.2.0 for SQLPre-Installation Steps Installing Recovery Manager Understanding the Registry Verifying the InstallationDeinstalling Recovery Manager Configuring Recovery Manager Configuring the SQL DatabaseConfiguring Recovery Manager Configuring Recovery Manager Policies Configuring Mount FunctionalityGrouping Volumes into Autonomic Groups Volume Sets Testing SQL ConnectivityTroubleshooting SQL Connectivity Configuring the Host Computer and the HP 3PAR Storage SystemWindows Server Formatting Partitions on a New HP 3PAR VlunSetting Up Symantec NetBackup Configuring Backup SoftwareOverview Before You BeginSetting Up the HP Data Protector Backup Specification Configuring HP Data ProtectorSetting Up HP Data Protector Cell Manager Access RequirementsUsing Symantec NetBackup Using Your Backup SoftwareUsing HP Data Protector RM installation location\log\nbulog\databasetimestamp.logOverview of the Recovery Manager GUI Using 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 Retention Time Restrictions Setting Recovery Manager PoliciesModifying the Policy for a Virtual Copy Configuring Email NotificationsCreating Virtual Copies Deleting Email ConfigurationsHow Virtual Copy Creation Works Manually Creating a Virtual CopyScheduling Automatic Virtual Copies Creating Remote Virtual CopiesScheduling Automated Tasks with Task Scheduler Automating TasksManaging Automated Tasks with Task Manager Mounting a Virtual CopyManually 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 File Copy Restore Restoring an Instance or Database with Volume RestoreAnalyzing and Synchronizing the Repository Restoring an Instance or Database from a BackupViewing Event Message Descriptions Removing a Virtual CopyUsing the Recovery Manager CLI Recovery Manager for SQL Server Command Line Interface CLIRecovery Manager Commands RMSql analyze -s SQL server -sync -f RMSql analyzeSQL Server SyncRMSql backup Example RMSql create RMSql create -s SQLVirtualServer -d test RMSql create -s SQLServer -d testUsing the Recovery Manager CLI RMSql deletebackup -s server1 -d db1 -t RMSql deletebackupRMSql display -s server1 RMSql displayRMSql 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 -n number -s WindowsHost RMSql portconfigRMSql portconfig -n RMSql portconfig -n 9999 -s WindowsHostRMSql remove -s SQL server -t timestamp RMSql removeRMSql report -s WindowsHost -output OutputDirectory RMSql reportWindowsHost RMSql report -s Grampus -output c\MyReportRMSql repository RMSql repository -a alter location -rRMSql repository -a d\3parvv RMSql restore SystemDrive\3parSnapshot by defaultAltLocation RMSql restore -s server1 -d testdb -t NorecoveryRMSql restore -snap -s server1 -d testdb -t SnapUsing the Recovery Manager CLI RMSql setvc RMSql setvc -s server1 -t 020409162103 -exp 30d RMSql setvc -s server1 -t 020409162103 -exp 2hRMSql timeconfig RMSql timeconfigRMSql timeconfig -prt RMSql timeconfig -bktScheduling an Automated Task in Windows Running Recovery Manager as a Scheduled JobRMSql unmount RMSql unmount -s SQL server -t timestampFor example Microsoft SQL Server Recovery Models Recovery for Microsoft SQL ServerRecovering 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 How Remote Copy Works Remote Copy for Recovery ManagerSetting Up Remote Copy Setting Up a Remote Copy Volume Group for Databases Setting Up Remote Copy Volume GroupsSupport for Remote Copy Modes and Policies Support for GeoCluster for Microsoft WindowsSetting Up a Remote Copy Volume Group for Instances Recovering a SQL Database from a Remote Copy Backup ServerVMWare and Egenera Server Virtualization EnvironmentsTroubleshooting Installpath\NetBackup\db\altnames\No.Restrictions Installpath\NetBackup\db\Event Messages Event ID Event ID Event ID Event ID Provcfg conn -syncrc Yes
Top Page Image Contents