HP Application Software Suite for Microsoft SQL Licenses User Manual

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

HP Part Number: QL226-96143 Published: August 2011

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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries

in the United States and other countries.

Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

SQL Server is a trademark of Microsoft Corporation.

All other trademarks and registered trademarks are owned by their respective owners.

Documentation

For the latest version of this document, go to http://www.hp.com/go/3par/, navigate to your product page, click Support for your product, and then click Manuals.

1 Introduction...............................................................................................6

Related Documents...................................................................................................................6

Typographical Conventions........................................................................................................6

Advisories................................................................................................................................7

2 Overview of Recovery Manager...................................................................8

System Requirements.................................................................................................................8

Windows Server Requirements...............................................................................................8

Windows Server 2003 with SP2 or above..........................................................................8

Windows Server 2008....................................................................................................8

Windows Server 2008 R2...............................................................................................8

Additional System Requirements.............................................................................................8

Recovery Manager Requirements................................................................................................9

Running Recovery Manager on a Japanese OS............................................................................9

Features Supported.................................................................................................................10

Features Not Supported...........................................................................................................11

Microsoft Volume Shadow Copy Service....................................................................................11

Supported VSS Components....................................................................................................12

How HP 3PAR VSS Software Works with Microsoft SQL Server.....................................................12

Recovery Manager Layout........................................................................................................13

3 Installation and Deinstallation.....................................................................15

Upgrading to Recovery Manager 4.2.0 for SQL ........................................................................15

Upgrading the Production Server.........................................................................................15

Upgrading the Backup Server..............................................................................................15

Verifying the Upgrade........................................................................................................15

Pre-Installation Steps...............................................................................................................15

Installing Recovery Manager....................................................................................................16

Verifying the Installation...........................................................................................................17

Understanding the Registry......................................................................................................17

Deinstalling Recovery Manager................................................................................................18

4 Configuring Recovery Manager..................................................................19

Configuring the SQL Database.................................................................................................19

Configuring Recovery Manager................................................................................................19

Installation Location............................................................................................................19

Search Path.......................................................................................................................19

Changing the Recovery Manager TCP/IP Port........................................................................19

Changing a Production Server Port from the Backup Server.................................................20

Configuring Recovery Manager Policies................................................................................20

Configuring Mount Functionality..........................................................................................20

Managing SQL Servers across Multiple Active Directory Domains............................................20

Grouping Volumes into Autonomic Groups............................................................................20

Domain Sets.................................................................................................................20

Volume Sets..................................................................................................................21

Host Sets......................................................................................................................21

Testing SQL Connectivity..........................................................................................................21

Troubleshooting SQL Connectivity........................................................................................22

Configuring the Host Computer and the HP 3PAR Storage System.................................................22

Formatting Partitions on a New HP 3PAR VLUN..........................................................................23

Windows Server 2003.......................................................................................................23

Contents 3

5 Configuring Backup Software.....................................................................24

Overview..............................................................................................................................24

Before You Begin....................................................................................................................24

Setting Up Symantec NetBackup...............................................................................................24

Configuring HP Data Protector .................................................................................................25

Requirements ....................................................................................................................25

Setting Up the HP Data Protector Backup Specification............................................................25

Setting Up HP Data Protector Cell Manager Access................................................................25

Using Your Backup Software ...................................................................................................26

Using Symantec NetBackup.................................................................................................26

Using HP Data Protector.....................................................................................................26

6 Using the Recovery Manager GUI..............................................................27

Overview of the Recovery Manager GUI...................................................................................27

Menu Bar.........................................................................................................................27

Node Tree Pane.................................................................................................................27

Informational Pane.............................................................................................................27

Opening the Recovery Manager GUI........................................................................................27

Closing the Recovery Manager GUI..........................................................................................27

Registering the Server..............................................................................................................27

Updating Registration after Server Modification.....................................................................28

Unregistering a SQL Server Instance..........................................................................................29

Setting the Recovery Manager Policy.........................................................................................29

