HP 3PAR Recovery Manager 4.2.0 Software for Microsoft SQL Server User’s Guide Abstract This guide is designed for System Administrators and Microsoft SQL Server Administrators who are responsible for backing up Microsoft SQL Server databases and who understand Microsoft™ Windows™ and Microsoft SQL Server™.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction...............................................................................................6 Related Documents...................................................................................................................6 Typographical Conventions........................................................................................................6 Advisories.....................................................................................................................
5 Configuring Backup Software.....................................................................24 Overview..............................................................................................................................24 Before You Begin....................................................................................................................24 Setting Up Symantec NetBackup...............................................................................................
Viewing Event Message Descriptions.........................................................................................41 7 Using the Recovery Manager CLI................................................................42 Recovery Manager for SQL Server Command Line Interface (CLI)..................................................42 Recovery Manager Commands................................................................................................42 RMSql analyze....................................
1 Introduction Related Documents For Information About… Read the… Using the HP 3PAR InForm OS Command Line Interface HP 3PAR InForm OS CLI Administrator’s Manual (CLI) to configure and manage the HP 3PAR Storage System Using the HP 3PAR InForm Management Console to configure and administer HP 3PAR Storage Systems HP 3PAR InForm Management Console Help Assigning the appropriate user roles and rights HP 3PAR InForm OS Concepts Guide HP 3PAR InForm OS CLI Administrator’s Manual Identifying HP 3PAR Storag
NOTE: The InServ Storage Server has been rebranded as HP 3PAR Storage System. There are instances in this document where screenshots and/or menu items and command output refer to the HP 3PAR Storage System as InServ or InServ Storage Server. Advisories To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment.
2 Overview of Recovery Manager System Requirements Windows Server Requirements Microsoft Windows Server 2003 with SP2 or above, Windows Server 2008, or Windows Server 2008 R2 Windows Server 2003 with SP2 or above x86-based computer: • 1.4 GHz processor • 512+ MB RAM • 2+ GB hard disk space x64-based computer: • 1.4 GHz processor • 512+ MB RAM • 4+ GB hard disk space Windows Server 2008 x86-based computer: • 2 GHz processor • 2+ GB RAM • 40 GB hard disk space x64-based computer: • 1.
• 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: The Japanese OS does not support scheduling virtual copies using Task Scheduler. (In other words, the functionality described in “Automating Tasks” (page 34) is not available in the Japanese OS.) Features Supported • Windows Enterprise Server For detailed OS version support, see the HP 3PAR InForm OS Configuration Matrix. • Microsoft SQL Server For detailed SQL server version support, see the HP 3PAR InForm OS Configuration Matrix.
NOTE: Due to an SQL instance limitation, the recommended maximum number of databases for which you can create snapshot backups at the same time is 35. For more information, see Microsoft KB 943471: http://support.microsoft.
The HP 3PAR VSS Provider Software coordinates between Requestors (backup applications such as Recovery Manager), Writers (applications in windows services such as Microsoft SQL Server) and Providers (components that create the shadow copies). VSS Component VSS Component Description Requestor The requestor is backup software that initiates the creation of the shadow copy.
2. 3. 4. Volume Shadow Copy service communicates with SQL Writer on the Microsoft SQL Server to flush the current log files to disk and suspend any writes to the transaction log files and to the database file. However, HP 3PAR VSS Software allows read-only access so the client can access any data that is already in the SQL Server database. Volume Shadow Copy service communicates with the provider to initiate the shadow copy process for the disk volumes that contain the Microsoft SQL Server data.
HP 3PAR Recovery Manager Software for SQL provides off-host backup and mounting capabilities. These features reduce the impact on the production server and also provide centralized management for the backup and restore functions across all SQL servers. • Backup Server A backup server is the central control point for Recovery Manager. It controls and manages the backup and restore on different SQL servers. • SQL Server The SQL Server can be a standalone or clustered server.
3 Installation and Deinstallation Upgrading to Recovery Manager 4.2.0 for SQL You can upgrade to HP 3PAR Recovery Manager 4.2.0 Software for Microsoft SQL Server from Recovery Manager 3.0.2 for SQL or Recovery Manager 4.1.0 for SQL. Upgrading the Production Server 1. 2. Deinstall 3PAR Recovery Manager for SQL. For more information, see “Deinstalling Recovery Manager” (page 18). Install HP 3PAR Recovery Manager 4.2.0 for SQL. For more information, see “Installing Recovery Manager” (page 16).
Installing Recovery Manager To install HP 3PAR Recovery Manager Software on Windows: CAUTION: Do not install Recovery Manager on a clustered drive. If you do so, Recovery Manager allows you to proceed with the installation, but after the install is complete, the process hangs and evicts the clustered disk. 1. Log on as the system administrator to the Microsoft SQL Server host computer.
13. If you are using a remote desktop session to install Recovery Manager, log off all connected remote sessions after the installation is complete. The newly added environment variables then go into effect. 14. If you are installing Recovery Manager for SQL on a system that also has a Symantec NetBackup service running in the background, restart the NetBackup service after Recovery Manager installation is complete. The environment path is then registered in the NetBackup service.
NOTE: The DataFilePath field is created in the registry database only after you launch the Recovery Manager GUI for the first time. Deinstalling Recovery Manager 1. 2. 3. 4. Log on as the system administrator. Depending on your operating system, do the following: • In Windows 2003, click Start→Control Panel→Add/Remove Programs. • In Windows 2008, click Start→Control Panel→Programs→Programs and Features. Select 3PAR Recovery Manager for Microsoft SQL Server. Click Remove.
4 Configuring Recovery Manager Configuring the SQL Database When you configure the SQL database: • Be sure to use database files and transaction logs created on basic disks using the NTFS file system. Recovery Manger for SQL Server does not support other types of disks. • Maintain a 1:1 relationship between databases and volumes: ◦ Do not add more than one database plus its transaction log files to a volume.
NOTE: The TCP/IP port used by Recovery Manager for SQL must be the same on all servers. Changing a Production Server Port from the Backup Server 1. On the backup server, run the following Recovery Manager CLI command: RMSql portconfig -s -n 2. On the production server, restart the Recovery Manager for SQL service.
HP 3PAR Storage System domain set. This configuration allows you to use just one Recovery Manager backup server to manage all your database servers. • All hosts, users, and virtual volumes, including the backup server, must belong to the same HP 3PAR Virtual Domain. • To mount a virtual copy or media backup to a server that is in a different HP 3PAR Virtual Domain than the domain in which it was created, you must use the Recovery Manager CLI command RMSql mount -ts.
Server name: Enter the server and instance name as follows: • For the default instance, enter the name of your SQL server. For example: Server name: Bottlenosed • For a named instance, enter the name of your SQL server and the name of your SQL instance in the format: \. For example: Server name: Bottlenosed\MSDE_VC Authentication: Windows Authentication 4. Click Connect.
NOTE: The HP 3PAR Storage System source volumes used by Recovery Manager must be base volumes. Recovery Manager cannot use physical copies or virtual copies as source volumes. Formatting Partitions on a New HP 3PAR VLUN When you create HP 3PAR VLUNs for use with SQL Server, you must align the partitions. Windows Server 2003 Before formatting a partition on a new HP 3PAR VLUN, use the Windows diskpart.exe tool to align the starting partition offset.
5 Configuring Backup Software Overview HP 3PAR Recovery Manager Software for Microsoft SQL Server can be used with either Symantec NetBackup or HP Data Protector to back up and restore the virtual copies created by Recovery Manager. If you are using backup software in the backup environment, you must install a backup master or client on the backup server. NOTE: For information about the supported versions of Symantec NetBackup and HP Data Protector, see the latest HP 3PAR InForm OS Configuration Matrix.
NOTE: If the backup server is running the NetBackup client interface, NetBackup cannot validate the policy. NOTE: If you add the NetBackup path to the system’s PATH environment variable after you install HP 3PAR Recovery Manager Software for Microsoft SQL Server, you must restart Recovery Manager for your changes to take effect. Configuring HP Data Protector Requirements • HP Data Protector Software 6.
For more information on installing HP Data Protector, see HP Data Protector documentation. Using Your Backup Software • The default mount point for virtual copy backups is: :\3parSnapshot • You must manually synchronize backups. If a backup expires in your backup software, you must manually remove the backup from Recovery Manager. If you remove a valid backup from Recovery Manager, you must manually remove it from your backup software. • Recovery Manager does not track restore progress.
6 Using the Recovery Manager GUI Overview of the Recovery Manager GUI HP 3PAR Recovery Manager Software for SQL Server provides a Graphical User Interface (GUI) for managing SQL servers. The Recovery Manager GUI enables you to create, remove, mount, unmount, back up, and restore a virtual copy of an individual database or an entire instance (i.e., all databases within an instance).
1. Right-click the MS SQL Server node and select Register Server. NOTE: If your backup server and SQL production servers reside on different networks, the Recovery Manager for SQL Server Register window might not display all of the available SQL servers. In addition, the displayed list of SQL servers can vary depending on factors such as network traffic, timeouts, routers, lost broadcasted packets, and other network issues. 2.
Unregistering a SQL Server Instance To remove a server instance from the list of registered servers: 1. Right-click the MS SQL Server node. 2. Select Register Server. 3. Uncheck the Register checkbox for the server instance you are deleting. 4. Click OK. Setting the Recovery Manager Policy Recovery Manager applies policy settings at the instance level; therefore, each instance can have its own policy. In addition, you can configure individual virtual copies with their own policy settings.
Retention Time Restrictions If you have a Virtual Lock license, you can set a retention time for virtual copies. The instance or database and the associated virtual copies created within the retention period cannot be removed during the retention period. When setting a retention time, keep in mind the following restrictions: • You must have a Virtual Lock license to set retention times. • The minimum retention time is 1 hour; the maximum is 43,800 hours/1,825 days (5 years).
4. Click Finish. The virtual copy policy is effective immediately for all future virtual copies. NOTE: You can also use the Recovery Manager CLI command RMSql policy to set Recovery Manager policies. For more information, see “Using the Recovery Manager CLI” (page 42). Modifying the Policy for a Virtual Copy To modify the retention time or the expiration time or both for a virtual copy: 1. In the node tree pane, right-click the virtual copy you want to modify, and select Edit Time Constraints. 2.
5. In the Operations pane, check the desired checkboxes in the tab for each type of task (Create Virtual Copy, Backup, and/or Restore) for which you want emails: • Info - Recovery Manager sends informational emails for successful operations. • Error - Recovery Manager sends informational emails for operations that were not completed successfully. Both informational and error emails contain the result of the operation and the related CLI output. 6. Click Finish.
2. Optional: To adjust policy values for this virtual copy (or, if you are scheduling automatic copies, this group of virtual copies): • To adjust the expiration time, check the Expiration Time checkbox and enter the new expiration time. • To adjust the retention time, check the Retention Time checkbox and enter the new retention time. Valid values are 0 (for no retention time) to 43,800 hours/1,825 days. For more information, see “Setting the Recovery Manager Policy” (page 29). 3.
1. 2. In the node tree pane, right-click the instance or database for which you want to create a virtual copy, and select one of the following: • Create Virtual Copy • Create Remote Virtual Copy Click Next in the Create Virtual Copy dialog box. The Task Scheduler appears. For more information on using the Task Scheduler, see “Scheduling Automated Tasks with Task Scheduler” (page 34).
• Weekly - Schedules automated virtual copies by the day of the week. In the right pane, enter the number of weeks you want to pass between automated copies and check the checkbox for each day of the week on which a virtual copy is to be created. • 7. Monthly - Schedules automated virtual copies by day or date of the specified months. ◦ Day - To schedule copies on a specific date at a specific monthly interval, enter the date (as a number) and the number of months between copies.
NOTE: 4. Recovery Manager does not support mounting a virtual copy to a drive letter. Click OK. Recovery Manager: • Adds the mounted virtual copy to the list view in the informational pane • Displays the server to which the copy is mounted in the Exposure column • Displays the absolute path on which the copy is mounted in the Mount Point column • Displays the icon for the mounted virtual copy in green Unmounting a Virtual Copy 1. 2.
2. 3.
Creating a Backup of a Virtual Copy When you create a backup of one virtual copy, Recovery Manager copies the existing virtual copy, and the backup software backs the copy up to the media using the same timestamp as the original copy. Recovery Manager does not create a new virtual copy for a backup of an individual virtual copy. To create a backup of one virtual copy: 1. In the node tree pane, right-click the instance or database you want to back up and select Backup to Media. 2.
NOTE: If your servers are configured in a shared volume environment such as a Microsoft cluster environment, see the following sections for more information on performing a restore in an MSCS environment: • “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) Alternatively, you can use InForm CLI commands to promote the virtual copy to its parent base volume.
you enter an alternate location, you must enter an alternate name in the Database Name text box. If you leave this text box blank, the clone database is restored to the parent location of the original virtual copy. d. 4. 5. To use the point-of-failure recovery method to restore the database, check the No Recovery checkbox. For more information about completing a point-of-failure recovery, see “Recovering All Data with Point-of-Failure Recovery” (page 69).
3. Click Yes. Depending on whether you are both analyzing and synchronizing the repository or just analyzing the repository, Recovery Manager does the following: • If you opt to automatically synchronize the results, Recovery Manager analyzes the repository, synchronizes the repository and the HP 3PAR Storage System (if necessary), and updates the list of virtual copies under the Virtual Copy Management node in the node tree pane.
7 Using the Recovery Manager CLI Recovery Manager for SQL Server Command Line Interface (CLI) HP 3PAR Recovery Manager Software for Microsoft SQL Server provides a Command Line Interface (CLI). The CLI allows users to manage Recovery Manager functionality using commands rather than the Graphical User Interface (GUI).
RMSql analyze SYNTAX RMSql analyze -s [-sync] [-f] DESCRIPTION The RMSql analyze command validates all virtual copy records by matching virtual copies in the HP 3PAR Storage System against records in the Recovery Manager for SQL repository. If any existing virtual copies in the system are missing from the repository, Recovery Manager for SQL displays them as out-of-sync records.
RMSql backup SYNTAX RMSql backup -s [-i ] [-d ] [-t | -r ] [-ts ][-p -u -M ] [-noemail] [-dl ] DESCRIPTION The RMSql backup command backs up a virtual copy to the specified media. The backup can be an existing virtual copy, or it can be a new virtual copy created by this command. PARAMETERS The following options are supported: -s The SQL server associated with the database.
EXAMPLE The following command performs a backup of virtual copy 020405162103 with the necessary Symantec NetBackup parameters. RMSql backup -s inst1 -d test_db -t 020405162103 -p test -u full -M host1 NOTE: Use quotes ("") when an option value includes spaces. NOTE: During backup, snapshot volumes of the virtual copy are surfaced to the operating system with a default mount point under the :\3parsnapshot directory.
RMSql create SYNTAX RMSql create -s [-rc [-w ]][-i ] [-d ] [-noemail] [-exp
NOTE: -f Retention time restrictions are: • You must have a Virtual Lock license to use the -retain option. • The minimum retention period is 1 hour; the maximum is 43,800 hours/1,825 days (5 years). • The default retention time is 336 hours (14 days). • The retention time cannot exceed the value of the InServ's VVRetentionTimeMax. • You can set a retention time regardless of whether the policy is numeric- or expiration-based.
NOTE: Use quotes ("") when an option value includes spaces. NOTE: HP 3PAR VSS Software waits up to 10 seconds for a virtual copy operation; this interval is not configurable. In most cases, 10 seconds is a sufficient window in which to successfully create a virtual copy. However, in some circumstances under very heavy loads, 10 seconds may not be enough time, and the virtual copy might fail on this attempt. This failure is a VSS framework requirement on Microsoft’s part.
RMSql deletebackup SYNTAX RMSql deletebackup -s [-i ] [-d ] -t DESCRIPTION The RMSql deletebackup command removes the specified backup entry from the Recovery Manager repository only. It does not remove the Symantec NetBackup or HP Data Protector entry, nor does it remove the actual images backed up by the backup process. PARAMETERS The following options are supported: -s SQL server to which the backup belongs. -i Optional.
RMSql display SYNTAX RMSql display -s [-rc ] [-i ] [-d ] [-t ] DESCRIPTION The RMSql display command displays all virtual copies in the server at a local site or remote site. PARAMETERS The following options are supported: -s SQL server associated with the database. -i Optional. The SQL instance associated with the database. If not specified, MSSQLSERVER is used as the default value. -d Optional.
RMSql listbackup SYNTAX RMSql listbackup -s [-i ] [-d ] [-t ] DESCRIPTION The RMSql listbackup command displays all virtual copies being backed up via Symantec NetBackup or HP Data Protector. PARAMETERS The following options are supported: -s SQL server to which the database belongs. -i Optional. SQL server instance to which the database belongs. If not specified, MSSQLSERVER (local) is used as the default.
RMSql mount SYNTAX RMSql mount -s -t [-m ] [-ts ] DESCRIPTION The RMSql mount command mounts a virtual copy created by the RMSql create command. To mount a virtual copy, you must create an available mount point on the NTFS volume before you execute the command. PARAMETERS The following options are supported: -s The SQL server associated with the database. -t The timestamp for the virtual copy to be mounted.
RMSql policy SYNTAX RMSql policy -s [-i ] [-q] [-exp
-retain
NOTE: By default, the Recovery Manager for SQL policy is set to a maximum of 10 virtual copies each for the instance level and the database level. In addition, the option to delete the oldest virtual copy is by default set to ‘No’; therefore, when the virtual copy limit is reached, Recovery Manager for SQL retains the oldest virtual copy.
RMSql portconfig SYNTAX RMSql portconfig [-n ] [-s ] DESCRIPTION After Recovery Manager for SQL is installed, by default the port used for communication between the backup server and production server is 9932. If necessary, you can specify an alternate port. PARAMETERS The following options are supported: -n Optional. The port number. If not specified, 9932 is used as the default. -s Optional. Name of the Windows host on which to change the port.
RMSql remove SYNTAX RMSql remove -s -t DESCRIPTION The RMSql remove command removes a virtual copy from the system and the Recovery Manager repository. The virtual copy must not be mounted; if the virtual copy is mounted, Recovery Manager for SQL does not remove it. PARAMETERS The following options are supported: -s The SQL server to which the database belongs. -t The timestamp of the virtual copy to remove.
RMSql report SYNTAX RMSql report -s -output DESCRIPTION The RMSql report command collects the environmental information from a specified Windows host and creates a report for diagnostic purposes. PARAMETERS The following options are supported: -output Full path to the folder in which to generate the report. -s Name of the Recovery Manager for SQL host.
RMSql repository SYNTAX RMSql repository [-a ] [-r] DESCRIPTION After Recovery Manager for SQL is installed, by default the repository directory is located under the Recovery Manager install directory. To provide the highest level access to the repository, you can change the repository destination to the location of the HP 3PAR virtual volume. PARAMETERS The following options are supported: -a Optional. Alternate location in which to store data.
RMSql restore SYNTAX RMSql restore -s [-i ] [-d ]-t [-ts ] [-M ] [-a ] [-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).
-snap Optional. (Volume Restore only) Promotes the virtual copy back to the base volume for a faster restore. You can only promote a base volume that is exposed to a host. If not specified, the virtual copy is not promoted to the base volume. -noemail Optional. Do not send an email notification even if configured for this operation. If not specified, Recovery Manager sends an email notification of the restore if configured. For more information, see Configuring Email Notifications.
NOTE: 62 Use quotes ("") when an option value includes spaces.
RMSql setvc SYNTAX RMSql setvc -s [-i ] [-d ] -t -exp
NOTE: Retention time restrictions are: • You must have a Virtual Lock license to use the -retain option. • The minimum retention period is 1 hour; the maximum is 43,800 hours/1,825 days (5 years). • The default retention time is 336 hours (14 days). • The retention time cannot exceed the value of the InServ's VVRetentionTimeMax. • You can set a retention time regardless of whether the policy is numeric- or expiration-based.
RMSql timeconfig SYNTAX RMSql timeconfig [-s ] [-prt ][-bkt ] [-ai ] DESCRIPTION After you install Recovery Manager for SQL, by default the wait time for snap volume restore is 30 seconds, the wait time for backup is 5 minutes, and the wait time for analysis of the repository with the HP 3PAR Storage System is 60 minutes. You can use this command to change these values. PARAMETERS -prt Optional.
RMSql unmount SYNTAX RMSql unmount -s -t DESCRIPTION The RMSql unmount command unmounts a currently mounted virtual copy that was mounted by the RMSql mount command. Recovery Manager for SQL can only unmount a virtual copy if its mounted status is not “Available.” PARAMETERS The following options are supported: -s The SQL server to which the database belongs. -t The timestamp of the virtual copy to unmount.
For example: “C:\Program Files\3par\RM\SQL\RMSql.exe” create –i inst01–d test -s SQLserver 15. On the Schedule tab, further refine the scheduled task by selecting the frequency and start time of the task. 16. Click Apply and OK when finished. Result: Virtual copies are created as you have scheduled.
8 Recovery for Microsoft SQL Server Microsoft SQL Server Recovery Models Microsoft SQL Server offers three disaster-recovery models: • Simple Recovery Model - The Simple Recovery model enables you to restore a database to the point at which a virtual copy or backup was created; it does not enable you to restore a database to a specific point in time. Therefore, any data modifications made between the time of the most recent backup and the time of the failure are lost.
1. 2. Schedule downtime before performing the restore. 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.
NOTE: Point-of-failure recovery only supports a file copy restore at the database level. Determining Whether You Can Perform a Point-of-Failure Recovery You can perform a point-of-failure recovery, in which a database is completely recovered up to the point of the failure, if the following are all true: • You have performed a full backup of the SQL database. • You have subsequently used the SQL backup utility to perform one or more transaction log backups.
3. To apply the transaction logs as well as to recover the database to the point in time desired, enter the following restore commands at the command prompt: a. Enter the following command for the first to the penultimate backed-up transaction logs in the sequence: RESTORE log database name from transaction log backup media with norecovery; The database is still in “no recovery” mode. You can now apply the backed-up transaction logs to update the database to the point of failure. b.
9 Remote Copy for Recovery Manager Overview HP 3PAR Remote Copy Software helps you safeguard against disasters that might occur at one location by allowing you to keep copies of data on a separate server, which can be placed at a remote location. For example, if there were a fire or earthquake at one location, all of the data stored there could be lost unless a backup copy can be recovered from a separate location not affected by the disaster.
NOTE: For the Recovery Manager GUI to manage virtual copies on the Remote Copy backup server, you must configure Recovery Manager with the precise server and instance names for the supported SQL servers. For more information, see “Configuring Recovery Manager” (page 19). Setting Up Remote Copy 1. Install and configure Remote Copy. For more information, see the HP 3PAR Remote Copy Software User’s Guide.
Support for Remote Copy Modes and Policies Recovery Manager supports Remote Copy in synchronous and asynchronous periodic mode. • If you are using synchronous Remote Copy, the policies on the production system (the Remote Copy primary system) and the Remote Copy backup system must match. If the policies do not match, Recovery Manager cannot create virtual copies on a synchronous Remote Copy system.
Setting Up a Remote Copy Volume Group for Instances 1. 2. 3. Identify the virtual volumes that contain all database(s) and log files to be copied. Create one primary Remote Copy volume group for this instance. Add all virtual volumes that belong to this instance (all database and log files) to the primary Remote Copy volume group, and add the associated secondary virtual volumes to the secondary volume group on the Remote Copy backup server.
A Server Virtualization Environments VMWare and Egenera VMWare and Egenera environments are supported under specific conditions. For VMWare and Egenera support in a virtualization environment, the setup must meet the following requirements: • The disks presented to the SQL servers must be raw devices. • The backup server must be connected directly to the HP 3PAR Storage System. The backup server cannot be connected to the HP 3PAR Storage System through VMWare or Egenera.
B Troubleshooting This appendix is designed to be used like a Frequently Asked Questions section. It will help you find solutions to some of the common issues that might arise when running HP 3PAR Recovery Manager Software for Microsoft SQL Server. Problem: Recovery Manager displays error message “VSS_E_PROVIDER_VETO.” Suggestion: Check the application event log and VSS provider log from the production server.
If you install Recovery Manager via a remote desktop session, the newly added environment variables do not go into effect until you log out of the session. (If Recovery Manager is installed directly from the system console, these variables should be available immediately.) Problem: Symantec NetBackup takes a substantial amount of time to complete a backup process. Suggestion: Make sure you have the latest maintenance package installed for your NetBackup application.
C Event Messages This appendix provides information for the event messages generated by HP 3PAR Recovery Manager Software for Microsoft SQL Server. Table 3 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages Event ID Event Message Description/Action 5312 RMS5312: ERROR: Some of your volumes Some of the target volumes are not HP 3PAR virtual volumes. are either non-3PAR volumes or All of the drives need to be HP 3PAR drives. unsupported types of disk drives.
Table 3 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued) Event ID Event Message Description/Action 5325 RMS5325: ERROR: The virtual copy timestamp does not exist for the snapshotset ID. When you created the virtual copy, Recovery Manager could not store the virtual copy timestamp in the repository for the specified snapshotset ID. • Wait a few minutes and then retry the operation. 5326 RMS5326: ERROR: Volume Restore failed.
Table 3 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued) Event ID Event Message Description/Action 5341 RMS5341: ERROR: Could not find the header information in the command output. Failed to parse the header information from the CLI command output. • Verify that you can connect to the required HP 3PAR Storage System from the CLI command window. • Wait a few minutes and try the operation again.
Table 3 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued) Event ID Event Message Description/Action 5372 RMS5372: ERROR: Failed to connect to the NetBackup master server. Recovery Manager could not connect to the NetBackup server. • Ensure that you can connect to the NetBackup master server. • For more details, check the application event log and NetBackup logs on the NetBackup server. 5373 RMS5373: ERROR: No storage units available for use.
Table 3 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued) Event ID Event Message Description/Action 5379 RMS5379: ERROR: Failed to mount virtual Recovery Manager for SQL failed to mount the virtual copy. copy. Please check the application and • Check the application and system event logs for the most system event logs for the most recent error. recent error messages.
Table 3 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued) Event ID Event Message Description/Action 5384 RMS5384: ERROR: Error encountered while running the Data Protector command. Data Protector failed to execute the specified command. • For more details, check the Data Protector logs on the Data Protector Cell Manager server.
