HP Recovery Manager Software for Microsoft SQL Server Licenses User Manual
HP 3PAR Recovery Manager 4.3.0 Software for Microsoft SQL Server
User Guide
Abstract
This document is designed for System Administrators and Microsoft SQL Server Administrators who are experienced in using
Microsoft™ Windows™ and Microsoft SQL Server™ and responsible for backing up Microsoft SQL Server databases.
HP Part Number: QL226-96277
Published: May 2012
© Copyright 2012 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. 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.
Acknowledgements
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.
Contents
1 Overview of Recovery Manager...................................................................6
System Requirements.................................................................................................................6
Windows Server Requirements...............................................................................................6
Windows Server 2008....................................................................................................6
Windows Server 2008 R2...............................................................................................6
Additional System Requirements.............................................................................................6
Recovery Manager Requirements................................................................................................6
Running Recovery Manager on a Japanese OS............................................................................7
Features Supported...................................................................................................................7
Features Not Supported.............................................................................................................8
Microsoft Volume Shadow Copy Service......................................................................................9
Supported VSS Components......................................................................................................9
How HP 3PAR VSS Software Works with Microsoft SQL Server.....................................................10
Recovery Manager Layout........................................................................................................11
2 Installing and Uninstalling HP 3PAR Recovery Manager for SQL.....................12
Installing HP 3PAR Recovery Manager for SQL...........................................................................12
Verifying the Installation...........................................................................................................13
Understanding the Registry......................................................................................................14
Upgrading to Recovery Manager 4.3.0 for SQL ........................................................................14
Upgrading the Production Server.........................................................................................15
Upgrading the Backup Server..............................................................................................15
Verifying the Upgrade........................................................................................................15
Uninstalling HP Recovery Manager for SQL................................................................................15
3 Configuring Recovery Manager..................................................................16
Configuring the SQL Database.................................................................................................16
Configuring Recovery Manager................................................................................................16
Installation Location............................................................................................................16
Search Path.......................................................................................................................16
Changing the Recovery Manager TCP/IP Port........................................................................16
Changing a Production Server Port from the Backup Server.................................................17
Configuring Recovery Manager Policies................................................................................17
Configuring Mount Functionality..........................................................................................17
Managing SQL Servers across Multiple Active Directory Domains............................................17
Grouping Volumes into Autonomic Groups............................................................................18
Domain Sets.................................................................................................................18
Volume Sets..................................................................................................................19
Host Sets......................................................................................................................19
Testing SQL Connectivity..........................................................................................................19
Troubleshooting SQL Connectivity........................................................................................20
Configuring the Host Computer and the HP 3PAR Storage System.................................................21
Formatting Partitions on a New HP 3PAR VLUN..........................................................................21
4 Configuring Backup Software.....................................................................22
Overview..............................................................................................................................22
Before You Begin....................................................................................................................22
Setting Up Symantec NetBackup...............................................................................................22
Configuring HP Data Protector .................................................................................................23
Requirements ....................................................................................................................23
Setting Up the HP Data Protector Backup Specification............................................................23
Setting Up HP Data Protector Cell Manager Access................................................................23
Using Your Backup Software ...................................................................................................24
Contents 3
Using Symantec NetBackup.................................................................................................24
Using HP Data Protector.....................................................................................................24
5 Using the Recovery Manager GUI..............................................................25
Overview of the Recovery Manager GUI...................................................................................25
Menu Bar.........................................................................................................................25
Node Tree Pane.................................................................................................................25
Informational Pane.............................................................................................................25
Status and Summary Information..........................................................................................25
Opening the Recovery Manager GUI........................................................................................26
Closing the Recovery Manager GUI..........................................................................................26
Registering the Server..............................................................................................................26
Updating Registration after Server Modification.....................................................................28
Unregistering a SQL Server Instance..........................................................................................28
Setting the Recovery Manager Policy.........................................................................................28
How Recovery Manager Policies Work.................................................................................28
Numeric-Based Policies..................................................................................................28
Expiration-Based Policies................................................................................................28
Retention Time Restrictions..............................................................................................29
Setting Recovery Manager Policies.......................................................................................29
Modifying the Policy for a Virtual Copy.................................................................................30
Configuring Email Notifications................................................................................................30
Deleting Email Configurations..................................................................................................31
Creating Virtual Copies...........................................................................................................31
How Virtual Copy Creation Works.......................................................................................31
Manually Creating a Virtual Copy........................................................................................31
Creating Remote Virtual Copies...........................................................................................32
How Remote Virtual Copy Works....................................................................................32
Manually Creating a Remote Virtual Copy........................................................................32
Displaying Remote Virtual Copies....................................................................................32
Scheduling Automatic Virtual Copies....................................................................................32
Automating Tasks...................................................................................................................33
Scheduling Automated Tasks with Task Scheduler...................................................................33
Managing Automated Tasks with Task Manager....................................................................34
Prerequisites for Attach and Detach Operation............................................................................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..............................................................................41
Removing a Virtual Copy.........................................................................................................41
Viewing Event Message Descriptions.........................................................................................41
Viewing Online Help..............................................................................................................41
6 Using the Recovery Manager CLI................................................................42
Recovery Manager for SQL Server Command Line Interface (CLI)..................................................42
Recovery Manager Commands................................................................................................43
RMSql analyze..................................................................................................................43
RMSql backup...................................................................................................................44
4 Contents
RMSql create.....................................................................................................................45
RMSql deletebackup..........................................................................................................47
RMSql display...................................................................................................................48
RMSql listbackup...............................................................................................................49
RMSql mount.....................................................................................................................50
RMSql policy.....................................................................................................................52
RMSql portconfig...............................................................................................................54
RMSql remove...................................................................................................................55
RMSql report.....................................................................................................................55
RMSql repository...............................................................................................................56
RMSql rescan....................................................................................................................56
RMSql restore....................................................................................................................57
RMSql setvc......................................................................................................................60
RMSql timeconfig...............................................................................................................62
RMSql unmount.................................................................................................................63
Running Recovery Manager as a Scheduled Job.........................................................................63
Scheduling an Automated Task in Windows 2008......................................................................63
7 Recovery for Microsoft SQL Server..............................................................65
Microsoft SQL Server Recovery Models......................................................................................65
Recovering Data with HP 3PAR Recovery Manager.....................................................................65
Preparing for the Recovery Process............................................................................................65
Recovering from Logical Errors with Point-in-Time Recovery............................................................65
Restoring a SQL Instance in an MSCS Environment Using File Copy Restore...............................66
Restoring a Volume in an MSCS Environment Using Volume Restore..........................................66
Recovering All Data with Point-of-Failure Recovery.......................................................................66
Determining Whether You Can Perform a Point-of-Failure Recovery...........................................67
Performing a Point-of-Failure Recovery...................................................................................67
Recovering Data with Auto-Restore............................................................................................68
Performing a File Copy Restore............................................................................................69
Performing a Volume Restore...............................................................................................71
8 Using HP 3PAR Peer Motion Manager Software with Recovery Manager.........72
9 Remote Copy for Recovery Manager...........................................................73
Overview..............................................................................................................................73
How Remote Copy Works........................................................................................................73
Setting Up Remote Copy..........................................................................................................74
Support for Remote Copy Modes and Policies........................................................................74
Support for GeoCluster for Microsoft Windows......................................................................75
Setting Up Remote Copy Volume Groups...................................................................................75
Setting Up a Remote Copy Volume Group for Databases........................................................75
Setting Up a Remote Copy Volume Group for Instances..........................................................75
Recovering a SQL Database from a Remote Copy Backup Server..................................................76
10 Support and Other Resources...................................................................77
Related Documents.................................................................................................................77
Typographical Conventions......................................................................................................77
Advisories..............................................................................................................................78
A Server Virtualization Environments..............................................................79
VMWare and Microsoft Hyper-V Environments............................................................................79
B Troubleshooting........................................................................................80
C Event Messages.......................................................................................82
Contents 5
1 Overview of Recovery Manager
System Requirements
Windows Server Requirements
Microsoft Windows Server 2008, or Windows Server 2008 R2
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, Microsoft SQL
Server 2008 R2, or Microsoft SQL Server 2012.
• 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.
• 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 information and release levels, refer to “Related Documents” (page
77).
Recovery Manager Requirements
• Using a single backup server
• Creating online virtual copies of a database for performing one-click backup
6 Overview of Recovery Manager
• Adding the database 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 43).
• Using the same version of HP 3PAR InForm OS, HP 3PAR VSS Provider, and HP 3PAR Recovery
Manager for SQL Software on all backup and productions systems
• Installing the same version of the InForm CLI software on both the backup and production
systems
• Using the SQLServerWriter service
• Exporting volumes to a host must be in the form of base volumes; exporting snapshot volumes
is not supported.
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.1
• HP 3PAR Recovery Manager Software for SQL Server 4.3
• HP 3PAR Storage System 2.3.1 or higher
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
• 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
• Selective restore of databases from a instance level virtual copy
• Automate the Point of failure restoration process
Running Recovery Manager on a Japanese OS 7
• Attach or detach a database to any SQL server during mounting or unmounting operations
• Restore from virtual copies
• Backups using HP Data Protector or Symantec NetBackup – includes client, master, and media
server
• 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)
• Support for Virtual Machines running on Microsoft Hyper-V Hypervisor and VMware ESX(i)
with SQL.
• Support for iSCSI setup backup server running in a Microsoft Hyper-V and VMware ESX(i)
Virtual Machine.
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
• 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 virtual copies to a Windows host that resides in virtual environment
• Performing a restore in a virtual environment
8 Overview of Recovery Manager
• Customizing date format. Recovery Manager supports date format in month/day/year
• Windows auto-mount feature
Microsoft Volume Shadow Copy Service
Microsoft includes Volume Shadow Copy Service (VSS) in 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.
The HP 3PAR VSS Provider Software for Microsoft Windows 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, 2008 R2, and 2012 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.
Microsoft Volume Shadow Copy Service 9
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.
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.
10 Overview of Recovery Manager
Recovery Manager Layout
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, and 2012. 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.
Recovery Manager Layout 11
2 Installing and Uninstalling HP 3PAR Recovery Manager
for SQL
During the installation, an automated installer verifies the correct user authority before analyzing
all components required for installation. To run the installation, you must have Microsoft 2008 or
R2 administrative privileges and the following required components:
• Microsoft .NET Framework
• Microsoft Visual C++ 2008 Redistributable Package
• HP 3PAR CLI (3.1.1 MU1 or above)
• HP 3PAR VSS Provider 2.1.1 for Microsoft
:
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.
:
For details on system requirements, see the latest HP 3PAR Configuration Matrix.
Installing HP 3PAR Recovery Manager for SQL
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
W2K8_x86Win2008 32-bit
W2K8_x64Win2008 64-bit
5. Select the appropriate package and double-click Setup.exe to launch the installation wizard.
When you first initiate the installation, the system prerequisites are checked and validated to
make sure all of the necessary components required to run HP 3PAR Recovery Manager for
Microsoft SQL are installed. If a necessary component is missing, you are guided through the
steps to perform the necessary installation and the overall progress is shown for completing
12 Installing and Uninstalling HP 3PAR Recovery Manager for SQL
that step in the process. There are two options for using the installation wizard to load the
prerequisite components:
• You can perform the installation by clicking the start/retry button and the required
components are automatically installed one by one where you only have to supply the
correct path for the application.
If necessary, refer to the user guide of the respective components for installation instructions.
• You can perform the installation by clicking on the hyperlink for a given step and you
are then led through the process one step at a time with your confirmation. You have to
click next available install hyperlink if that product is missing on your system.
NOTE: In some cases, you may be prompted to remove a previous version of HP 3PAR
Recovery Manager for Microsoft SQL, the HP 3PAR CLI, or HP 3PAR VSS Provider for Microsoft.
In this case, you need to manually remove the previous version since the older versions are
not automatically removed. If necessary, refer to the user guide of the respective components
for uninstalling instructions.
When all of the necessary components have been installed, you are prompted with a message
to install HP 3PAR Recovery Manager Software for Microsoft SQL.
6. Click Install. The HP 3PAR Recovery Manager Software for Microsoft SQL InstallShield Wizard
interface appears.
7. Click Next to start the wizard, agree to the license, then click Next again. You are asked to
supply the destination folder.
8. Accept the default location, or specify the installation directory for by clicking Change and
choosing an alternate destination. Click Next when you are done to advance to the features
selection.
NOTE: Only use a local drive directory for installation. Do not use a network shared directory
when installing the application.
9. Select the default features, or make any alterations that are necessary before installation. To
change a feature installation option, click the icon feature.
10. Click Next to confirm the feature selections.
11. Click Install to start the installation. A status bar shows the progression as the application is
installed and a concludes with a screen indicating whether the installation has been completed
successfully.
12. When the installation is completed, click Finish.
When the installation is complete, the system gathers and displays the configuration information
in a text file named RMSCfgChk.txt. Use this information to verify all the required installation
components are present on the system.
13. Continue with the remaining messages for the prerequisite interface and the click Close to
complete the installation.
NOTE: If you are using a remote desktop session to install Recovery Manager, log off all
connected remote sessions after the installation is complete to apply the newly added
environmental variables.
NOTE: If you are installing Recovery Manager for SQL on a system also using Symantec
NetBackup service in the background, restart the NetBackup service after Recovery Manager
installation is complete to register the environmental path in the NetBackup service.
Verifying the Installation
1. Log on to the system as system administrator.
Verifying the Installation 13
2. Click Start→Control Panel→Programs and Features.
3. Verify Recovery Manager appears in the Currently installed programs column.
4. Verify the HP 3PAR Recovery Manager for SQL Server icon appears on the desktop when
using the Recovery Manager for Backup Server option to install the application.
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
PortNo
PromoteTimeout
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
Specifies installed features of Recovery ManagerPackageType
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
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
NOTE: The DataFilePath field is created in the registry database only after you launch the
Recovery Manager GUI for the first time.
Upgrading to Recovery Manager 4.3.0 for SQL
You can upgrade to HP 3PAR Recovery Manager 4.3.0 Software for Microsoft SQL Server from
Recovery Manager 4.1.0 or 4.2.0 for SQL.
NOTE: When upgrading, you need to uninstall the existing RMS application along with the
dependent components (e.g. VSS and CLI) before installing the latest version of Recovery Manager
for SQL.
14 Installing and Uninstalling HP 3PAR Recovery Manager for SQL
Upgrading the Production Server
1. Uninstall HP 3PAR Recovery Manager for SQL. For more information, see “Uninstalling HP
Recovery Manager for SQL” (page 15).
2. Install HP 3PAR Recovery Manager 4.3.0 for SQL. For more information, see “Installing HP
3PAR Recovery Manager for SQL” (page 12).
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 or later 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. Uninstall the previous version of 3PAR Recovery Manager for SQL. For more information, see
“Uninstalling HP Recovery Manager for SQL” (page 15).
3. Install HP 3PAR Recovery Manager 4.3.0 for SQL. For more information, see “Installing HP
3PAR Recovery Manager for SQL” (page 12).
4. If you used a different installation folder for Recovery Manager 4.3.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 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. Reregister the
SQL servers if necessary.
3. If you used the Recovery Manager for Backup Server option to install the application, verify
the HP 3PAR Recovery Manager for SQL Server icon appears on the desktop.
4. Verify the registry key. For more information, see “Understanding the Registry” (page 14).
Uninstalling HP Recovery Manager for SQL
1. Log on as the system administrator.
2. Click Start→Control Panel→Programs and Features.
3. Select HP 3PAR Recovery Manager for Microsoft SQL Server.
4. Click Uninstall.
NOTE: After uninstalling 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.
Uninstalling HP Recovery Manager for SQL 15
3 Configuring Recovery Manager
Configuring the SQL Database
When you configure the SQL database:
• 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:
◦ Avoid adding more than one database plus its transaction log files to a volume
◦ Avoid adding files from a database to multiple volumes
:
Be sure to maintain a single database:single 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 executable is 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.
16 Configuring Recovery Manager
Procedure 1
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
:
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 HP 3PAR Recovery Manager for SQL service.
4. Repeat these steps for all production servers and the backup server.
:
Use the same TCP/IP port on all servers for Recovery Manager for SQL.
Changing a Production Server Port from the Backup Server
Procedure 2
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 HP 3PAR 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 25).
• 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:
Procedure 3
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.
Configuring Recovery Manager 17
Procedure 4
1. On the backup server:
• In Windows 2008, click Start→Control Panel→User Accounts and click Manage your
network passwords.
In the Stored User Names and Passwords 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
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:
18 Configuring Recovery Manager
Procedure 5
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 Common 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
9. Ensure the HP 3PAR Storage System connection is good.
Volume Sets
Provider Software.
:
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.
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:
Testing SQL Connectivity 19
Procedure 6
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
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 20).
Troubleshooting SQL Connectivity
Procedure 7
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.
20 Configuring Recovery Manager
2. After you have fixed the SQL configuration on the production server, log onto the backup
server and run the SQL connectivity test again.
:
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.
:
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.
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,
http://msdn.microsoft.com/en-us/library/dd758814.aspx.
Configuring the Host Computer and the HP 3PAR Storage System 21
4 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 or media 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:
SettingBackup Policy Parameter
MS-Windows-NTPolicy type
Clients
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
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.
NOTE: Recovery Manager supports full backups when running on a NetBackup master server.
Recovery Manager also supports user-defined backups when running on a NetBackup client
machine.
22 Configuring Backup Software
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 tool bar 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>.
For more information on installing HP Data Protector, see HP Data Protector documentation.
Configuring HP Data Protector 23
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 supports Master, Client, and Media modes for tape backups.
• 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 14).
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.
24 Configuring Backup Software
5 Using the Recovery Manager GUI
Overview of the Recovery Manager GUI
HP 3PAR Recovery Manager Software for SQL Server provides a Graphical User Interface (GUI)
for managing SQL servers.
The Recovery Manager GUI enables you to create, remove, mount, unmount, back up, and restore
a virtual copy of an individual database or an entire instance (i.e., all databases within an instance).
In addition, the Recovery Manager GUI enables you to configure automatic email notifications,
schedule automatic creation and backup of virtual copies, view event messages, and sync the
backup repository.
The Recovery Manager GUI contains a menu bar, a node tree pane on the left, an informational
pane on the right, and a command log window.
Menu Bar
The menu bar consists of the following menu options:
• Console - allows you to exit the GUI.
• Actions - provides access to virtual copy functionality, includes create, email notification,
mount, policies, register, remove, rescan, restore, refresh, remote copy, and unmount.
• Scheduled Tasks - provides access to the Task Manager.
• About - allows you to access event message descriptions and version information.
Node Tree Pane
After you register the SQL server, the node tree pane displays the SQL server’s instances, databases,
virtual copies, and backup records as a nested tree. Servers configured in a non-cluster environment
are represented by blue icons; servers configured in a cluster environment are represented by
orange icons. For more information about registering SQL servers, see “Registering the Server”
(page 26).
Informational Pane
When a tree node is selected, the informational pane displays detailed information about the node.
If the contents exceed the width of the pane, a scroll bar appears at the bottom of the pane. When
viewing information, you have the option of sorting the content by clicking on the applicable table
headings.
Status and Summary Information
After launching HP 3PAR Recovery Manager for SQL, you can click on the MS SQL node to see
a detailed status and summary of relevant information in a tabular format:
• Sever Name
• Cluster (True/False)
• Version
• No. of Instances
• Instance Names
• Database Count
• Virtual Copy Count for each instance
• Backup Count for each instance
Overview of the Recovery Manager GUI 25
Table management feature like Sorting will be available for each column in the tables.
• Columns having timestamp values in date/time format (MM/dd/yy hh:mm:ss) should be left
justified.
• Columns having numeric values and timestamp values in Unix time (number format), are right
justified.
Opening the Recovery Manager GUI
To open the Recovery Manager GUI, double-click the HP 3PAR Recovery Manager for SQL Server
icon on your desktop or, in the taskbar, click Start→All Programs→HP 3PAR→Recovery Manager
for SQL Server.
Closing the Recovery Manager GUI
To close the Recovery Manager GUI, either close the entire window or select Console→Exit.
Registering the Server
In order for the Recovery Manager GUI to manage your SQL servers, you must register the SQL
Server instances.
To register a SQL instance:
1. Right-click the MS SQL Server node and select Register Server.
NOTE: If your backup server and SQL production servers reside on different networks, the
Recovery Manager for SQL Server Register window might not display all of the available SQL
servers.
In addition, the displayed list of SQL servers can vary depending on factors such as network
traffic, timeouts, routers, lost broadcasted packets, and other network issues.
26 Using the Recovery Manager GUI
2. Depending on whether the Recovery Manager for SQL Server Register window displays the
SQL server you want to register, do the following:
• If the list displays the SQL server you want to register, Recovery Manager discovered the
server instance. Continue as follows:
a. Click the Register checkbox for the server instance.
b. Click OK.
• If the list does not display the SQL server you want to register, you must manually register
the instance. To do so:
a. In the Server Name text box, enter the SQL server name and instance name. Use the
format SQLServerName\instanceName as follows:
◦ If you are registering the default instance, either enter the SQL server name only,
or enter the SQL server name and default, separated by a backslash.
For example, Aztec or Aztec\default.
◦ If you are registering a named instance, enter the SQL server and instance name,
separated by a backslash. Multiple server names can be simultaneously added
separated by comma (,).
If you are registering a named instance, enter the SQL server and instance name,
separated by a backslash.
For example: Aztec\Bld2.
◦ Multiple server names can be simultaneously added by separating server name
or instance name with a comma (,).
NOTE: Do not use the following characters when naming a server:
`~!@#$%^&* ( ) + = _ [ ] { } | \” ‘ ,< > / ?
Do not use the following characters when naming an instance: `~!@%^&* (
) + = [ ] { } | \” ‘ ,< > / ?
Do not use $ as the first character in an instance name and the names are limited
to 16 characters.
b. Click Add. Recovery Manager adds the new SQL server and instance to the list and
automatically selects the Register checkbox for the entry.
c. Click OK to start the registration.
NOTE: Depending on your network traffic, it may take up to several minutes for the Recovery
Manager GUI to register a SQL server instance.
3. Depending on the success of the registration, do one of the following:
• If Recovery Manager displays Update Success in the entry's Status column, Recovery
Manager successfully registered the instance. Click OK; you can now use the Recovery
Manager GUI to manage the instance.
• If Recovery Manager displays UpdateFailed in the entry's Status column, Recovery
Manager was not able to connect to the instance. Continue as follows:
a. To fix any connectivity issues, see “Troubleshooting SQL Connectivity” (page 20).
The instance must pass the SQL connectivity test before the Recovery Manager GUI
can successfully register the instance.
b. Repeat the registration steps for the SQL server until Recovery Manager successfully
registers the instance.
Registering the Server 27
Loading...