How Recovery Manager Policies Work.................................................................................29

Numeric-Based Policies..................................................................................................29

Expiration-Based Policies................................................................................................29

Retention Time Restrictions..............................................................................................30

Setting Recovery Manager Policies.......................................................................................30

Modifying the Policy for a Virtual Copy.................................................................................31

Configuring Email Notifications................................................................................................31

Deleting Email Configurations..................................................................................................32

Creating Virtual Copies...........................................................................................................32

How Virtual Copy Creation Works.......................................................................................32

Manually Creating a Virtual Copy........................................................................................32

Creating Remote Virtual Copies...........................................................................................33

How Remote Virtual Copy Works....................................................................................33

Manually Creating a Remote Virtual Copy........................................................................33

Displaying Remote Virtual Copies....................................................................................33

Scheduling Automatic Virtual Copies....................................................................................33

Automating Tasks...................................................................................................................34

Scheduling Automated Tasks with Task Scheduler...................................................................34

Managing Automated Tasks with Task Manager....................................................................35

Mounting a Virtual Copy.........................................................................................................35

Unmounting a Virtual Copy......................................................................................................36

Backing Up a Virtual Copy......................................................................................................36

Manually Creating Backups at the Instance or Database Level.................................................36

Scheduling Automatic Backups of an Instance or Database.....................................................37

Creating a Backup of a Virtual Copy....................................................................................38

Removing a Backup from the Repository....................................................................................38

Restoring Instances, Databases, and Volumes.............................................................................38

Restoring an Instance or Database with Volume Restore..........................................................39

Restoring an Instance or Database with File Copy Restore.......................................................39

Restoring an Instance or Database from a Backup..................................................................40

Analyzing and Synchronizing the Repository..............................................................................40

Removing a Virtual Copy.........................................................................................................41

4 Contents

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

RMSql backup...................................................................................................................44

RMSql create.....................................................................................................................46

RMSql deletebackup..........................................................................................................49

RMSql display...................................................................................................................50

RMSql listbackup...............................................................................................................51

RMSql mount.....................................................................................................................52

RMSql policy.....................................................................................................................53

RMSql portconfig...............................................................................................................56

RMSql remove...................................................................................................................57

RMSql report.....................................................................................................................58

RMSql repository...............................................................................................................59

RMSql restore....................................................................................................................60

RMSql setvc......................................................................................................................63

RMSql timeconfig...............................................................................................................65

RMSql unmount.................................................................................................................66

Running Recovery Manager as a Scheduled Job.........................................................................66

Scheduling an Automated Task in Windows 2003......................................................................66

Scheduling an Automated Task in Windows 2008......................................................................67

8 Recovery for Microsoft SQL Server..............................................................68

Microsoft SQL Server Recovery Models......................................................................................68

Recovering Data with HP 3PAR Recovery Manager.....................................................................68

Preparing for the Recovery Process............................................................................................68

Recovering from Logical Errors with Point-in-Time Recovery............................................................68

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

Restoring a Volume in an MSCS Environment Using Volume Restore..........................................69

Recovering All Data with Point-of-Failure Recovery.......................................................................69

Determining Whether You Can Perform a Point-of-Failure Recovery...........................................70

Performing a Point-of-Failure Recovery...................................................................................70

9 Remote Copy for Recovery Manager...........................................................72

Overview..............................................................................................................................72

How Remote Copy Works........................................................................................................72

Setting Up Remote Copy..........................................................................................................73

Support for Remote Copy Modes and Policies........................................................................74

Support for GeoCluster for Microsoft Windows......................................................................74

Setting Up Remote Copy Volume Groups...................................................................................74

Setting Up a Remote Copy Volume Group for Databases........................................................74

Setting Up a Remote Copy Volume Group for Instances..........................................................75

Recovering a SQL Database from a Remote Copy Backup Server..................................................75

A Server Virtualization Environments..............................................................76

VMWare and Egenera............................................................................................................76

