3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 3PAR, Inc. 4209 Technology Drive Fremont, CA 94538 U.S.A. Part No.
Revision Notice This is the second release of this manual. A complete revision history is provided at the end of this manual. Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein.
PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Table of Contents 1 Introduction 1.1 Audience 1.1 1.2 Related Documents 1.2 1.3 Organization 1.3 1.4 Typographical Conventions 1.4 1.5 Advisories 1.5 2 Overview of Recovery Manager 2.1 Microsoft Volume Shadow Copy Service 2.1 2.2 How VSS Works with Microsoft SQL Server 2.3 2.3 Recovery Manager Layout 2.4 2.4 Supported VSS Components 2.5 2.5 System Requirements 2.6 2.6 Recovery Manager Requirements 2.6 2.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 3.2 Verifying the Installation 3.9 3.3 Deinstalling Recovery Manager 3.9 3.4 Understanding the Registry 3.11 4 Configuring NetBackup for Recovery Manager 4.1 Overview 4.1 4.2 Defining a NetBackup Policy 4.2 5 Configuring Recovery Manager 5.1 Configuring the SQL Database 5.2 5.2 Configuring Recovery Manager 5.2 5.2.1 Installation Location 5.2 5.2.2 Search Path 5.2 5.2.3 Recovery Manager TCP/IP Port 5.2 5.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.7 Creating a Remote Virtual Copy 6.14 6.7.1 Creating a Remote Virtual Copy for an Instance 6.15 6.7.2 Creating a Remote Virtual Copy for a Database 6.15 6.8 Mounting a Virtual Copy 6.17 6.9 Unmounting a Virtual Copy 6.19 6.10 Backing Up a Virtual Copy Using Veritas NetBackup 6.19 6.10.1 Backup at Instance Level 6.20 6.10.2 Backup at Database Level 6.23 6.11 Creating a Backup at the Timestamp Level 6.25 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide RMSql report 7.23 RMSql repository 7.24 RMSql portconfig 7.25 RMSql timeconfig 7.26 7.3 Running Recovery Manager as a Scheduled Job 7.27 8 Recovery for Microsoft SQL Server 8.1 Recovery 8.1 8.1.1 Point-In-Time Recovery 8.2 8.1.2 Point-Of-Failure Recovery 8.3 8.1.3 SQL Instance Level File Copy Restore in an MSCS Environment 8.4 8.1.4 Volume Restore in an MSCS Environment 8.5 9 Remote Copy for Recovery Manager 9.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 1 Introduction In this chapter 1.1 Audience 1.1 1.2 Related Documents 1.2 1.3 Organization 1.3 1.4 Typographical Conventions 1.4 1.5 Advisories 1.5 This guide provides the information you need to install, deinstall and use the 3PAR Recovery Manager 3.0.2 for Microsoft SQL Server on the Microsoft Windows operating system. 1.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 1.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 1.3 Organization This guide is organized as follows: ■ This chapter provides an overview of this guide, including intended audience, related documentation, typographical conventions, and advisories. ■ Chapter 2, Overview of Recovery Manager, provides an overview of virtual copies and how Recovery Manager interacts with Microsoft SQL Server.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 1.4 Typographical Conventions The following typographical conventions are used in this guide: Typeface Meaning Example ABCDabcd Used for dialog box Enter your system name in the elements such as titles and Value box and click OK. button labels. ABCDabcd Used for file names, paths, and screen output, and for Found < 12 > 73G disks. Enter cli at the Windows text you are to enter. command prompt.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 1.5 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. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 1.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 2 Overview of Recovery Manager In this chapter 2.1 Microsoft Volume Shadow Copy Service 2.1 2.2 How VSS Works with Microsoft SQL Server 2.3 2.3 Recovery Manager Layout 2.4 2.4 Supported VSS Components 2.5 2.5 System Requirements 2.6 2.6 Recovery Manager Requirements 2.6 2.7 Features Supported 2.7 2.8 Features Not Supported 2.8 2.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide operating system and applications and freezes computing tasks to allow snapshot creation. The freeze function enables an application consistent snapshot to be taken. The shadow copy volume is then used for the actual backup. After the shadow copy volume is saved on the backup device, the shadow copy is deleted.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Figure 2-1. 3PAR VSS Provider for Microsoft Windows Operation Overview 2.2 How VSS Works with Microsoft SQL Server 1 The requestor (Recovery Manager) sends a command to the Volume Shadow Copy service to take a shadow copy of the selected Microsoft SQL Server database. 2 The Volume Shadow Copy service communicates with the Microsoft SQL Server with SQL Writer.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 3 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. VSS communicates with the writers and providers to create a shadow copy. The provider actually creates the shadow copy. 4 The shadow copy typically takes less than a minute.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Recovery Manager 3.0.2 for Microsoft SQL provides off-host backup and mounting capabilities. These features reduce the impact on the production server and also provides the central management for the backup and restore functions across all SQL servers. ■ Backup Server A backup server is the central control point for the Recovery Manager which controls and manages the backup and restore on different SQL servers.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 2.5 System Requirements ■ Microsoft Windows Server 2003 with SP2 or above, or Windows Server 2008. ■ Microsoft SQL Server 2005 with SP2 or above, or Microsoft SQL Server 2008. ■ SQL Server client utilities need to be installed on the backup server. ■ All SQL instances need to be TCP/IP enabled and in order to create snapshots for named SQL instances, their corresponding SQL Browser Service(s) must be turned on. ■ Microsoft .
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide ■ Backup and Production server(s) must be running the same level OS version, operating mode, and version of 3PAR Recovery Manager for SQL. Cross-platform configurations are not supported. ■ The SQLServerWriter service must be running. ■ Volumes exported to a host must be base volumes, you cannot export snapshot volumes.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide ■ Volumes Analyze. ■ Volume Restore. ■ Supports virtual copy creation of local and remote Microsoft SQL Server. ■ Supports MSCS environment. ■ Provides the Remote Copy feature for the SQL Servers. ■ Supports virtual copy operations on SQL instance and database level. NOTE: Due to an SQL instance limitation, it is recommended that you do not create snapshot backups of more than 35 databases at a time.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide ■ Virtual copy ownership transferring. For example, virtual copies can only be removed by the same user who created them. Virtual copies can only be unmounted by the same user who mounted them. ■ Taking a snapshot of an instance or database residing on dynamic disks. ■ Mounting snapshots to a Windows host that resides in virtual environment. Features Not Supported 3PAR Confidential 2.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 2.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 3 Installation and Deinstallation In this chapter 3.1 Installing Recovery Manager 3.1 3.2 Verifying the Installation 3.9 3.3 Deinstalling Recovery Manager 3.9 3.4 Understanding the Registry 3.11 This chapter describes how to install, verify, and deinstall Recovery Manager. 3.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: If you are installing the application through a remote desktop session, the newly added environment variables will not become effective until you log off all connected remote sessions after the installation is completed. It is recommended that you install the application directly from system console.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6 Click Next. Installing Recovery Manager 3PAR Confidential 3.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 7 3.4 Agree to the license agreement, then click Next.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 8 Select the installation type: ◆ Select the Recovery Manager Backup Server option if this server will be your backup server. With this selection, the Recovery Manager GUI will be installed on this server. You can use the Recovery Manager GUI to manage your SQL production servers. NOTE: The SQL Server client utilities need to be installed on the host where the Recovery Manager Backup Server is installed.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 9 Specify the installation directory for Recovery Manager . NOTE: The Disk Cost button analyzes the amount of available storage space and compares it to the amount required for the Recovery Manager installation. 10 Click Next to confirm the installation destination. 11 Click Close once the installation has completed.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Installing Recovery Manager 3PAR Confidential 3.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 13 After the utility completes, the results are automatically displayed in a Notepad file. 14 Carefully review the information displayed in the Notepad file. Pay special attention to any WARNING or ERROR messages and correct them before running Recovery Manager for SQL. . NOTE: If you are installing Recovery Manager through a Remote Desktop session, log out the session and then log back in after the installation is complete. 3.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 3.2 Verifying the Installation Verify the Recovery Manager installation as follows: 1 2 Log on as the system administrator. Click Start > Control Panel > Add/Remove Programs on Windows 2003 or programs and features on Windows 2008. Result: The Add/Remove Programs window appears on Windows 2003 or programs and features on Windows 2008. 3 Verify Recovery Manager appears under the Currently installed programs column. 3.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 3.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 3.4 Understanding the Registry After Recovery Manager is installed successfully, information is written into the registry database under: HKEY_LOCAL_MACHINE\SOFTWARE\3PAR\VCDBA_SQL CAUTION: DO NOT try to edit the registry key value unless asked by your local service provider for support purposes. Table 3-2. System Registry Values for Recovery Manager Name Value DataFilePath Location of the XML repository.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: The DataFilePath field is created in the registry database only after you launch the Recovery Manager GUI for the first time. 3.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 4 Configuring NetBackup for Recovery Manager In this chapter 4.1 Overview 4.1 4.2 Defining a NetBackup Policy 4.2 This chapter contains instructions for configuring Veritas NetBackup for use with Recovery Manager. 4.1 Overview Recovery Manager can be used with Veritas NetBackup for backup and restore of virtual copies created by Recovery Manager. The following sections describe setting up Veritas NetBackup for use with Recovery Manager.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 4.2 Defining a NetBackup Policy Perform the following steps to set up a NetBackup policy for use with Recovery Manager. 1 Launch the Veritas NetBackup Administration Console from the NetBackup Master Server. Select the policies node in the left pane, right-click and select New Policy... 4.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: A storage unit to store the virtual copy backups should already be set up. See the Veritas NetBackup documentation for setting up a storage unit. 2 Give the policy a name. 3 Click OK. NOTE: Provide a policy name that easily identifies it as a policy for use with Recovery Manager. Result: A dialog box appears. 4 On the Attributes tab: a Select MS-Windows-NT as the policy type.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide d 4.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Result: The Change Schedule Attributes dialog appears. e When the backup server is just running the NBU client interface, select User Backup from the drop-down menu as the type of backup. When the backup server is just running the NBU master interface, select Full Backup from the drop-down menu as the type of backup. f Click OK. Defining a NetBackup Policy 3PAR Confidential 4.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide g Select the “Start Window” tab and activate the all time slot for schedule by selecting “Mon,” “12:00:00AM” as the “Start time” and “Sun,” “12:00:00AM” as the “End time” and make sure “7” days are entered in the Duration selection box. Click OK to activate the schedule: h Select the Clients tab and enter the machine name where the Recovery Manager is installed.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: When the backup server is just running the NBU client interface, the policy validation cannot be done. NOTE: 3PAR recommends that you reboot the system after the NetBackup Installation so that the NBU path gets added to the PATH environment variable. If you do not reboot the system, the backup to the media might end up with Windows API call errors.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 4.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 5 Configuring Recovery Manager In this chapter 5.1 Configuring the SQL Database 5.2 5.2 Configuring Recovery Manager 5.2 5.2.1 Installation Location 5.2 5.2.2 Search Path 5.2 5.2.3 Recovery Manager TCP/IP Port 5.2 5.3 SQL Connectivity Test 5.3 5.3.1 Troubleshooting SQL Connectivity 5.5 5.4 Configuring the Host Computer and the 3PAR InServ Storage Server 5.6 5.5 Formatting Partitions on a New 3PAR VLUNs 5.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 5.1 Configuring the SQL Database Recovery Manger for SQL only supports Microsoft SQL Server database files and transaction logs created on basic disks using the NTFS file system. NOTE: 3PAR recommends that each database, as well as transaction log files, be allocated to separate volumes.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 1 Select an available port that is not being used by any process. The valid TCP/IP port range is from1024 to 65535. 2 Open the port selected in step 1 if the port is not already open. 3 Run the Recovery Manager CLI RMSql portconfig command to set your desired port number. For example: RMSql portconfig -n 9999 changes the port number to 9999. 4 Re-start the Recovery Manager for SQL service from the Windows Service console.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 2 In the Connect to Server window, enter or select the following: Server type: Database Engine Server name: enter the \ Authentication: Windows Authentication For the default instance, enter the name of your SQL server. For example: Server name: For named instance, enter the name of your SQL server and the name of your SQL instance. For example: Server name: \ 3 5.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide If the connection can be made, you can safely ignore the rest of this chapter. However, if the connection cannot be made you must fix your SQL configuration environment. 5.3.1 Troubleshooting SQL Connectivity The system administrator must log onto the SQL production server and check the following: ■ From the SQL production server, launch the SQL Server Management Studio to make sure the connection can be made locally.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 5.4 Configuring the Host Computer and the 3PAR InServ Storage Server See the 3PAR InForm OS Concepts Guide and the 3PAR InForm OS CLI Administrator’s Manual for information about configuring the controller nodes on the InServ Storage Server to communicate with the host computer. NOTE: The InServ Storage Server source volumes used by the Recovery Manager must be base volumes.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6 Using the Recovery Manager GUI In this chapter 6.1 Overview of the Recovery Manager GUI 6.2 6.1.1 Menu Bar 6.3 6.1.2 Node Tree Pane 6.4 6.1.3 Informational Right Pane 6.4 6.2 Opening the Recovery Manager GUI 6.4 6.3 Closing the Recovery Manager GUI 6.4 6.4 Server Registration 6.4 6.5 Setting the Recovery Manager Policy Configuration 6.8 6.6 Creating Instance or Database Virtual Copy 6.11 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.10 Backing Up a Virtual Copy Using Veritas NetBackup 6.19 6.10.1 Backup at Instance Level 6.20 6.10.2 Backup at Database Level 6.23 6.11 Creating a Backup at the Timestamp Level 6.25 6.12 Deleting Backup from the Repository 6.26 6.13 Restoring an Instance or Database from Virtual Copy using Volume Restore 6.26 6.14 Restoring an Instance or Database from Virtual Copy Using File Copy 6.28 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Menu Bar Tool Bar Node Tree Pane Command Log Window Informational Right Pane 6.1.1 Menu Bar The Menu Bar consists of the following menu items: ■ Console menu - allows you to rescan all existing SQL instances, to register a new instance, and to exit the GUI. ■ Actions menu - provides access to virtual copy functionality including: backup, create, mount, policies, remove, restore, refresh, remote copy, and unmount.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.1.2 Node Tree Pane Once the SQL server/instance is registered, the SQL instance’s databases, virtual copies, and backup records are displayed as a nested tree in this pane. For information about registering SQL servers, see Server Registration on page 6.4. 6.1.3 Informational Right Pane When a tree node is selected, its detailed information is displayed as a table the right pane. 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide To register an SQL instance: 1 Right click on MS SQL Server node and select Register Server to bring up the registration window. After selecting Register Server, the Recovery Manager for SQL Server Register window opens. Server Registration 3PAR Confidential 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 2 A list of SQL Servers and their instances is displayed in the Recovery Manager for SQL Server Register window. NOTE: If your backup server and SQL production servers reside on different networks, all of the available SQL servers may or may not be listed. The displayed list of SQL servers may also vary depending on factors such as network traffic, timeouts, routers, broadcasted packets being lost, and other network issues.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide After your SQLServerName\instanceName is entered in the Server Name text field, click on the Add button. The new SQL Server and instance are added as a new entry on the list and automatically selected. Click the Ok button to start the registration. 3 Depending on your network traffic, it may take up to several minutes for the Recovery Manager GUI to register a SQL server instance.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: After a SQL instance is successfully registered, if you alter that instance's configuration (such as creating a new database under that instance), the instance must be rescanned. To rescan the instance, right-click on MS SQL Server and select Rescan Server Configuration. 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide When setting the virtual copy limit, you can also optionally select the Remove the oldest virtual copies checkbox indicating that the oldest virtual copy for each database is automatically removed once the set maximum limit of virtual copies is reached. If the Remove the oldest virtual copies checkbox is unselected, once the set maximum limit is met, a new virtual copy cannot be created until you manually remove the old virtual copy.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide To set Recovery Manager policies: 1 Start the Recovery Manager application (see Opening the Recovery Manager GUI on page 6.4). 2 Select the Instance that is to be configured in the node tree pane. 3 Click on the policy icon that appears on the tool bar. Alternatively, you can right-click on the SQL server and select policy, or select Policy from the Virtual Copy drop-down menu from the menu bar.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.6 Creating Instance or Database Virtual Copy Virtual Copies are created at the instance or database level for Microsoft SQL Server. When Recovery Manager creates a Virtual Copy for an instance, it creates a Virtual Copy of all databases under that instance including the instance's log and system files.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide c Select Create Virtual Copy from the Actions drop-down menu on the menu bar. Once a virtual copy is created, it appears under the Virtual Copy Management node under the relevant instance name (see the following figure). The virtual copy is given a timestamp that is used as its name. Result: A newly created timestamp will be added to Virtual Copy Management->instance tree node in the Node Tree Pane.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 2 Click the database name and the Create Virtual Copy icon appears on the toolbar. You can select to create a virtual copy by: a b Click on the Create Virtual Copy icon on the toolbar. Right-click on the database node and selecting Create Virtual Copy from the pop-up menu. c Select Create Virtual Copy from the Actions drop-down menu on the menu bar.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Result: A newly created timestamp will be added to Virtual Copy Management->instance tree node in the Node Tree Pane. NOTE: Creating a Virtual Copy of an Instance creates a Virtual Copy of all the volumes where all the databases reside. Therefore, it is recommended that only database data files be stored in the volume. 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.7.1 Creating a Remote Virtual Copy for an Instance To create a Remote Virtual Copy for an Instance: 1 Navigate through the node tree view on the left pane and locate the instance for which a Remote Virtual Copy is to be created. 2 Click the instance name and the Create Remote Virtual Copy icon appears on the toolbar. You can create a remote virtual copy as follows: a Click on the Create Remote Virtual Copy icon on the toolbar.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide b Select Create Remote Virtual Copy from the Actions drop-down menu on the menu bar. c Enter the remote backup server name in the Target Server Name field. . NOTE: A Target Server name is required. Target Server is a remote server which is a Recovery Manager backup server with the same version of Recovery Manager for SQL installed. NOTE: Remote Virtual Copy will not be seen on the GUI from Recovery Manager Backup server.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.8 Mounting a Virtual Copy A virtual copy can be mounted at an Instance or Database level. To mount a Virtual Copy under Instance: 1 Click on the timestamp in the left pane tree view, then either: a Right-click on the timestamp name and select Mount … . b Click on the Mount icon in the tool bar. c Select Mount … from the Actions drop-down menu on the menu bar. Result: The select mount point dialog appears.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Result: The virtual copy status (Exposure column) shows Exposed locally and the mount point column shows the absolute path to which the virtual copy was mounted. Result: The icon for the mounted VC turns green. To mount a Virtual Copy under Database: 1 6.18 Click on the timestamp in the left pane node tree view, then either: a Right-click on the timestamp name and select Mount ... b Click on the Mount icon in the tool bar.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: Mounting to the drive letter is not currently supported. 6.9 Unmounting a Virtual Copy A virtual copy can be unmounted at the Instance or database level. To unmount a Virtual Copy: 1 Click on the timestamp in the left pane node tree view, then either: a Right-click on the database name and select Unmount … b Click on the Unmount icon in the tool bar. c Select Unmount … from the Actions drop-down menu on the menu bar.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.10.1 Backup at Instance Level This is a fully automatic backup. It creates a virtual copy for a instance, mounts it, backs it up to the media, unmounts it and removes it automatically. To backup at the instance level: 1 Locate the instance node you want to backup in the left pane node tree, then select Backup to Media. 6.20 a Right-click on the Instance Node and select Backup to Media. b Click on the Backup icon in the tool bar.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Result: The Recovery Manager NBU Configuration dialog box appears: Fill in the Master Server Name, the NBU Policy Name and NBU Full Schedule Name text boxes. The policy and schedule names should match the names of the policy and schedule that were set up for use with Recovery Manager in Chapter 4, Configuring NetBackup for Recovery Manager.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: The Master Server Name, the NBU policy name and NBU Full Schedule Name information will be saved and appear as default values in the next backup and is at the instance level, meaning that each instance can have its own default value set. NOTE: While creating a backup at the instance level, a Virtual Copy will be created automatically and will be mounted prior to, and during the backup.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Result: A newly created timestamp will be added to Backup Management > instance tree node in the Node Tree Pane. 6.10.2 Backup at Database Level This is a fully automatic backup. It creates a virtual copy for a database, mounts it, backs it up to the media, unmounts it and removes it automatically. To backup at the database level: 1 Locate the database node you want to backup in the left pane node tree, then select Backup to Media.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Result: The Recovery Manager NBU Configuration dialog box appears: Fill in the Master Server Name, the NBU Policy Name and NBU Full Schedule Name text boxes. The policy and schedule names should be the names as the policy and schedule that were set up for use with Recovery Manager in Chapter 4, Configuring NetBackup for Recovery Manager.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: The Master Server Name, the NBU policy name and NBU Full Schedule Name information will be saved and appear as default values in the next backup and is at the database level, meaning that each database can have its own default value set. NOTE: While creating a backup at the database level, a Virtual Copy will be created automatically and will be mounted prior to, and during the backup.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Result: Once a backup is started, it appears under the Backup Management node under the relevant instance or database name with a tape icon. The backup is given a timestamp that is used as its name. When backup is done, the tape icon will be replaced by a normal database icon and the backup time stamp will be shown up on the right information pane. 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide a Right-click on the virtual copy timestamp node and select Restore Using->Volume. b Click on the Volume Restore icon in the tool bar. c Select Restore Using->Volume from the Actions drop-down menu on the menu bar. Result: The Restore Instance or Database from Virtual Copy dialog appears.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.14 Restoring an Instance or Database from Virtual Copy Using File Copy NOTE: You can manually set the cluster resource to the maintenance mode, remove LUNs exported to all cluster hosts, and promote the virtual copy to its parent base volume with the InForm CLI commands. For more information, see the 3PAR InForm OS CLI Administrator’s Manual.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Result: The Restore Instance or Database from Virtual Copy dialog appears. NOTE: Virtual Copy (File Copy) will be displayed at Vendor Restore Method. NOTE: When restoring from a virtual copy, it will only restore to the original location. Therefore, the Alternate Location will be disabled. 6.15 Restoring a Virtual Copy Using Veritas NetBackup Once a virtual copy is backed up to media, the Restore menu option is enabled.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide To restore a virtual copy that has been backed up using NetBackup: 1 Locate the backup timestamp node under Backup Management Node you wish to restore in the left pane node tree, then select Restore using one of the following methods: a Right-click on the backup timestamp node under Backup Management Node and select Restore. b Click on the Restore icon in the tool bar. c Select Restore from the Actions drop-down menu on the menu bar.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.16 Removing a Virtual Copy To remove a virtual copy from the InServ Storage Server and the Recovery Manager repository, the virtual copy timestamp must have a status of Available. To remove a virtual copy, use one of the methods described below: 1 Right-click on the virtual copy timestamp node and select Remove. 2 Click on the Remove icon in the toolbar. 3 Select Remove from the Actions drop-down menu on the menu bar.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 7 Using the Recovery Manager CLI In this chapter 7.1 Recovery Manager Command Line Interface (CLI) 7.2 7.2 Recovery Manager Commands 7.3 RMSql backup 7.4 RMSql create 7.6 RMSql deletebackup 7.9 RMSql analyze 7.10 RMSql display 7.11 RMSql mount 7.13 RMSql remove 7.15 RMSql restore 7.16 RMSql unmount 7.19 RMSql policy 7.20 RMSql listbackup 7.22 RMSql report 7.23 RMSql repository 7.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide RMSql portconfig 7.25 RMSql timeconfig 7.26 7.3 Running Recovery Manager as a Scheduled Job 7.27 7.1 Recovery Manager Command Line Interface (CLI) Recovery Manager for Microsoft SQL provides a Command Line Interface (CLI).
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 7.2 Recovery Manager Commands The following commands can be run from the Command Line Interface: ■ RMSql analyze ■ RMSql backup ■ RMSql create ■ RMSql deletebackup ■ RMSql display ■ RMSql mount ■ RMSql remove ■ RMSql report ■ RMSql restore ■ RMSql unmount ■ RMSql policy ■ RMSql listbackup ■ RMSql repository ■ RMSql portconfig ■ RMSql timeconfig Recovery Manager Commands 3PAR Confidential 7.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql backup SYNTAX RMSql backup -s [-i ] [-d ] [-t | -r ] [-ts ] -p -u -M DESCRIPTION The RMSql backup command backups a virtual copy to the specified media. The backup can be made of an existing virtual copy or one that is created through this command.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide EXAMPLE: The following command will perform a backup of virtual copy 020405162103 with the necessary NetBackup parameters. RMSql backup -s inst1 -d test_db -t 020405162103 -p test -u full -M host1 . NOTE: Use quotes ("") where spaces are included. NOTE: During backup, snapshot volumes of the virtual copy will be surfaced to the operating system with a default mount point under the %SystemDrive%\3parsnapshot directory.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql create SYNTAX RMSql create -s [-rc [-w ]] [-i ] [-d ] DESCRIPTION The RMSql create command creates a virtual copy of a SQL database or databases under an instance on the primary host where the SQL server instance is running. The virtual copy can be mounted to a host later for off-host processing.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide RMSql create -s SQLServer -d test The following command will create a snapshot for the database test on Virtual SQL server(SQLVirtualServer) on a cluster. RMSql create -s SQLVirtualServer -d test The following command will create a Remote Copy snapshot for the database test on Virtual SQL server(SQLVirtualServer) on a cluster to a secondary site server SecondaryServer.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: The Instance level operation is only granted if the current user is given the sysadmin server role for security permission in SQL Server. NOTE: Database level operation is only granted if the database owner or user is given sysadmin server role for security permission. 7.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql deletebackup SYNTAX RMSql deletebackup -s [-i ] [-d ] -t DESCRIPTION The RMSql deletebackup command only removes the specified backup entry in the Recovery Manager repository. It does not remove NBU's entry and does not remove the actual images backed up by NBU. PARAMETERS The following options are supported: -s - SQL server to which the backup belongs.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql analyze SYNTAX RMSql analyze -s [-sync] [-f] DESCRIPTION The RMSql analyze command validates all snapshot records by matching virtual volumes in the InServ Storage Server against records in the Recovery Manager repository. If any existing virtual volumes in the InServ are missing from the repository, they are displayed as out-of-sync records.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND 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 - SQL instance associated with the database.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: Use quotes ("") where spaces are included. 7.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql mount SYNTAX RMSql mount -s -t [-m ] [-ts ] DESCRIPTION The RMSql mount command mounts a virtual copy created by the RMSql create command. In order to mount the virtual copy devices, an available mount point must be created on the NTFS volume before the command is executed.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: When mounting in read-write mode, the VDS API is used to make the volume read-writeable. However if there is another operation on the disk and the device is locked, the volume can not be unmounted. If this happens, the following error message is displayed: ERROR: COM call “pVolumeMF->Dismount(TRUE,FALSE)” failed.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql remove SYNTAX RMSql remove -s -t DESCRIPTION The RMSql remove command removes the virtual copy from the InServ Storage Server and the backup XML document. If the virtual copy is mounted, it will not be removed. PARAMETERS The following options are supported: ◆ -s - The SQL server to which the database belongs. ◆ -t - The timestamp for the virtual copy to remove.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql restore SYNTAX RMSql restore -s [-i ] [-d ] -t [-ts ] [-M ] [-a ] [-snap] DESCRIPTION The RMSql restore command can be used to perform 3 different types of restore: ■ Media Restore. Using a backup entry that was previously created, the Recovery Manager issues a restore request to NetBackup.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide -s - SQL server to which the database belongs. Optional: Uses the current server name as the default. -i - SQL server instance to which the database belongs. Optional: Uses MSSQLSERVER as the default if not specified. -d - The database from which to create a virtual copy. Optional: Without the -d parameter, the instance level restore will be performed.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: Use quotes ("") where spaces are included. 7.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql unmount SYNTAX RMSql unmount -s -t DESCRIPTION The RMSql unmount command dismounts a currently mounted virtual copy that was mounted by the RMSql mount command. The virtual copy’s mounted status must not be “Available” before it can be unmounted. PARAMETERS The following options are supported: ◆ -s - The SQL server to which the database belongs.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql policy SYNTAX RMSql policy -s [-q] [-i ] [<-r>] [-n ][-in ] DESCRIPTION The RMSql policy command sets the policy at instance and database level. PARAMETERS The following options are supported: ◆ -s - The SQL server to which the database belongs.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide NOTE: The -r option is used to retain the oldest Virtual Copy when the number of Virtual copies exceeds the limit set by policy. Therefore, no new Virtual Copies will be created when the limit is exceeded and the -r option specified. NOTE: By default, the policy limit is set to 10 virtual copies at both Instance-level and database-level, with the option to delete the oldest virtual copy being set to ‘No.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql listbackup SYNTAX RMSql listbackup -s [-i ] [-d ] [-t ] DESCRIPTION The RMSql listbackup command displays all virtual copies being backed up through the NetBackup. PARAMETERS The following options are supported: ◆ -s - The SQL server to which the database belongs.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND 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 diagnosis purposes. PARAMETERS The following options are supported: ◆ -output - The full path to the folder where the report will be generated.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND 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 availability access to the repository, you can change the repository destination to the location where the 3PAR virtual volume resides.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND 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 - Port number (default is 9932).
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide COMMAND RMSql timeconfig SYNTAX RMSql timeconfig [<-prt promotetime>] [<-bkt backuptime] [-s ] DESCRIPTION After Recovery Manager for SQL is installed, by default the wait time for snap volume restore and the backup is 30 seconds and 5 minutes respectively. You can use this command to change this value as needed. PARAMETERS -prt - Promote Time to query the status (default is 30 seconds).
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 7.3 Running Recovery Manager as a Scheduled Job In addition to creating virtual copies using the Command Line Interface, you can also schedule virtual copies to be created for a specific database using Windows Scheduled Tasks. To create virtual copies using Windows Scheduled Tasks: 1 Click Start > Programs > Accessories. The click System Tools > Scheduled Tasks. 2 Double-click Add Scheduled Tasks.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide See the RMSql CREATE command for detailed information. For example: “C:\Program Files\3par\VCDBA\SQL\RMSql.exe” create –i inst01 –d test -s SQLserver 10 On the Schedule tab, further refine the scheduled task by selecting the frequency and start time of the task. Click Apply and OK when finished. ◆ Virtual copies are created as you have scheduled.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide maximum threshold (see Setting the Recovery Manager Policy Configuration on page 6.8). Running Recovery Manager as a Scheduled Job 3PAR Confidential 7.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 7.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 8 Recovery for Microsoft SQL Server In this chapter 8.1 Recovery 8.1 8.1.1 Point-In-Time Recovery 8.2 8.1.2 Point-Of-Failure Recovery 8.3 8.1.3 SQL Instance Level File Copy Restore in an MSCS Environment 8.4 8.1.4 Volume Restore in an MSCS Environment 8.5 8.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide The full recovery model allows you to restore a database to a specific point in time. For example, you can restore a database to a specific time just before a failure occurs. With the full recovery model, no data is lost because the transaction logs are saved until the failure occurs. The bulk-logged recovery model is used for high-performance operations and involves bulk copying and bulk data modification.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 8.1.2 Point-Of-Failure Recovery A point-of-failure recovery can be achieved when a full backup of the SQL database has been performed and has been followed by a log backup. This type of recovery is useful for customers who cannot afford to lose any data in the event of a system failure. As long as the transaction logs were not damaged, this function can be used to recover the database up to the point of the failure.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Bring the database back online. At this stage, the database is in the no_recovery mode and the DBA can now apply the log backups that took place after the virtual copy backup was taken. To perform a point-of-failure recovery: 1 Find the timestamp that has a consistent full backup, (such as 010106000000). 2 Find the server name (such as SQLserver01). 3 Find the SQL instance name (such as SQLInstan01).
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 8.1.4 Volume Restore in an MSCS Environment To perform a volume restore in an MSCS environment: 1 Logon to your production server, which is also the active node in your cluster, and put all disks associated with the instance or database in maintenance mode. a If you are using Windows 2003, run the following commands for all disks associated with the instance or database.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 2 Take the corresponding SQL Server and SQL Server Agent offline. a If you are using Windows 2003, go to the Cluster Administrator and select your cluster group. Right-click on the corresponding SQL Server and SQL Server Agent, and select Take Offline. 8.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide b If you are using Windows 2008, go to the Failover Cluster Manager. Under Services and applications, select your SQL Server. Under Other Resources, right-click on SQL Server and select Take this resource offline. 3 Log onto your Backup server and perform a volume restore. You can perform the volume restore with either the RMSql restore command or the Recovery Manager GUI.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide b If you are using Windows 2008, go to the Failover Cluster Manager under Services and applications, and select your SQL Server. Under Disk Drives, rightclick the on the disk and select More Actions > Turn off maintenance for this disk. Repeat for all disks associated with the instance or database to be taken out of maintenance mode. 8.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 5 Put the SQL Server and SQL Server Agent resources back online. a If you are using Windows 2003, go to the Cluster Administrator and select your cluster group. Right-click on the SQL Server resources that were taken offline in Step 2 and select Bring Online. Recovery 3PAR Confidential 8.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide b If you are using Windows 2008, go to the Failover Cluster Manager. Under Services and applications, select your SQL Server. Under Other Resources, right-click on SQL Server and select Bring this resource online. c Under Other Resources, if your SQL Server Agent is still offline, bring it back online. The volume restore is complete. 8.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 9 Remote Copy for Recovery Manager In this chapter 9.1 Purpose of Remote Copy 9.1 9.2 How it works 9.2 9.3 How to Setup the Remote Copy Feature 9.3 9.3.1 Set Up Remote Copy Group for Databases 9.4 9.3.2 Set Up Remote Copy Group for Instances 9.4 9.4 Recovering an SQL database from a Secondary Site 9.5 9.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 9.2 How it works When users want to synchronize the data from the production site to secondary site, Recovery Manager for Microsoft SQL will leverage the VSS framework to freeze the I/O at the application level, and then allows the VSS provider to take a snapshot of the database and log volumes. Once the snapshot is taken, Remote Copy performs a synchronization on the data changes to the target volumes at the secondary site.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 9.3 How to Setup the Remote Copy Feature In order to use the 3PAR Remote Copy feature, you must first install and configure a Remote Copy environment. NOTE: See the 3PAR Remote Copy User’s Guide for details on how to set up Remote Copy. Once you have Remote Copy set up between two Inservs, you should create a remote copy group for testing before going to the next step.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 9.3.1 Set Up Remote Copy Group for Databases Follow these steps to set up Remote Copy for a given database: 1 Identify the volumes that contain the database and log files to be copied. 2 Create one remote copy group for one database. 3 Add the volumes belonging to the database files and log files into the remote copy group with remote copy target volumes. 4 Synchronize the remote copy group.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 9.4 Recovering an SQL database from a Secondary Site In the event of an SQL database crash at a Primary site, you should have a dedicated target server at the Secondary site, that is setup in an identical manner to the original SQL production server for recovery purposes. (Same configuration includes: instance names, database names, structures, and with Windows authentication mode set in the same way as well).
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide 9.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide A Server Virtualization Environments A.1 VMWare and Egenera Support for VMWare and Egenera environments is provided under certain specific conditions. New volumes presented to VMWare and Egenera servers are not surfaced automatically, so the RMSql mount command is limited to being executed on the backup host. Figure A-1 on page A.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide SQL Server 1 Egenera SQL Server 2 VMWare ESX Server 3PAR InServ Recovery Manager Backup Server Figure A-1. Server Virtualization Environment The following requirements need to be met for VMWare and Egenera to be supported: 1 The disks presented to the SQL Servers need to be raw devices. 2 The backup server needs to be connected directly to the InServ and not through VMWare or Egenera. ■ A.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide B Troubleshooting This appendix is designed to be used like a Frequently Asked Questions section. It will help find solutions to some of the common issues that may arise when running the Recovery Manager for Microsoft SQL. Problem: Error message “VSS_E_PROVIDER_VETO” appears.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Suggestion: Restart the RMSql agent service on the backup and production servers. Problem: When backing up a virtual copy using NetBackup through the Recovery Manager GUI, if a directory is specified for backup, the directory must be entered in exactly the same case as it resides on the file system. If this is not done then a restore of this backup will fail. This is a limitation of Veritas NetBackup.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Problem: Recovery Manager always fails to issue command from the user interface and command line right after the installation. Suggestion: If the software is installed through remote desktop session, the newly added environment variables will not become effective until user logs off the session. If the software is installed directly from system console, these variables should be available immediately.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide B.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Index A G advisories 1.5 GUI menu bar 6.3 audience for this guide 1.1 C H cautions, defined 1.5 host computer and controller nodes, configuring 5.4 configuring host computer and controller nodes 5.4 I Recovery Manager 5.2 installation location of Recovery Manager 5.2 the database 5.2 installation of Recovery Manager, verifying 3.7 controller nodes and host computer, configuring 5.4 installing Recovery Manager 3.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide R T Recovery Manager Troubleshooting commands 7.3 default installation location 5.2 troubleshooting B.1 typographical conventions 1.4 installation 3.1 verifying installation 3.7 U related documents 1.2 understanding the registry, registry 3.9 revision history RH.1 V S verifying installation of Recovery Manager 3.7 search path 5.2 virtual copy server maintenance required tools A.2, B.1 setting virtual copy limit 6.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide Revision History .............. Release Level Revision Summary 320-200206 Rev A First release of this manual to support product release 3.0.2. January 2010 320-200206 Rev B Second release of this manual to clarify minor technical references. March 2010 Revision History RH.
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide RH.
