HP 10400 Application Software Suite for Microsoft SQL Media LTU Recovery Manager Requirements

Page 9

•Virtual copy (snapshot) space must be available on virtual volumes where the SQL Server database resides.

•To create virtual copies on the base volume, you must associate virtual copy space with the base volume itself. For more information on creating a base volume with virtual copy space, or assigning virtual copy space after the base volume is created, see the HP 3PAR InForm OS Command Line Interface Reference.

NOTE: For platform-specific release levels, refer to the latest HP 3PAR InForm OS Configuration Matrix. To obtain a copy of this documentation, go to http://www.hp.com/go/3par/, navigate to your product page, click Support for your product, and then click Manuals.

Recovery Manager Requirements

•To create virtual copies and perform one-click backup, the Microsoft SQL Server database for which virtual copies are to be created must be online.

•One backup server is required.

•Because Recovery Manager operates through HP 3PAR VSS Software, the database must be online to perform a file copy restore at the database level. To restore a SQL database that is detached, you can either mount a previously created snapshot of this database to the production server and copy over the database files, or you can issue a volume restore at the database level. For more information about restoring volumes, see “Recovery Manager Commands” (page 42).

•Backup and production server(s) must be running the same level OS version and the same version of HP 3PAR Recovery Manager for SQL Software. Recovery Manager does not support cross-platform configurations.

•The same version of the InForm CLI must be installed on both the production and backup servers.

•The SQLServerWriter service must be running.

•Volumes exported to a host must be base volumes; you cannot export snapshot volumes.

Running Recovery Manager on a Japanese OS

CAUTION: To be fully compatible with Recovery Manager, you must use English-language naming conventions in your SQL Server setup (for example, for domain names, instance and database names, path names, and so on).

Recovery Manager does not function correctly when any language other than English is used, even for areas in which SQL Server itself supports Japanese characters.

•SQL Server OS: Windows Server 2008 R2, Japanese OS

•Microsoft SQL Server 2008 R2

•HP 3PAR VSS Provider Software 2.1.0

•HP 3PAR Recovery Manager Software for SQL Server 4.2

•HP 3PAR Storage System 2.3.1 or higher

Recovery Manager Requirements

9

Page 8 Page 10
Image 9
Page 8 Page 10
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