B Troubleshooting........................................................................................77

C Event Messages.......................................................................................79

Contents 5

1 Introduction

Typographical Conventions

ABCDabcd

HP 3PAR VSS Provider Software for Microsoft Windows User's Guide

HP 3PAR InForm OS Configuration MatrixPlatform-specific release levels 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.

Used for dialog box elements such as titles and button labels.

Used for file names, paths, and screen output, and for text you are to enter.

Used to contrast your input with system output.

Used for variables in file names, paths, and screen output, and for variables in user input.

ExampleMeaningTypeface

Enter your system name in the Value box and click OK.

Found < 12 > 73G disks. Enter cli at the Windows command prompt.

cli% removevv VV1 Removing vv VV1.

[root@(systemID-nodeID)root] To continue enter your system name ==> systemname

6 Introduction

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.

WARNING! Warnings alert you to actions that can cause injury to people or irreversible damage

to data or the operating system.

CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.

NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this

guide.

Advisories 7

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.4 GHz processor

• 2+ GB RAM

• 40 GB hard disk space

Windows Server 2008 R2

• Either 1.4 GHz (x64) or 1.3GHz (Dual Core) processor

• 2+ GB RAM

• 32+ GB hard drive space

Additional System Requirements

• Microsoft SQL Server 2005 with SP2 or above, Microsoft SQL Server 2008, or Microsoft SQL

Server 2008 R2.

• SQL Server client utilities must be installed on the backup server.

• All SQL instances must be TCP/IP enabled.

• To automatically display the SQL server name and instance name in the server-registration

wizard, turn on the corresponding SQL Browser Service(s).

• Microsoft .NET framework 3.5 SP1 or above.

• HP 3PAR Recovery Manager for SQL Software license for the HP 3PAR Storage System.

8 Overview of Recovery Manager

• 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

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.

• Volume Shadow Copy Service Full backup type

• Virtual copy creation using HP 3PAR VSS Provider Software for Microsoft Windows

• Scheduling and management of automated tasks

• Access HP 3PAR Storage System via HP 3PAR InForm OS CLI

• Mount virtual copies locally or remotely

• Mount virtual copies in read/write mode

• Unmount virtual copies

• Delete virtual copies

• Environment Report

• File Copy restore

• Database-level file restore in “No Recovery” mode

• Restore from virtual copies

• Backups using HP Data Protector or Symantec NetBackup – both client and master

• Database cloning

• Restore from backup using HP Data Protector or Symantec NetBackup

• Recovery Manager GUI

• Recovery Manager CLI

• Volume analysis

• Volume restore

• Virtual copy creation of local and remote Microsoft SQL Server

• MSCS environment

• Remote Copy

• Virtual copy operations on SQL instance and database level

• Virtual Lock of an instance and its virtual copies

• Autonomic groups (domain sets, volume sets, and host sets)

10 Overview of Recovery Manager

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.com/kb/943471

Features Not Supported

• Microsoft SQL Server offline backup

• VSS backup types “Incremental,” “Differential,” “Copy,” and “Log”

• All backup tools, except for HP Data Protector and Symantec NetBackup

• Access to HP 3PAR Storage System via SSH

• Display of different versions of Microsoft SQL Server from the same Recovery Manager backup

server

• Interoperability between Windows Server 2003 and Windows Server 2008

In other words, you cannot mount a virtual copy created under Windows 2003 to a Windows 2008 target host.

• Taking a snapshot of the SQL servers created with the SQL Server Authentication setting.

Recovery Manager for SQL supports SQL servers created with the Windows Authentication setting. If you are running SQL Server, Recovery Manager supports both Windows Authentication mode and SQL Server and Windows Authentication mode.

• Taking a snapshot of a database residing on a network mapped volume

• Virtual copy ownership transferring. For example, you can only remove virtual copies if you

created them, and you can only unmount virtual copies if you mounted them.

• Taking a snapshot of an instance or database that resides on dynamic disks

• Mounting snapshots to a Windows host that resides in virtual environment

• Performing a restore in a virtualization environment

• Date customization. Recovery Manager always displays dates in month/day/year format.

• Windows automount feature

Microsoft Volume Shadow Copy Service

Microsoft includes Volume Shadow Copy Service (VSS) in Windows 2003 and Windows 2008 to simplify the enterprise’s storage environment, which provides a framework for creating a point-in-time copy of either a single volume or multiple volumes.

Microsoft Windows Server 2008 VSS works with VSS-aware applications that are used to determine when a volume shadow copy (snapshot) can be made. (A snapshot is a virtual copy: a copy of some data set—for example, a disk volume—at a point in time.) Before making a snapshot, VSS communicates with the operating system and applications to freeze computing tasks, which enables an application-consistent snapshot to be taken. The shadow copy volume is then used for the actual backup. After VSS saves the shadow copy volume on the backup device, it deletes the shadow copy.

Features Not Supported 11

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 DescriptionVSS Component

Requestor

Writer

Provider

Supported VSS Components

Requestor:

• Recovery Manager

• Symantec NetBackup for Microsoft Windows

• HP Data Protector for Microsoft Windows

Writer:

• Microsoft SQL Server 2005, 2008, and 2008 R2 with SQL Server Writer

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.

The requestor is backup software that initiates the creation of the shadow copy.

The writer is any application software that participates in the shadow copy process and whose files and data are included in the process.

The provider is the storage technology that does the actual shadow copy.

How HP 3PAR VSS Software Works with Microsoft SQL Server

Figure 1 HP 3PAR VSS Provider Software for Microsoft Windows Operation Overview

1. The requestor (HP 3PAR Recovery Manager) sends a command to the Volume Shadow Copy service to take a shadow copy of the selected Microsoft SQL Server database.

12 Overview of Recovery Manager

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

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.

4. HP 3PAR VSS Software then communicates with the writers and providers to start creating the shadow copy. The provider actually creates the shadow copy.

The shadow copy typically takes less than a minute.

5. After the shadow copy is created, Volume Shadow Copy service communicates with the Microsoft SQL Server with MSDE writer or SQL writer to indicate that it can resume writing to disk.

6. The queues of the SQL transactions are written to the logs. The shadow copy is now available to the requestor for backing up.

Recovery Manager Layout

Recovery Manager Layout 13

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. The release version of SQL Server must be 2005, 2008, or 2008 R2. Versions prior to SQL Server 2005 are not supported.

• Connectivity

Both the backup server and SQL Server must be connected to the same HP 3PAR Storage System.

14 Overview of Recovery Manager

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. Deinstall 3PAR Recovery Manager for SQL. For more information, see “Deinstalling Recovery

Manager” (page 18).

2. Install HP 3PAR Recovery Manager 4.2.0 for SQL. For more information, see “Installing

Recovery Manager” (page 16).

Upgrading the Backup Server

The upgrade steps for the Recovery Manager backup server also apply to the Remote Copy backup server(s), if applicable to your setup.

1. If you plan to use a different installation folder for the new version of Recovery Manager for

SQL and not the same folder as the previous version, make a copy of the repository. The repository is located in:

• Recovery Manager 4.1.0 for SQL: <Install Directory>\RM\SQL\Data

• Recovery Manager 3.0.2 for SQL: <Install Directory>\VCDBA\SQL\Data

If you plan to use the same installation folder for the new version as the folder that was used for the previous version, skip this step.

2. Deinstall the previous version of 3PAR Recovery Manager for SQL. For more information, see

“Deinstalling Recovery Manager” (page 18).

3. Install HP 3PAR Recovery Manager 4.2.0 for SQL. For more information, see “Installing

Recovery Manager” (page 16).

4. If you used a different installation folder for Recovery Manager 4.2.0 for SQL, copy the

repository data from the previous version of Recovery Manager for SQL to:

<Install Directory>\RM\SQL\Data

If you used the same installation folder for both the new and previous version, skip this step. Recovery Manager for SQL automatically imports all the repository data.

Verifying the Upgrade

1. Verify that Recovery Manager for SQL is listed as a service that is currently running.

2. Check whether you can see the previously created virtual copies in the GUI. Re-register the

SQL servers if necessary.

3. If you used the Recovery Manager Backup or All of above option to install Recovery Manager,

verify that the 3PAR Recovery Manager for SQL Server icon appears on the desktop.

4. Verify the registry key. For more information, see “Understanding the Registry” (page 17).

Pre-Installation Steps

Before installing HP 3PAR Recovery Manager Software, install the following:

• HP 3PAR InForm OS Command Line Interface (CLI) for remote clients. For more information,

see the HP 3PAR InForm OS CLI Administrator’s Manual.

• HP 3PAR VSS Provider Software for Microsoft Windows. For more information, see the HP

3PAR VSS Provider User's Guide.

Upgrading to Recovery Manager 4.2.0 for SQL 15

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.

NOTE: You can perform the installation from a remote desktop connection, but HP

recommends that you install the application directly from the system console.

2. Insert the Recovery Manager CD.

3. Open a Windows Explorer window and click the CD-ROM drive to expand the files.

4. Select the corresponding package for your OS version.

Table 1 Operating System Packages

PackageOperating System

RMS_W2K3_x86.msiWin2003 32-bit

RMS_W2K3_x64.msiWin2003 64-bit

RMS_W2K8_x86.msiWin2008 32-bit

RMS_W2K8_x64.msiWin2008 64-bit

RMS_W2K8_x64.msiWin2008 R2 64-bit

5. In the 3PAR Recovery Manager for SQL Server Setup wizard, click Next.

6. After the license agreement appears, select I Agree and click Next.

7. Select the type of server on which you are installing Recovery Manager:

• Recovery Manager Backup Server - Select this option if this server is your backup server.

This option installs the Recovery Manager GUI on this server; you can use this GUI to manage your SQL production servers.

NOTE: You must install the SQL Server client utilities on the host on which the Recovery

Manager Backup Server is installed.

• Recovery Manager Agent for SQL Server - Select this option if this server is one of your

SQL production servers running Microsoft SQL Server.

• All of above - Select this option if this server is both your backup server and your SQL

production server. This option installs the Recovery Manger GUI and all of the Recovery Manager Agent components on this server.

8. Specify the installation directory for Recovery Manager.

NOTE: To check whether the server has enough space for Recovery Manager, click the Disk

Cost button. The wizard analyzes the amount of available storage space and compares it to

the amount required for the Recovery Manager installation.

9. Click Next to confirm the installation destination.

10. After installation is complete, click Close.

11. Recovery Manager for SQL runs a utility to scan for possible configuration errors.

12. After this utility completes, the results are automatically displayed in a Notepad file. 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.

16 Installation and Deinstallation

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.

Verifying the Installation

1. Log on as the system administrator.

2. Depending on your operating system, do the following:

• In Windows 2003, click Start→Control Panel→Add/Remove Programs.

• In Windows 2008 or 2008 R2, click Start→Control Panel→Programs and Features.

3. Verify that Recovery Manager appears in the Currently installed programs column.

4. If you used the Recovery Manager Backup or All of above option to install Recovery Manager, verify that the 3PAR Recovery Manager for SQL Server icon appears on the desktop.

Understanding the Registry

After Recovery Manager is successfully installed, information is written into the registry database under: HKEY_LOCAL_MACHINE\SOFTWARE\3PAR\RM_SQL

CAUTION: DO NOT edit the registry key value unless asked by your local service provider for

support purposes.

Table 2 System Registry Values for Recovery Manager

ValueName

AnalyzeInterval

BackupTimeout

Build

Interval in minutes between automatic synchronizations of the repository with the InForm. The default interval is 60 minutes.

Backup process timeout value in minutes to confirm that NetBackup has received the backup request.

Build number of the installed version of Recovery Manager for SQL.

Location of the XML repository.DataFilePath

Recovery Manager for SQL installation path.InstallPath

Tracing log files.LogFilePath

Number of trace files to keep before deleting.TraceHistory

Trace level for the log file.TraceLevel

Information used to generate the trace file name.TraceLog

Size of the log files.TraceLogSize

PortNo

PromoteTimeout

Port used by Recovery Manager for SQL. PortNo is set to 9932 by default.

Time interval in seconds to monitor the status of volume restore operation.

Current version of Recovery Manager for SQL Server.Version

Verifying the Installation 17

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. Log on as the system administrator.

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

3. Select 3PAR Recovery Manager for Microsoft SQL Server.

4. Click Remove.

NOTE: After deinstalling Recovery Manager, snapshots and scheduled tasks still reside

locally in the Data folder as well as on the system. You can remove snapshots and/or scheduled tasks later, if desired.

18 Installation and Deinstallation

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

◦ Do not add files from one database (including its transaction log files) to multiple volumes.

CAUTION: Be sure to maintain a one database:one volume relationship.

If you add multiple databases to one volume, backup and disaster recovery operations on one database can result in conflicts between the databases in the volume.

Configuring Recovery Manager

Installation Location

By default, Recovery Manager installs in:

C:\Program Files\3PAR\RM\SQL

Search Path

After installation, you can instantly issue Recovery Manager CLI commands from any directory. Although the Recovery Manager executables are installed in a fixed location that is specified during installation, the location is automatically added to the Windows PATH environment variable.

Changing the Recovery Manager TCP/IP Port

By default, Recovery Manager for SQL uses port 9932 for cross-server communication. As long as port 9932 is available, no extra port configuration is necessary.

If port 9932 is not available or is occupied by another system process, you must change the Recovery Manager TCP/IP port.

1. Select an available port. The valid TCP/IP port range is 1024 to 65535.

2. To set your desired port number, run the Recovery Manager CLI RMSql portconfig command.

For example, to change the port number to 9999, use: RMSql portconfig -n 9999

CAUTION: If you are changing ports from the backup server, be sure to change the Recovery

Manager ports on the production servers first. If you change the backup server port first, you cannot then access the production servers in order to change their ports.

3. From the Windows Service console, restart the Recovery Manager for SQL service.

4. Repeat these steps for all production servers and the backup server.

Configuring the SQL Database 19

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 <Windows_host/production_server> -n <port_number>

2. On the production server, restart the Recovery Manager for SQL service.

Configuring Recovery Manager Policies

• To use the Recovery Manager GUI to set database policies, see “Using the Recovery Manager

GUI” (page 27).

• To use the Recovery Manager CLI to set database policies, see “Using the Recovery Manager

CLI” (page 42), for information about using the RMSql policy command.

Configuring Mount Functionality

The Windows automount feature is not compatible with Recovery Manager. To ensure that the Windows automount feature is disabled:

1. Open a command prompt (cmd) window.

2. Enter: diskpart

3. At the DISKPART prompt, enter: automount disable

4. Exit the command prompt window.

Managing SQL Servers across Multiple Active Directory Domains

If you are configuring Recovery Manager to work with SQL Servers across multiple Active Directory domains, you must store the appropriate login and password in the Windows user account on the backup server.

1. On the backup server:

• In Windows 2003, click Start→Control Panel→Stored User Names and Passwords and

click Add.

• In Windows 2008, click Start→Control Panel→User Accounts and click Manage your

network passwords. In the Logon Information Properties dialog box, click Add.

• In Windows 2008 R2, click Start→Control Panel→User Accounts and click Manage your

credentials→Add a Windows credential.

2. In the Log on to field (or, for Windows 2008 R2, the Internet or network address field), enter

the network location to which you want automatic access. You can use a wildcard if you want access to multiple computers on a domain. For example:

*.aztec.com

3. Enter the appropriate login and password.

4. Repeat these steps for all SQL Server domains in the Recovery Manager configuration.

Grouping Volumes into Autonomic Groups

You can group virtual volumes into autonomic groups (domain sets, volume sets, or host sets).

Domain Sets

If your SQL Server configuration involves multiple database servers that belong to different HP 3PAR Virtual Domains, you can use the domain set feature to group these virtual domains into one

20 Configuring Recovery Manager

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.

• To create a Remote Copy group for a virtual volume that is in a user-defined domain, the

associated virtual volume on the Remote Copy backup server must be in the same user-defined domain.

To configure domain sets, use HP 3PAR CLI commands to:

1. Ensure you are running HP 3PAR InForm Operating System Software 2.3.1 or higher.

2. Ensure you have access to all domains.

3. Create a domain set that contains all HP 3PAR Virtual Domains for all the database servers.

4. Create a Command Provisioning Group (CPG) belonging to the new virtual domain.

5. Create a virtual volume belonging to the CPG you just created.

6. Create a host belonging to the virtual domain.

7. Export the VLUN to the host.

8. On the Recovery Manager backup and production servers, set the user for the HP 3PAR VSS Provider Software.

9. Ensure the HP 3PAR Storage System connection is good.

NOTE: For more information on HP 3PAR CLI commands, see the HP 3PAR InForm OS

Command Line Interface Reference. For more information on HP 3PAR VSS Provider Software,

see the HP 3PAR VSS Provider Software for Microsoft Windows User’s Guide.

Volume Sets

To configure volume sets:

• In a volume set, place either:

one database and its log files◦

◦ one instance and its related files

• Do not place one volume in more than one volume set.

• Do not place unrelated volumes in a volume set.

Host Sets

You can configure your system with host sets and volume sets, or with host sets only. You can add all nodes of a cluster to one host set.

Testing SQL Connectivity

After you install and configure Recovery Manager on the backup server and all of the production servers, verify that your SQL instances are reachable:

1. Log onto the backup server as the system administrator.

2. Launch SQL Server Management Studio.

3. In the Connect to Server window, enter or select the following:

Server type: Database Engine

Testing SQL Connectivity 21

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: <SQLserverName>\<instanceName>. For example:

Server name: Bottlenosed\MSDE_VC

Authentication: Windows Authentication

4. Click Connect. SQL Server displays a screen similar to the following:

If you are able to connect, the installation and configuration is complete. If the connection cannot be made, you must fix the SQL configuration. For more information,

see “Troubleshooting SQL Connectivity” (page 22).

Troubleshooting SQL Connectivity

1. Log onto the SQL production server as system administrator and check connectivity:

• From the SQL production server, launch SQL Server Management Studio to make sure

the connection can be made locally.

• From Management Studio, right-click SQL server→Properties→Connections.

Make sure the Allow remote connections to this server box is checked.

• Make sure the SQL server for that instance has a status of started.

• For named instances, make sure the SQL server browser has a status of started.

• Double-check the settings under Properties→Security.

• Double-check the settings under Properties→Permissions.

2. After you have fixed the SQL configuration on the production server, log onto the backup server and run the SQL connectivity test again.

NOTE: Your backup server must pass this SQL connectivity test before you can use HP 3PAR

Recovery Manager Software for Microsoft SQL Server.

Configuring the Host Computer and the HP 3PAR Storage System

For information about configuring the HP 3PAR Storage System to communicate with the host computer, see the HP 3PAR InForm OS Concepts Guide and the HP 3PAR InForm OS CLI Administrator’s Manual.

22 Configuring Recovery Manager

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. Align the offset to 64KB, as recommended in this article: Disk

Partition Alignment Best Practices for SQL Server

To check the current offset value, use the Microsoft System Information utility, included with Windows:

1. Launch the System Information utility one of the following ways:

• Select Start→Programs→Accessories System Tools→System Information

• At the command prompt, run the command: msinfo32.exe

2. Select System Summary→Components→Storage→Disks. The offset for each disk in the system is displayed in bytes in the Partition Starting Offset field.

Formatting Partitions on a New HP 3PAR VLUN 23

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

Before You Begin

Ensure that you have set up a storage unit for storing virtual copy backups. For more information, see the documentation for the backup software you are using.

Setting Up Symantec NetBackup

To set up your Symantec NetBackup software, see the Symantec NetBackup documentation. To configure Symantec NetBackup to function with Recovery Manager for SQL, set the following

parameters during the configuration process:

Clients

SettingBackup Policy Parameter

MS-Windows-NTPolicy type

Select the machine on which the Recovery Manager Backup Server component is installed.

Ensure this option is unchecked.Collect disaster recovery information for Bare Metal Restore

User backupType of backup

Activate all the time slots:Starting times for backups

• Modify Day: Mon

• Start Time: 12:00:00AM

• End Day: Sun

• End Time: 12:00:00AM

• Duration (days): 7

24 Configuring Backup Software

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

• Data Protector patch for omnidl (# DPWIN_00514)

• Each data list name (also known as the backup specification) must be unique across the entire

system

Setting Up the HP Data Protector Backup Specification

To use HP Data Protector with Recovery Manager, you must set up a default backup specification. The backup specification specifies the default mount point and the necessary devices for tape backup.

1. Open the Data Protector GUI.

2. Select Backup→Add Backup.

3. In the Create New Backup dialog box, select Blank_Filesystem_Backup and click OK.

4. Click Next (do not select any items).

5. Select the device that Data Protector is to use for backups.

6. Click Next until the Manual add... appears.

7. Click Manual add...

8. Select Windows filesystem and click Next.

9. Enter the appropriate client system, mount point, and description. HP recommends:

<server_used_as_backup_client>Client system

C:Mount point

defaultDescription

NOTE: Recovery Manager uses this information only to create a backup template. Recovery

Manager does not use the actual data entered.

10. Click Next until the Finish button is enabled.

11. Save the backup specification. When you issue the RMSql backup command with the -dl option, use the name with which

you saved the backup specification (e.g., DPbackup) as the value of the -dl option.

Setting Up HP Data Protector Cell Manager Access

To use HP Data Protector with Recovery Manager, you must enable the system accounts on the registered client system to access the Data Protector Cell Manager.

1. Open the Data Protector GUI.

2. In the toolbar drop-down list, select Users.

3. Under the Users folder in the left pane, select admin→SYSTEM.

4. In the Client system drop-down list on the General tab in the right pane, select <Any>.

Configuring HP Data Protector 25

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:

<system drive>:\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. You must use your backup software to

monitor restore progress.

• For more information about using CLI commands with your backup software, see RMSql

backup, RMSql deletebackup, RMSql listbackup, and RMSql restore in “Using

the Recovery Manager CLI” (page 42).

• For more information about using your backup software to back virtual copies up to media,

see “Backing Up a Virtual Copy” (page 36).

• For more information about using your backup software to restore virtual copies from media,

see “Restoring Instances, Databases, and Volumes” (page 38).

Using Symantec NetBackup

• Symantec NetBackup software is case-sensitive. If you are using NetBackup, make sure all

information entered pertaining to the policy is supplied with the proper case.

• Any time you are using NetBackup to back up to media or restore from media, you can monitor

the progress using the progress log:

<RM installation location>\log\nbulog\database_timestamp.log

• To modify the timeout value for NetBackup software initialization, see “Understanding the

Registry” (page 17).

Using HP Data Protector

For each HP Data Protector backup you create, a postscript (.bat) file is created in the $DP_HOME\

bin folder (where $DP_HOME is the Data Protector install location; for example, C:\ program files\Omniback.) This script cleans up after the associated backup is complete.

Note that Recovery Manager does not clean these postscripts. After a backup is complete (either successfully or with failures), you can manually remove the associated postscript batch file if desired.

26 Configuring Backup Software

+ 58 hidden pages