Download HP 3PAR Recovery Manager 4.6.0 Software for Microsoft SQL

HP 3PAR Recovery Manager 4.6.0 Software
for Microsoft SQL Server
User Guide
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-97330a
Published: February 2015
Edition: 1.1
© Copyright 2006 – 2014 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.
Revision History
Document part number
Publication date
Edition Notes
QL226-97330
September 2014
Initial publication for 1.0
QL226-97330a
February 2015
Removed the section Support for GeoCluster for
Microsoft Windows.
Contents
1 Overview of Recovery Manager...................................................................7
System Requirements.................................................................................................................7
Windows Server Requirements...............................................................................................7
Windows Server 2008....................................................................................................7
Windows Server 2008 (Enterprise or Datacenter edition), Windows Server 2008 R2 (Enterprise
or Datacenter edition), Windows Server 2012 (Datacenter edition), or Windows Server 2012
R2 (Datacenter edition)....................................................................................................7
Additional System Requirements.............................................................................................7
Recovery Manager Requirements................................................................................................8
Running Recovery Manager on a Japanese or a Chinese OS.........................................................8
Features Supported...................................................................................................................8
Features Not Supported...........................................................................................................10
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
2 Installing and Uninstalling HP 3PAR Recovery Manager for SQL.....................15
Installing HP 3PAR Recovery Manager for SQL...........................................................................15
Verifying the Installation...........................................................................................................16
Understanding the Registry......................................................................................................17
Upgrading to Recovery Manager 4.6.0 for SQL ........................................................................17
Upgrading from Recovery Manager 4.4.0 for SQL, Recovery Manager 4.4.1 for SQL, Recovery
Manager 4.4.2 for SQL, or Recovery Manager 4.5.0 for SQL to Recovery Manager 4.6.0 for
SQL.................................................................................................................................18
Upgrading the Backup Server.........................................................................................18
Upgrading the Production Server.....................................................................................18
Verifying the Upgrade........................................................................................................19
Uninstalling HP Recovery Manager for SQL................................................................................19
3 Configuring Recovery Manager..................................................................20
Configuring the SQL Database.................................................................................................20
Configuring Recovery Manager................................................................................................20
Installation Location............................................................................................................20
Search Path.......................................................................................................................20
Changing the Recovery Manager TCP/IP Port........................................................................20
Changing a Production Server Port from the Backup Server.................................................21
Configuring Recovery Manager Policies................................................................................21
Configuring Mount Functionality..........................................................................................21
Managing SQL Servers across Multiple Active Directory Domains............................................21
Configuring Recovery Manager for Availability Group............................................................21
Grouping Volumes into Autonomic Groups............................................................................23
Domain Sets.................................................................................................................23
Volume Sets..................................................................................................................24
Host Sets......................................................................................................................24
Testing SQL Connectivity..........................................................................................................24
Troubleshooting SQL Connectivity........................................................................................25
Configuring the Host Computer and the HP 3PAR StoreServ Storage System...................................25
4 Configuring Backup Software.....................................................................26
Overview..............................................................................................................................26
Before You Begin....................................................................................................................26
Setting Up Symantec NetBackup...............................................................................................26
Contents
3
Configuring HP Data Protector .................................................................................................27
Requirements ....................................................................................................................27
Setting Up the HP Data Protector Backup Specification............................................................27
Setting Up HP Data Protector Cell Manager Access................................................................28
Configuring Backup Exec.........................................................................................................28
Requirements.....................................................................................................................28
Setting Up the Symantec Backup Exec .................................................................................31
Using Your Backup Software ...................................................................................................32
Using Symantec NetBackup.................................................................................................32
Using HP Data Protector.....................................................................................................32
Using Symantec Backup Exec .............................................................................................32
5 Using the Recovery Manager GUI..............................................................34
Overview of the Recovery Manager GUI...................................................................................34
Menu Bar.........................................................................................................................34
Node Tree Pane.................................................................................................................34
Informational Pane.............................................................................................................34
Status and Summary Information..........................................................................................35
Opening the Recovery Manager GUI........................................................................................35
Closing the Recovery Manager GUI..........................................................................................35
Registering the Server..............................................................................................................35
Updating Registration after Server Modification.....................................................................37
Unregistering a SQL Server Instance..........................................................................................37
Setting the Recovery Manager Policy.........................................................................................38
How Recovery Manager Policies Work.................................................................................38
Numeric-Based Policies..................................................................................................38
Expiration-Based Policies................................................................................................38
Retention Time Restrictions..............................................................................................38
Setting Recovery Manager Policies.......................................................................................39
Modifying the Policy for a Virtual Copy.................................................................................39
Configuring Email Notifications................................................................................................40
Deleting Email Configurations..................................................................................................41
Creating Virtual Copies...........................................................................................................41
How Virtual Copy Creation Works.......................................................................................41
Manually Creating a Virtual Copy........................................................................................41
Creating Remote Virtual Copies...........................................................................................43
How Remote Virtual Copy Works....................................................................................43
Manually Creating a Remote Virtual Copy........................................................................43
Displaying Remote Virtual Copies....................................................................................43
Scheduling Automatic Virtual Copies....................................................................................43
Automating Tasks...................................................................................................................44
Scheduling Automated Tasks with Task Scheduler...................................................................44
Managing Automated Tasks with Task Manager....................................................................45
Prerequisites for Attach and Detach Operation............................................................................45
Mounting a Virtual Copy.........................................................................................................46
Unmounting a Virtual Copy......................................................................................................46
Backing Up a Virtual Copy......................................................................................................46
Manually Creating Backups at the Instance or the Database Level............................................47
Scheduling Automatic Backups of an Instance or a Database...................................................48
Creating a Backup of a Virtual Copy....................................................................................49
Removing a Backup from the Repository....................................................................................49
Restoring Instances, Databases, and Volumes.............................................................................49
Restoring an Instance or a Database with Volume Restore........................................................50
Restoring an Instance or a Database with File Copy Restore.....................................................50
Restoring an Instance or a Database from Backup..................................................................51
4
Contents
Analyzing and Synchronizing the Repository..............................................................................52
Removing a Virtual Copy.........................................................................................................52
Viewing Event Message Descriptions.........................................................................................52
Viewing Online Help..............................................................................................................53
6 Using the Recovery Manager CLI................................................................54
HP 3PAR Recovery Manager for Microsoft SQL Server Command Line Interface (CLI).......................54
Recovery Manager Commands................................................................................................55
HpRmCli Sql analyze.........................................................................................................55
HpRmCli Sql backup..........................................................................................................56
HpRmCli Sql create............................................................................................................57
HpRmCli Sql deletebackup..................................................................................................60
HpRmCli Sql display..........................................................................................................61
HpRmCli Sql listbackup.......................................................................................................62
HpRmCli Sql mount............................................................................................................63
HpRmCli Sql policy............................................................................................................65
HpRmCli Sql portconfig......................................................................................................67
HpRmCli Sql remove..........................................................................................................68
HpRmCli Sql report............................................................................................................68
HpRmCli Sql repository.......................................................................................................69
HpRmCli Sql rescan...........................................................................................................69
HpRmCli Sql restore...........................................................................................................70
HpRmCli Sql setvc..............................................................................................................73
HpRmCli Sql timeconfig......................................................................................................75
HpRmCli Sql unmount.........................................................................................................76
Running Recovery Manager as a Scheduled Job.........................................................................76
Scheduling an Automated Task in Windows...............................................................................76
7 Recovery for Microsoft SQL Server..............................................................78
Microsoft SQL Server Recovery Models......................................................................................78
Recovering Data with HP 3PAR Recovery Manager.....................................................................78
Preparing for the Recovery Process............................................................................................78
Recovering from Logical Errors with Point-in-Time Recovery............................................................79
Restoring an SQL Instance in an Failover Cluster Environment Using File Copy Restore.................79
Restoring a Volume in Failover Cluster Environment Using Volume Restore..................................79
Recovering All Data with Point-of-Failure Recovery.......................................................................80
Determining Whether You Can Perform a Point-of-Failure Recovery...........................................80
Performing a Point-of-Failure Recovery...................................................................................80
Recovering Data with Auto-Restore............................................................................................81
Performing a File Copy Restore............................................................................................82
Performing a Volume Restore...............................................................................................84
Performing volume and file copy restore for availability databases............................................84
8 Coexistence of HP 3PAR Recovery Manager for SQL and HP 3PAR Recovery
Manager for Exchange................................................................................86
Prerequisites...........................................................................................................................86
9 Using HP 3PAR Peer Motion Manager Software with Recovery Manager.........87
10 Using HP 3PAR CLX with Recovery Manager..............................................88
11 Remote Copy for Recovery Manager..........................................................90
Overview..............................................................................................................................90
How Remote Copy Works........................................................................................................90
Setting Up Remote Copy..........................................................................................................91
Support for Remote Copy Modes and Policies........................................................................92
Setting Up Remote Copy Volume Groups...................................................................................92
Setting Up a Remote Copy Volume Group for Databases........................................................92
Contents
5
Setting Up a Remote Copy Volume Group for Instances..........................................................92
Recovering an SQL Database from a Remote Copy Backup Server................................................93
12 Support and Other Resources...................................................................94
Related Documents.................................................................................................................94
Typographical Conventions......................................................................................................94
Advisories..............................................................................................................................95
13 Documentation feedback.........................................................................96
A Server Virtualization Environments..............................................................97
VMware and Microsoft Hyper-V Environments.............................................................................97
B Troubleshooting........................................................................................98
Known Issues.........................................................................................................................98
Troubleshooting......................................................................................................................99
C Event Messages.....................................................................................105
6
Contents
1 Overview of Recovery Manager
System Requirements
Windows Server Requirements
Microsoft Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows
Server 2012 R2
Windows Server 2008
x86-based computer:
•
2 GHz processor
•
2 GB or more RAM
•
40 GB hard disk space
x64-based computer:
•
1.4 GHz processor
•
2 GB or more RAM
•
40 GB hard disk space
Windows Server 2008 (Enterprise or Datacenter edition), Windows Server 2008 R2 (Enterprise
or Datacenter edition), Windows Server 2012 (Datacenter edition), or Windows Server 2012 R2
(Datacenter edition)
•
Either 1.4 GHz (x64) or 1.3GHz (Dual Core) processor
•
2 GB or more RAM
•
32 GB or more hard disk space
Additional System Requirements
•
Microsoft SQL Server 2005, Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2,
Microsoft SQL Server 2012, or Microsoft SQL Server 2014.
For more information on Microsoft SQL Server versions and patches supported, see the Single
Point of Connectivity Knowledge (SPOCK) website: http://www.hp.com/storage/spock
•
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 the instance name in the server-registration
wizard, turn on the corresponding SQL Server Browser Services.
•
Microsoft .NET framework v4.0 or later.
NOTE:
Microsoft .NET framework v3.5 is required for installation on Windows 2012.
•
Microsoft Visual C++ 2010 Redistributable Package.
•
HP 3PAR Recovery Manager for SQL Software license for the HP 3PAR StoreServ 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,
System Requirements
7
or assigning virtual copy space after the base volume is created, see the HP 3PAR Command
Line Interface Reference.
NOTE:
94).
For platform-specific information and release levels, refer to “Related Documents” (page
NOTE: If any of the components mentioned in the additional system requirements are not installed,
HP 3PAR Recovery Manager might not function properly.
Recovery Manager Requirements
•
Backup server
•
Install the same version of HP 3PAR VSS Provider and HP 3PAR Recovery Manager for SQL
Software on all backup and production systems.
•
Install the same version of the HP 3PAR CLI software on both the backup and the production
systems.
•
Ensure that the same StoreServ is registered as a default in production server and backup
server.
•
Instance and all of its database (system and user databases) must reside on volumes belonging
to the same StoreServ.
•
Using the SQL Server VSS Writer service.
Running Recovery Manager on a Japanese or a Chinese OS
CAUTION: For full compatibility 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 or Chinese characters.
•
Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 Japanese
or Chinese OS
•
Microsoft SQL Server 2008 R2, Microsoft SQL Server 2012, or Microsoft SQL Server 2014
Japanese or Chinese
•
HP 3PAR VSS Provider Software 2.4.0
•
HP 3PAR StoreServ Storage System
NOTE: For information about the HP 3PAR StoreServ versions supported, refer the latest
Single Point of Connectivity Knowledge for HP Storage Products (SPOCK) document. To obtain
a copy of this documentation, see http://www.hp.com/storage/spock.
•
HP 3PAR CLI
Features Supported
•
Windows Enterprise or Datacenter edition Server
For detailed OS version support, see the Single Point of Connectivity Knowledge for HP Storage
Products (SPOCK) website: http://www.hp.com/storage/spock.
•
Microsoft SQL Server
For detailed SQL server version support, see the Single Point of Connectivity Knowledge for
HP Storage Products (SPOCK) website: http://www.hp.com/storage/spock.
8
Overview of Recovery Manager
•
Recovery Manager for SQL supports English, Japanese, and Chinese version of Microsoft
Windows operating system
•
Recovery Manager for SQL supports English, Japanese, and Chinese version of Microsoft SQL
Server
For more information on localization support, see Single Point of Connectivity Knowledge for
HP Storage Products (SPOCK) website www.hp.com/storage/spock
•
Support for HP 3PAR OS 3.2.1, HP 3PAR OS 3.1.3, HP 3PAR OS 3.1.2 MU2, and HP 3PAR
OS 3.1.1 MU3
•
Volume Shadow Copy Service supports Full backup type, copy-only backup type for secondary
AlwaysOn databases
•
Virtual copy creation using HP 3PAR VSS Provider Software for Microsoft Windows
•
Virtual Copy creation of Availability Group databases in Microsoft SQL Server 2012
•
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 instance level virtual copy
•
Automate the Point of failure restoration process
•
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, or Symantec Backup Exec
•
Database cloning
•
Restore from backup using HP Data Protector, Symantec NetBackup, or Symantec Backup
Exec
•
Recovery Manager GUI
•
Recovery Manager CLI
•
Volume restore
•
Virtual copy creation of local and remote Microsoft SQL Server instances and databases
•
Failover Cluster environment
•
Remote Copy in synchronous mode or asynchronous periodic mode
•
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)
•
Manage production servers having different versions of SQL Servers with single backup server
•
Support for Virtual Fiber Channel in production server and backup server
•
Support for Virtual Machines running on Microsoft Hyper-V Hypervisor and VMware ESX(i)
with SQL
Features Supported
9
•
Support for backup server and production server on Microsoft Hyper-V and VMware ESX(i)
Virtual Machine in iSCSI environment
•
Support for HP 3PAR Cluster Extension (CLX) configuration
•
Support for coexistence with HP 3PAR Recovery Manager for Exchange software
•
Support for backup server and production server running in VMware VM Direct Environment
•
Support for basic GUID Partition Table (GPT) disks
•
Support for SQL database residing on a mount point (HP 3PAR volume mounted on a system
drive or another HP 3PAR volume)
•
Support for concurrent virtual copy or remote virtual copy creations, concurrent backup jobs,
and concurrent virtual copy or remote virtual copy creation with backup jobs.
NOTE:
◦
Backup of different databases with same policy cannot be taken using Symantec
NetBackup. Concurrent backups with different policies can be taken.
◦
Backup of different databases with same datalist can be taken using HP data protector.
◦
Backup of different databases using Symantec NetBackup, Symantec Backup Exec, or
HP Data Protector can be taken concurrently. For example, Backup of database db1
using Symantec NetBackup and backup of database db2 using HP Data Protector can
execute in parallel.
◦
Backup of different databases with same Device name cannot be taken using Symantec
Backup Exec.
◦
A database backup is not allowed when a backup of its instance is in progress. Similarly,
an instance backup is not allowed when a backup of the database is in progress.
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
NOTE: For information about the versions supported, refer the latest Single Point of Connectivity
Knowledge for HP Storage Products (SPOCK) document. To obtain a copy of this documentation,
see http://www.hp.com/storage/spock.
Features Not Supported
•
Microsoft SQL Server offline backup
•
VSS backup types “Incremental,” “Differential,” and “Log”
•
All backup tools except HP Data Protector, Symantec NetBackup, and Symantec Backup Exec
•
Access to HP 3PAR StoreServ Storage System via SSH
•
Taking a snapshot of the SQL servers created with SQL Server Authentication set to Mixed-mode
authentication mode
•
Taking a snapshot of a database residing on a network mapped volume
•
Virtual copy ownership transferring
For example, you can remove virtual copies only if you created them, and you can unmount
virtual copies only if you mounted them.
•
10
Taking a snapshot of an instance or a database that resides on dynamic disks
Overview of Recovery Manager
•
Mounting virtual copies to a Windows Fibre channel (FC) based host that resides in virtual
environment
•
Performing a restore on a Windows Fibre channel based host that resides in virtual environment
•
Performing a mount, an unmount, or a restore function in RDM (Raw Device Mapping) disk
and passthrough disk
•
Customizing date format
Recovery Manager supports date format in month/day/year
•
Windows auto-mount feature if the database or an instance LUN is on a mountpoint residing
on a mountpoint volume.
NOTE:
•
•
Virtualization support
Windows Hyper-V:
◦
Only iSCSI LUNs are supported.
◦
Pass-through Disks are not supported.
◦
Virtual fiber channel is supported.
VMware ESX
◦
Only iSCSI and VM Direct path is supported.
◦
Raw device mapping is not supported.
Microsoft Volume Shadow Copy Service
Microsoft includes Volume Shadow Copy Service (VSS) in Windows to simplify the enterprise’s
storage environment. VSS provides a framework for creating a point-in-time copy of either a single
volume or multiple volumes.
Microsoft Windows Server 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.
VSS coordinates between Requestors (backup applications such as Recovery Manager), Writers
(applications in windows services such as Microsoft SQL Server) and Providers (components that
create the shadow copies).
VSS Component
VSS Component Description
Requestor
The requestor is the backup software that initiates the
creation of the shadow copy.
Writer
The writer is any application software that participates in
the shadow copy process and whose files and data are
included in the process.
Provider
The provider is the storage technology that does the actual
shadow copy.
Microsoft Volume Shadow Copy Service
11
Supported VSS Components
Requestor:
•
Recovery Manager
•
Symantec NetBackup for Microsoft Windows
•
HP Data Protector for Microsoft Windows
•
Symantec Backup Exec for Microsoft Windows
Writer:
•
Microsoft SQL Server 2005, 2008, 2008 R2, and 2012 with SQL Server VSS Writer
NOTE: For platform-specific release levels, refer the latest Single Point of Connectivity Knowledge
for HP Storage Products (SPOCK) document. To obtain a copy of this documentation, see http://
www.hp.com/storage/spock.
How HP 3PAR VSS Software Works with Microsoft SQL Server
Figure 1 HP 3PAR VSS provider software for Microsoft Windows operation overview
1.
2.
3.
4.
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.
Volume Shadow Copy service communicates with SQL Writer on the Microsoft SQL Server to
flush the current log files to disk and suspend any writes to the transaction log files and to the
database file. However, HP 3PAR VSS Software allows read-only access so the client can
access any data that is already in the SQL Server database.
Volume Shadow Copy service communicates with the provider to initiate the shadow copy
process for the disk volumes that contain the Microsoft SQL Server data.
Volume Shadow Copy service 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.
12
Overview of Recovery Manager
5.
6.
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.
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
Figure 2 Centralized Backup Configuration
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
An SQL Server can be a standalone server or a clustered server. An SQL Server version must
be 2005, 2008, 2008 R2, 2012, or 2014. 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 StoreServ
Storage System.
14
Overview of Recovery Manager
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 start the installation, you must have Microsoft 2008,
Microsoft 2008 R2, Microsoft 2012, or Microsoft 2012 R2 administrative privileges and the
following required components:
•
Microsoft .NET Framework v4.0 or later
•
Microsoft Visual C++ 2010 Redistributable Package
•
HP 3PAR CLI 3.1.3 or later
•
HP 3PAR VSS Provider 2.4.0 for Microsoft
NOTE: For details on system requirements, refer the latest Single Point of Connectivity Knowledge
for HP Storage Products (SPOCK) document. To obtain a copy of this documentation, see http://
www.hp.com/storage/spock.
CAUTION: Do not install Recovery Manager on a clustered drive. If you continue with the
installation, Recovery Manager allows you to proceed with the installation, but after the install is
complete, the process stops responding and evicts the clustered disk.
NOTE: The active StoreServ (volumes on which SQL database or Instance reside) must be
configured as a default StoreServ in HP 3PAR VSS Provider.
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.
3.
4.
Insert the Recovery Manager CD.
Open Windows Explorer window and click the CD-ROM drive to view the files on the CD.
Select the package corresponding to your OS version.
Table 1 Operating system packages
5.
Operating System
Package
Win 2008 32-bit
RMS_x86
Win 2008 64-bit/ Win 2008 R2/ Win 2012/ Win
2012 R2
RMS_x64
Select the appropriate package and double-click Setup.exe to launch the installation wizard.
When the installation begins, the system prerequisites are validated to ensure that all the
components required to run HP 3PAR Recovery Manager for Microsoft SQL are installed. If
any of the required component is missing, you are guided through the steps to perform the
Installing HP 3PAR Recovery Manager for SQL
15
necessary installation and the overall progress is shown for completing 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.
7.
8.
Click Install. The HP 3PAR Recovery Manager Software for Microsoft SQL InstallShield Wizard
interface appears.
To start the wizard, click Next. Accept the license agreement and then click Next. You are
asked to supply the destination folder.
Accept the default location, or to specify the installation directory, click Change and choose
an alternate destination. Click Next after you provide the destination 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 installation progress. A message
appears to indicate whether the installation is completed successfully.
12. When the installation is completed, click Finish.
When the installation is complete, the system displays the configuration information in a text
file 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 then 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 HP 3PAR Recovery Manager for SQL on a system which is 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.
16
Log on to the system as system administrator.
Installing and Uninstalling HP 3PAR Recovery Manager for SQL
2.
3.
4.
Click Start→Control Panel→Programs→Programs and Features.
Verify Recovery Manager appears in the Currently installed programs column.
Verify that the HP 3PAR Recovery Manager for Microsoft 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
Name
Value
AnalyzeInterval
Interval in minutes between automatic synchronization of
the repository with HP 3PAR. The default interval is 60
minutes.
BackupTimeout
Backup process timeout value in minutes to confirm that
NetBackup has received the backup request.
Build
Build number of the installed version of Recovery Manager
for SQL.
DataFilePath
Location of the XML repository.
InstallPath
HP 3PAR Recovery Manager for SQL installation path.
LogFilePath
Tracing log files.
PackageType
Specifies installed features of Recovery Manager.
TraceHistory
Number of trace files to keep before deleting.
TraceLevel
Trace level for the log file.
TraceLog
Information used to generate the trace file name.
TraceLogSize
Size of the log files.
PortNo
Port used by Recovery Manager for SQL. PortNo is set to
9932 by default.
PromoteTimeout
Time interval in seconds to monitor the status of volume
restore operation.
Version
Current version of HP 3PAR Recovery Manager for
Microsoft SQL Server.
VolumeRestoreMaxRetry
The maximum number of retries to find the restored disks
after a volume restore operation.
NOTE: The DataFilePath field is created in the registry database only after you launch the
Recovery Manager GUI for the first time.
NOTE: An installation log file, called RMS_4.6_InstallerLog.txt, is created in the
%HOMEPATH% folder for troubleshooting purposes.
Upgrading to Recovery Manager 4.6.0 for SQL
This section provides instructions for upgrading HP 3PAR Recovery Manager Software for Microsoft
SQL from version 4.4.0, version 4.4.1, version 4.4.2, or version 4.5.0 to version 4.6.0.
Understanding the Registry
17
NOTE: When upgrading to Recovery Manager 4.6.0 from any of its earlier versions, SQL Server
2012 availability database properties are not updated. It requires RESCAN or re-registration of
the SQL server.
Upgrading from Recovery Manager 4.4.0 for SQL, Recovery Manager 4.4.1 for
SQL, Recovery Manager 4.4.2 for SQL, or Recovery Manager 4.5.0 for SQL to
Recovery Manager 4.6.0 for SQL
You can upgrade to HP 3PAR Recovery Manager 4.6.0 Software for Microsoft SQL Server from
Recovery Manager 4.4.0 for SQL, Recovery Manager 4.4.1 for SQL, Recovery Manager 4.4.2
for SQL, or Recovery Manager 4.5.0 for SQL Server.
Upgrading the Backup Server
1.
2.
On each HP 3PAR Recovery Manager for Microsoft SQL Backup Server:
•
Stop HP 3PAR Recovery Manager for Microsoft SQL service from Windows Services
Panel.
•
Stop HP 3PAR VSS Provider service from Windows Services Panel.
•
Close the HP 3PAR Recovery Manager for Microsoft SQL GUI and CLI.
•
Close windows event viewer window.
•
Ensure that no other user is logged on to the system and managing the HP 3PAR Recovery
Manager for Microsoft SQL application.
•
Disable any HP 3PAR Recovery Manager for Microsoft SQL task from Windows Scheduled
Tasks.
To backup the repository, move the folder C:\Program Files\3par\RM\SQL\Data and
all directories and files under it to another location.
TIP:
The hprmcli sql repository command provides the path of the repository.
3.
4.
5.
Uninstall HP 3PAR VSS Provider from the Control Panel. Reboot the server, if required.
Uninstall HP 3PAR CLI from the Control Panel. Reboot the server, if required.
Run Setup.exe.
a. Install HP 3PAR CLI, HP 3PAR VSS Provider.
b. While registering HP 3PAR StoreServ, if you are prompted to accept the certificate, click
YES and proceed.
c. While upgrading to HP 3PAR Recovery Manager for Microsoft SQL 4.6.0, user is prompted
for upgrade confirmation. Confirming to do so will uninstall the older version and install
HP 3PAR Recovery Manager for Microsoft SQL 4.6.0 on the backup server.
d. Reboot the server, if required.
6.
Verify that old virtual copies can be seen from the HP 3PAR Recovery Manager for Microsoft
SQL GUI or CLI.
Register the SQL Servers again, if required.
Enable the scheduled tasks from Windows Scheduled Tasks.
7.
8.
Upgrading the Production Server
1.
18
On each HP 3PAR Recovery Manager for Microsoft SQL Production Server:
•
Stop HP 3PAR Recovery Manager for Microsoft SQL service from Windows Services
Panel.
•
Stop HP 3PAR VSS Provider service from Windows Services Panel.
Installing and Uninstalling HP 3PAR Recovery Manager for SQL
2.
•
Close windows event viewer window.
•
Ensure that no other user is logged on to the system and managing the HP 3PAR Recovery
Manager for Microsoft SQL application.
•
Uninstall HP 3PAR VSS Provider from the Control Panel.
•
Uninstall HP 3PAR CLI from the Control Panel. Reboot the server, if required.
Run Setup.exe.
a. Install HP 3PAR CLI, HP 3PAR VSS Provider.
b. While registering HP 3PAR StoreServ, if you are prompted to accept the certificate, click
YES and proceed.
c. While upgrading to HP 3PAR Recovery Manager for Microsoft SQL 4.6.0, user is prompted
for upgrade confirmation. Confirming to do so will uninstall the older version and install
HP 3PAR Recovery Manager for Microsoft SQL 4.6.0 in backup server.
d. Reboot the server, if required.
NOTE: For Microsoft SQL Server Cluster production upgrade, first perform the upgrade on the
passive nodes. Failover and move the SQL server group in the cluster from the current active node
to any of the upgraded passive nodes. Then, perform the upgrade on the remaining node.
Verifying the Upgrade
1.
2.
3.
4.
Verify HP 3PAR Recovery Manager for SQL is listed as a service that is currently running.
Check whether you can see the previously created virtual copies in the GUI. Register the SQL
servers again, if necessary.
If you used the Recovery Manager for Backup Server option to install the application, verify
that the HP 3PAR Recovery Manager for Microsoft SQL Server icon appears on the desktop.
Verify the registry key. For more information, see “Understanding the Registry” (page 17).
Uninstalling HP Recovery Manager for SQL
1.
2.
3.
4.
Log on as the system administrator.
Click Start→Control Panel→Programs and Features.
Select HP 3PAR Recovery Manager for Microsoft SQL Server.
Click Uninstall.
NOTE: After uninstalling Recovery Manager, virtual copies and scheduled tasks still reside
locally in the Data folder as well as on the system. You can remove virtual copies and scheduled
tasks later, if desired.
Uninstalling HP Recovery Manager for SQL
19
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.
CAUTION:
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:
<system drive>:\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, HP 3PAR 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 the desired port number, run the Recovery Manager CLI HpRmCli Sql portconfig
command.
For example, to change the port number to 9999, use: HpRmCli Sql 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, then
you cannot then access the production servers to change their ports.
3.
4.
From the Windows Service console, restart the HP 3PAR Recovery Manager for SQL service.
Repeat these steps for all production servers and the backup server.
NOTE:
20
Use the same TCP/IP port on all servers for Recovery Manager for SQL.
Configuring Recovery Manager
Changing a Production Server Port from the Backup Server
1.
On the backup server, run the following Recovery Manager CLI command:
HpRmCli Sql portconfig -s <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 34).
•
To use the Recovery Manager CLI to set database policies, see “Using the Recovery Manager
CLI” (page 54), for information about using the HpRmCli Sql 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 2008, click Start→Control Panel→User Accounts and click Manage your
network passwords.
In the Stored User Names and Passwords dialog box, click Add.
•
2.
In Windows 2008 R2, click Start→Control Panel→User Accounts and then click Manage
your credentials→Add a Windows credential.
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:
*.<domain_name>
3.
4.
Enter the appropriate login and password.
Repeat these steps for all SQL Server domains in the Recovery Manager configuration.
NOTE:
Make sure that you add the FQDN while registering the server.
Configuring Recovery Manager for Availability Group
HP 3PAR Recovery Manager for SQL supports Microsoft SQL Server 2012 Availability Group
databases. In this configuration, each availability group replica is connected to only one StoreServ
and the StoreServ can be same or different from that of other replicas.
Configuring Recovery Manager
21
Figure 3 HP 3PAR Recovery Manager for SQL with Two Availability Replica Nodes
In Figure 3 (page 22), HP 3PAR Recovery Manager for SQL is configured with two availability
replica nodes. The configuration can be extended up to five replica sites, one primary replica node
and up to four secondary replica nodes. Virtual copy can be created for availability database on
primary replica node only through the RMS backup server 1 and virtual copy for availability
database on secondary replica node can be created only through RMS backup server 2. If both
primary and secondary replica nodes are connected to same StoreServ, then any backup server
can be used to create virtual copy.
NOTE: Connecting more than one StoreServ to backup server or production server is not supported
and must be set as a default StoreServ for the HP 3PAR hardware provider.
22
Configuring Recovery Manager
Before you start configuring Recovery Manager for Availability Group:
•
Make sure all the prerequisites for Availability Group are met before discovering Availability
Group in the Recovery Manager for SQL. For list of prerequisites, see http://
msdn.microsoft.com/en-us/library/ff878487%28v=SQL.110%29.aspx.
•
Make sure all the nodes participating in the Availability Group are part of the same Windows
cluster and user has a Domain account and is an administrator for the system.
WARNING!
•
HP 3PAR Recovery Manager for SQL does not support Availability Group databases received
from multiple StoreServs.
•
Do not make any change in the Availability Group configuration while HP 3PAR Recovery
Manager for SQL operations are in progress. Otherwise, the results may be unpredictable.
•
Remote copy is not supported for availability databases.
•
HP 3PAR Recovery Manager for SQL does not support Availability databases when any of
the Availability Group replicas is a part SQL cluster.
NOTE: If there is any change in the configuration of Availability Group, user must perform a
manual rescan in Recovery Manager for SQL.
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 StoreServ Storage System domain set. This configuration allows to use just one Recovery
Manager backup server to manage all 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 HpRmCli Sql mount -ts. For more information about the command, see
“HpRmCli Sql mount” (page 63)
•
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 Operating System Software 3.1.1 MU3 or later.
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 created as in step 4.
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.
Configuring Recovery Manager
23
9.
Ensure the HP 3PAR StoreServ Storage System connection is good.
NOTE: For more information on HP 3PAR CLI commands, see the HP 3PAR 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 one of the following:
◦
one database and its log files
◦
one instance and its related files
NOTE:
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
To verify that your SQL instances are reachable after you install and configure Recovery Manager
on the backup server and all of the production servers:
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
24
Configuring Recovery Manager
4.
Click Connect. A window appears as follows:
If you are able to connect, the installation and configuration is complete.
If the connection cannot be made, you must check the SQL configuration. For more information,
see “Troubleshooting SQL Connectivity” (page 25).
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 selected.
2.
•
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.
After you have checked 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.
3.
Verify that the SQL Server Browser service is running. Start the service if it is not running.
Configuring the Host Computer and the HP 3PAR StoreServ Storage System
For information about configuring the HP 3PAR StoreServ Storage System to communicate with the
host computer, see the HP 3PAR StoreServ Storage Concepts Guide (OS 3.1.3) and the HP 3PAR
Command Line Interface Administrator’s Manual.
NOTE: The HP 3PAR StoreServ Storage System source volumes used by Recovery Manager must
be base volumes. Recovery Manager cannot use physical copies or virtual copies as source volumes.
Configuring the Host Computer and the HP 3PAR StoreServ Storage System
25
4 Configuring Backup Software
Overview
HP 3PAR Recovery Manager Software for Microsoft SQL Server can be used with either HP Data
Protector, Symantec NetBackup, or Symantec Backup Exec 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
a backup client or a backup media on the backup server.
NOTE: For information about the supported versions of HP Data Protector, Symantec NetBackup,
and Symantec Backup Exec; refer the latest Single Point of Connectivity Knowledge for HP Storage
Products (SPOCK) document. To obtain a copy of this documentation, see http://www.hp.com/
storage/spock.
Table 3 (page 26) provides details of possible server combination scenarios for coexistence of
Recovery Manager for SQL and backup applications such as HP Data Protector, Symantec
NetBackup, or Symantec Backup Exec.
Table 3 Coexistence of Recovery Manager for SQL and Backup Applications
Recovery Manager for SQL
+ backup application
Scenario
Server 1 configuration
Server 2 configuration
Recovery Manager for SQL 1
and Symantec NetBackup
Recovery Manager for SQL +
Symantec NetBackup Client
Symantec NetBackup Media Server +
Symantec NetBackup Master Server*
2
Recovery Manager for SQL +
Not Applicable
Symantec NetBackup Client +
Symantec NetBackup Master Server
+ Symantec NetBackup Media Server
3
Recovery Manager for SQL +
Symantec NetBackup Client +
Symantec NetBackup Master Server
Symantec NetBackup Media Server
4
Recovery Manager for SQL +
Symantec NetBackup Client +
Symantec NetBackup Media Server
Symantec NetBackup Master Server
Recovery Manager for SQL 1
and HP Data Protector
Recovery Manager for SQL + HP
Data Protector Client
HP Data Protector Cell Manager
2
Recovery Manager for SQL + HP
Data Protector Client + HP Data
Protector Cell Manager
Not applicable
Recovery Manager for SQL 1
and Symantec Backup Exec
2
Recovery Manager for SQL +
Symantec Backup Exec Remote Media
Symantec Backup Exec Remote Agent Server
for Windows + Symantec Backup
Exec Admin Console
Recovery Manager for SQL +
Symantec Backup Exec Remote
Media Server**
Not Applicable
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.
26
Configuring Backup Software
To configure Symantec NetBackup to function with Recovery Manager for SQL, set the following
parameters during the configuration process:
Backup Policy Parameter
Setting
Policy type
MS-Windows-NT
Clients
Select the machine on which the Recovery Manager Backup
Server component is installed.
Add the client to backup policy by entering NetBIOS name.
Collect disaster recovery information for Bare Metal Restore Ensure that this option is not selected.
Type of backup
Full backup
Starting times for backups
Activate all the time slots:
• 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.
•
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 the changes to take effect.
•
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.
•
If Recovery Manager for SQL is running under the workgroup, then the client added in the
Symantec NetBackup Policy supports only host name. Fully Qualified Domain Name (FQDN)
is not supported.
Configuring HP Data Protector
Requirements
•
HP Data Protector Software
•
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.
Configuring HP Data Protector
27
7.
8.
9.
Click Manual add...
Select Windows filesystem and click Next.
Enter the appropriate client system, mount point, and description. HP recommends:
Client system
<server_used_as_backup_client>
Mount point
C:
Description
default
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 HpRmCli Sql 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
NOTE:
HP Data Protector Cell Manager 8.0 is not supported on Microsoft Windows x86 hosts.
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 menu, select Users.
3. Under the Users folder in the left pane, select admin→SYSTEM.
4. In the Client system menu on the General tab in the right pane, select <Any>.
For more information on installing HP Data Protector, see HP Data Protector documentation.
Configuring Backup Exec
Requirements
•
Symantec Backup Exec Media server on HP 3PAR Recovery Manager for SQL backup server
1. Symantec Backup Exec software
2. Symantec Backup Exec Media server user name and password must be same as the HP
3PAR Recovery Manager for SQL Backup Server, or you must add the current user to
Backup Exec.
•
Symantec Backup Exec Remote Media server
1. Symantec Backup Exec Remote media server must be installed on the same domain.
2. HP 3PAR Recovery Manager for SQL backup server must be installed with Symantec
Backup Exec remote agent for windows and Symantec Backup Exec administrator console.
To do this:
a. Install media server on Recovery Manager for SQL production server.
b. Install remote agent from production server to the backup server.
c. Install Symantec Backup Exec remote administrator console on the backup server.
3.
28
From the Symantec Backup Exec media server, Symantec Backup Remote administrator
console install path must be accessible with network path. For example, if Symantec
Configuring Backup Software
4.
Backup Exec is installed on C:\Program Files\Symantec\Backup Exec then
\\hostname\c$\ Program Files\Symantec\Backup Exec must be accessible
To support Symantec Backup Exec Remote media server, HP 3PAR Recovery manager
for SQL must be running with domain administrator privileges. To run the HP 3PAR
Recovery manager for SQL with domain administrator privileges:
a. To open the services, select Windows→Control Panel→Administrative Tools→Services.
b. Locate and double-click HP 3PAR Recovery Manager for SQL service.
Figure 4 HP 3PAR Recovery Manager for SQL service
c.
Select Log On tab.
Configuring Backup Exec
29
Figure 5 HP 3PAR Recovery Manager for SQL Properties
d.
30
Select This account. Enter the domain administrator username and password.
Configuring Backup Software
Figure 6 HP 3PAR Recovery Manager for SQL Properties Account
e.
Click Apply and then select OK. You must restart the service when asked for.
NOTE: These changes must be done on all the servers wherever the HP 3PAR Recovery
Manager for SQL is running.
•
Symantec Backup Exec
•
Media server user name and password must be same as the Backup Server, or you must add
the current user to Backup Exec
Setting Up the Symantec Backup Exec
NOTE: To use Symantec Backup Exec with Recovery Manager, either remote administrator
console or typical setup (that is mediaserver, administrator console) must be installed on Recovery
Manager for SQL backup server. Device must be configured in Backup Exec for backup.
1.
2.
3.
Open Symantec Backup Exec administrator console.
From the tool bar, select the device you want to backup.
To configure the device for backup, follow the onscreen instructions.
Configuring Backup Exec
31
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 backup software to monitor
restore progress.
•
For more information about using CLI commands with your backup software, see HpRmCli
Sql backup, HpRmCli Sql deletebackup, HpRmCli Sql listbackup, and HpRmCli
Sql restore in “Using the Recovery Manager CLI” (page 54).
•
For more information about using your backup software to back virtual copies up to media,
see “Backing Up a Virtual Copy” (page 46).
•
For more information about using your backup software to restore virtual copies from media,
see “Restoring Instances, Databases, and Volumes” (page 49).
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.
•
When you are using NetBackup to back up to media or restore from media, 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: 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.
Using Symantec Backup Exec
Symantec Backup Exec supports Media server and remote administrator console for backups.
When using the Backup Exec to backup to media or restore for media, monitor the progress using
the administrator console.
32
Configuring Backup Software
NOTE:
While performing concurrent backup operations:
•
Backup of different databases with different policies is allowed while using Symantec
NetBackup.
•
Backup of different databases is allowed, while using HP Data Protector or Symantec Backup
Exec.
•
Backups of different databases can be taken concurrently using Symantec NetBackup, HP
Data Protector, or Symantec Backup Exec. For example, backup of database db1 using
Symantec NetBackup and database db2 using HP Data Protector can execute simultaneously.
Using Your Backup Software
33
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, or restore
a virtual copy of an individual database or an entire instance (that is, 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
synchronize the backup repository.
NOTE: Only NetBIOS names should be used when specifying values for any server type such
as production server, backup server, mount server, target server, media server, master server.
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.
•
Help - This contains the following sub menu items:
◦
Event Messages - This provides the descriptions for event messages that may be generated
during Recovery Manager operations.
◦
Help - This is available for quickly accessing relevant information.
◦
About - This provides an About HP 3PAR Recovery Manager screen which gives the
product 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 35).
NOTE: An Availability Group database is indicated by
icon in the Node Tree Pane. For an
Availability Group database, Availability Group Database Name and its node are displayed in
the database detail pane. This information is also displayed in the detail pane for the Virtual Copies
and Backup Copies created for the Availability Group databases.
Informational Pane
When a tree node is selected, the informational pane displays detailed information about the node.
If the content exceeds the width of the pane, a scroll bar appears at the bottom of the pane. When
viewing information, to sort the content click the applicable table headings.
34
Using the Recovery Manager GUI
Status and Summary Information
After launching HP 3PAR Recovery Manager for SQL, you can click the MS SQL Server node to
see a detailed status and summary of relevant information in a tabular format:
•
Sever Name
•
Cluster (True/False)
•
Version
•
Number of Instances
•
Instance Names
•
Database Count
•
Virtual Copy Count for each instance
•
Backup Count for each instance
Table management features like Sorting are available for each column in the table.
•
Columns having timestamp values in date/time format (MM/dd/yy hh:mm:ss) are 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 Microsoft
SQL Server icon on your desktop. Alternatively, in the taskbar, click Start→All
Programs→3PAR→Recovery Manager for SQL Server.
NOTE: If only production server is installed, you might not see any icons on the desktop or any
menu in the start menu of windows.
Closing the Recovery Manager GUI
To close the Recovery Manager GUI, do one of the following:
•
Select Console→Exit.
•
Close the entire window.
Registering the Server
For the Recovery Manager GUI to manage SQL servers, the SQL Server instances must be registered.
When registering an SQL server instance in the Recovery Manager GUI, sysadmin role is required.
To configure the sysadmin role before registering the SQL server instance in the Recovery Manager
GUI:
1. Connect to the SQL instance through the SQL Management Studio.
2. Select the Security option and click NT AUTHORITY\SYSTEM from Login option.
3. The Login properties - NT AUTHORITY\SYSTEM window appears.
4. Click Server Roles, select sysadmin role and click OK.
Opening the Recovery Manager GUI
35
5.
Register the SQL server again with HP 3PAR Recovery Manager Software for SQL.
To register an SQL instance:
1. Right-click the MS SQL Server node and select Register Server.
NOTE: If backup server and SQL production servers reside on different networks, the HP
3PAR Recovery Manager for Microsoft SQL Server Register window may 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.
NOTE: In Microsoft SQL 2008, Microsoft SQL 2012, or Microsoft SQL 2014, the sysadmin
role is not selected for NT account (NT AUTHORITY\SYSTEM ), by default. For HP 3PAR
Recovery Manager for SQL to work, user must explicitly configure the sysadmin role if it is not
enabled.
2.
Depending on whether the HP 3PAR Recovery Manager for Microsoft SQL Server Register
window displays the SQL server to be registered, do one of the following:
•
If the list displays the SQL server to be registered, Recovery Manager discovered the
server instance, Do as follows:
a. Select the Register checkbox for the server instance.
b. Click OK.
•
If the list does not display the SQL server to be registered, you must manually register the
instance. To manually register the instance:
1. In the Server Name text box, enter the SQL server name and instance name. Use the
format SQLServerName\instanceName as follows:
◦
To register 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.
◦
To register a named instance, enter the SQL server and instance name, separated
by a backslash. Multiple server names can be added simultaneously by
seperating server names with a comma (,).
To register a named instance, enter the SQL server and instance name, separated
by a backslash.
36
Using the Recovery Manager GUI
For example: Aztec\Bld2.
◦
Multiple server names can be added simultaneously 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.
2.
3.
Click Add. Recovery Manager adds the new SQL server and instance to the list and
automatically selects the Register checkbox for the entry.
Click OK to start the registration.
NOTE: Depending on the 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 Update Failed in the entry's Status column, Recovery
Manager was not able to connect to the instance.
a. To fix any connectivity issues, see “Troubleshooting SQL Connectivity” (page 25).
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.
Updating Registration after Server Modification
If configuration of registered instance is modified (for example, a new database is created under
that instance), the instance must be rescanned to update the registration.
To rescan an instance:
1. Right-click the MS SQL Server node.
2. Select Rescan Server Configuration.
If Availability Group databases are configured on Microsoft SQL Server 2012, rescan is
recommended in following instances:
•
There is a change in Availability Group configuration.
•
An SQL Server is migrated to SQL 2012 from its previous versions.
NOTE: When a database is removed from Availability Group, running the RESCAN command
will remove Availability Group information from the database information list.
Unregistering a SQL Server Instance
To remove a server instance from the list of registered servers:
1. Right-click the MS SQL Server node.
2. Select Register Server.
3. Clear the Register checkbox for the server instance you are deleting.
Unregistering a SQL Server Instance
37
4.
Click OK.
Setting the Recovery Manager Policy
Recovery Manager applies policy settings at the instance level; therefore, each instance can have
its own policy. In addition, you can configure individual virtual copies with their own policy settings.
How Recovery Manager Policies Work
The Recovery Manager policy-setting feature allows you to:
•
Specify either a numeric-based or expiration-based policy for each instance and database on
a selected SQL server
•
Specify a retention time during which the instance or database and its virtual copies cannot
be removed (if you have a Virtual Lock license)
NOTE: Modifications made to an existing policy are not retroactive. Virtual copies created under
a previous policy (whether numeric or expiration-based) retain the policy setting under which they
were created.
Numeric-Based Policies
If you specify a numeric-based policy, you can modify the maximum number of virtual copies
allowed per database and per instance. By default, Recovery Manager allows you to create a
maximum of 10 virtual copies per database and 10 virtual copies per instance.
The numeric-based policy also enables you to set Recovery Manager to automatically remove the
oldest virtual copy for each database and instance, after the maximum limit of virtual copies is
reached, before creating a new virtual copy. If you do not choose to automatically remove virtual
copies when required to create a new virtual copy, you must manually delete old virtual copies
before you can create new copies.
NOTE: A virtual copy must be unmounted to be removed. If the oldest virtual copy is mounted,
a new virtual copy is not created until the oldest virtual copy is unmounted.
Expiration-Based Policies
If you choose an expiration-based policy, you can set Recovery Manager to automatically remove
virtual copies after a specified period of time has elapsed.
If you specify an expiration time for a remote virtual copy:
•
If Remote Copy is set up in periodic mode, Recovery Manager sets the expiration time for the
remote virtual copy on the Remote Copy backup server.
•
If Remote Copy is set up in synchronous mode, Recovery Manager sets the expiration time for
both the virtual copy on the primary server and the remote virtual copy on the Remote Copy
backup server.
For more information, see the HP 3PAR Remote Copy Software User’s Guide.
The expiration-based policy option is only available if HP 3PAR StoreServ Storage System is running
HP 3PAR Operating System Software 3.1.1 MU3 or later and a valid Virtual Lock license is available
on the storage system.
Retention Time Restrictions
If you have a Virtual Lock license, you can set a retention time for virtual copies. The instance or
the database and the associated virtual copies created within the retention period cannot be
removed during the retention period.
38
Using the Recovery Manager GUI
When setting a retention time:
•
You must have a Virtual Lock license to set retention times.
•
The minimum retention time is 1 hour; the maximum is 43,800 hours/1,825 days (5 years).
The default maximum retention time is 336 hours (14 days).
•
You can set a retention time for both numeric-based and expiration-based policies.
•
The retention time cannot exceed the default maximum retention time set for the Storage Server.
•
The retention time cannot be longer than the expiration time (if the policy is expiration-based).
•
If you create a remote virtual copy and Remote Copy is set up in asynchronous periodic mode,
the retention time is applied to the remote copy on the Remote Copy backup server only. If
Remote Copy is set up in synchronous mode, the retention time is applied to both the remote
copy on the Remote Copy backup server and the virtual copy on the primary server.
•
After the retention time is set, it can be increased, but it cannot be removed or reduced.
Setting Recovery Manager Policies
1.
2.
In the node tree pane, right-click the instance you want to configure and select Policy.
Depending on whether you want to set a maximum number of copies or you want to set an
expiration time frame, do one of the following in the Policy Setup dialog box:
To set:
Follow these steps:
Maximum number of virtual copies 1. Select the Numeric radio button.
2. In the Maximum Instance level Virtual Copies and Maximum Database
level Virtual Copies text boxes, enter the desired maximum for each as a
number between 1 and 500.
3. To remove the oldest virtual copy each time a copy above the maximum
is created, select the Remove the oldest Virtual Copies checkbox.
To keep the oldest virtual copy (and therefore prevent new virtual copies
from being made after the maximum number is reached), clear the Remove
the oldest Virtual Copies checkbox.
Expiration time frame for virtual
copies
3.
1. Select the Expiration radio button.
2. In the Default Expiration Time text box, enter the number of hours or days
after which you want Recovery Manager to remove each virtual copy. The
maximum expiration period is 43800 hours/1825 days (5 years).
3. In the list, select either Hours or Days.
To modify the default retention time for the instance and its virtual copies, enter the number
of hours or days you want to keep the instance and its contents.
The minimum retention period is 1 hour; the maximum is 43,800 hours/1,825 days (5 years).
For more information about retention time restrictions, see “How Recovery Manager Policies
Work” (page 38).
4.
Click Finish.
The virtual copy policy is effective immediately for all future virtual copies.
NOTE: You can also use the Recovery Manager CLI command HpRmCli Sql policy to
set Recovery Manager policies. For more information, see “Using the Recovery Manager CLI”
(page 54).
Modifying the Policy for a Virtual Copy
To modify the retention time or the expiration time or both for a virtual copy:
Setting the Recovery Manager Policy
39
1.
2.
3.
In the node tree pane, right-click the virtual copy you want to modify, and select Edit Time
Constraints.
To set a new retention time, select the Retention Time checkbox and enter a new value.
To set a new expiration time, select the Expiration Time checkbox and enter a new value.
For more information on setting the retention and expiration time, see “How Recovery Manager
Policies Work” (page 38).
4.
Click Ok.
NOTE: You can also use the CLI command HpRmCli Sql policy to modify Recovery Manager
policies. For more information, see “Using the Recovery Manager CLI” (page 54).
NOTE: Setting the same expiration value and retention value for a virtual copy using Edit Time
Constraints must be done at the same time.
Configuring Email Notifications
You can configure Recovery Manager to automatically send an email when:
•
You create a virtual copy or remote virtual copy, or Recovery Manager automatically creates
a virtual copy or remote virtual copy according to the task schedule.
•
You create a backup or Recovery Manager automatically creates a backup according to the
task schedule.
•
You restore a volume, an instance, or a database.
In addition, you can configure the email to notify you only when an operation completes, or only
when an error message displays, or when either occurs.
NOTE: For more information about scheduling automatic virtual copies and remote virtual copies,
see “Scheduling Automatic Virtual Copies” (page 43). For more information about scheduling
automatic backups, see “Scheduling Automatic Backups of an Instance or a Database” (page 48).
To configure email notifications:
1. In the node tree pane, right-click the instance for which you want to configure email
notifications, and select Email Config.
2. In the Email Configuration pane, enter the appropriate information in the following text boxes:
3.
•
Email Type - By Default, the Email Type is SMTP
•
SMTP Host Name - Name of the email server
•
Port - Port of the email server
•
Sender Email Address - Email address of the sender
•
Password - Password for the sender’s email address
•
Receiver Email Address - Email address of the person to be notified of task activity or
errors or both
To send email notifications via the Secure Sockets Layer protocol, select the SSL checkbox.
NOTE:
4.
5.
40
To send e-mails to multiple recipients, provide recipient name separated by semicolon.
To make sure the email configuration works, click the Test Connection button.
In the Operations pane, select the desired options in the tab for each type of task (Create
Virtual Copy, Backup, and/or Restore) for which you want emails:
•
Info - Recovery Manager sends informational emails for successful operations.
•
Error - Recovery Manager sends informational emails for operations that were not
completed successfully.
Using the Recovery Manager GUI
Both informational and error emails contain the result of the operation and the related CLI
output.
6.
Click Finish.
Recovery Manager encrypts the password and saves the configuration as an XML file with
the filename servername_instancename_EmailConfig.xml. Each time a virtual copy
or backup is created or a restoration is performed on this instance, Recovery Manager checks
the XML file and, if email is configured for the task, sends an email with the task information
or error messages or both.
NOTE:
Ensure that the Port of SMTP server is not already in use or not blocked by antivirus.
If SMTP server is not enabled for authentication, then any password is accepted.
Deleting Email Configurations
To permanently stop all email notifications for an instance:
1. Select the instance for which you do not want to receive any email notifications.
2. Select Actions→Delete Email Config.
Creating Virtual Copies
You can use Recovery Manager to manually create virtual copies at the instance and the database
level. You can also schedule Recovery Manager to automatically make virtual copies of instances
or databases or both.
NOTE: You can configure Recovery Manager to automatically send email notifications when
virtual copies are manually or automatically created. For more information, see “Configuring Email
Notifications” (page 40).
NOTE: You can execute concurrent virtual copy creation jobs through Recovery Manager GUI
and multiple Recovery Manager CLI instances.
How Virtual Copy Creation Works
When Recovery Manager creates a virtual copy for an instance, it creates a virtual copy of all
databases under that instance, including the instance's system databases. Similarly, when Recovery
Manager creates a virtual copy for a database, it creates a virtual copy of the entire volume where
the database and log files reside.
If you have Remote Copy set up, you can also create a virtual copy to be saved on the Remote
Copy backup server; this type of copy is called a remote virtual copy.
NOTE: For more information about setting up instances, databases, and volumes to avoid data
loss, see “Configuring the SQL Database” (page 20).
NOTE: Recovery Manager creates copy-only backup for availability databases on secondary
replica.
Manually Creating a Virtual Copy
To create a virtual copy:
1. In the node tree pane, right-click the instance or database for which you want to create a
virtual copy, and select Create Virtual Copy.
2. For Availability Group databases, select the Database Source from the menu. This menu lists
the primary and secondary database sources as shown in Figure 7 (page 42)
Deleting Email Configurations
41
Figure 7 Database Sources
3.
Optional: To adjust policy values for this virtual copy (or, if you are scheduling automatic
copies, this group of virtual copies):
•
To adjust the expiration time, select Expiration Time and enter the new expiration time.
•
To adjust the retention time, select Retention Time and enter the new retention time.
Valid values are 0 {h|H|d|D} (for no retention time) to 43,800 hours/1,825 days.
For Availability Group databases, the policy settings for the selected server or instance are
displayed. If the policy settings does not exist for the selected server or instance, the default
settings are displayed.
For more information, see “Setting the Recovery Manager Policy” (page 38).
NOTE: User needs to set value 0 {h|H|d|D}, if they do not want to set the expiration value
and retention value for the virtual copy to be created. If this is not set, the global expiration
policy value and retention policy value will be used for the virtual copy when expiration-based
policy is configured.
4.
To immediately create one virtual copy, click Finish in the Create Virtual Copy dialog box. To
schedule virtual copies, see “Scheduling Automatic Virtual Copies” (page 43)
NOTE:
For Microsoft SQL Server 2012 Availability Group configuration:
•
You can not create virtual copy on all the replica sites at once. You can create virtual
copies on the replica sites only one at a time.
•
You can not create virtual copies of the secondary replica databases which are not set
for read mode. They will not be displayed in the RM GUI. They will also not be a part of
instance level virtual copies. However, you can create virtual copies from the primary site
by selecting the secondary replica site from HP 3PAR Recovery Manager for SQL GUI or
HP 3PAR Recovery Manager for SQL CLI.
NOTE: Under Virtual Copy Management node, Database will have Availability Group icon
if it contains even one virtual copy that was created when database was of Availability Group
type.
42
Using the Recovery Manager GUI
Creating Remote Virtual Copies
How Remote Virtual Copy Works
When you create remote virtual copies, Recovery Manager uses HP 3PAR Remote Copy Software
to send virtual copies to the Remote Copy backup server. The Remote Copy backup server is a
remote server, that is the Recovery Manager backup server.
To use remote virtual copy functionality:
•
The HP 3PAR Remote Copy Software license must be installed.
•
Remote Copy volume groups must be configured.
•
Both the Remote Copy primary server and Remote Copy backup server must be running the
same version of Recovery Manager.
For more information, see “Remote Copy for Recovery Manager” (page 90).
Manually Creating a Remote Virtual Copy
To create a remote virtual copy:
1. In the node tree pane, right-click the instance or database for which you want to create a
remote virtual copy, and select Create Remote Virtual Copy.
2. In the Target Server Name field, enter the name of the Remote Copy backup server.
3. Optional: To view the policy values for the remote server, click Fetch Policy.
4. Optional: To edit the modifiable remote server policy values for the remote virtual copy (or
copies) you are creating, make your changes in the Policy Info area.
5. To immediately create one remote virtual copy, click Finish in the Create Remote Virtual Copy
dialog box. To schedule virtual copies, see “Scheduling Automatic Virtual Copies” (page 43)
NOTE: Remote Virtual copy creation is not supported for Availability Group databases.
Create Remote Virtual Copy option will be disabled for Availability Group Databases.
Displaying Remote Virtual Copies
The Recovery Manager GUI on the backup server does not automatically display remote virtual
copies. To display a remote virtual copy:
•
To display the virtual copy in the Recovery Manager GUI on the Remote Copy backup server,
refresh the Virtual Copy Management node on the Remote Copy backup server.
•
To use a Recovery Manager CLI command to display the virtual copy, enter the CLI command
HpRmCli Sql display with the -rc option on the Remote Copy primary server. For more
information, see “Using the Recovery Manager CLI” (page 54).
Scheduling Automatic Virtual Copies
To schedule automatic virtual copies:
1. In the node tree pane, right-click the instance or the database for which you want to create a
virtual copy, and select one of the following:
2.
•
Create Virtual Copy
•
Create Remote Virtual Copy
Click Next in the Create Virtual Copy dialog box.
The Task Scheduler appears. For more information on using the Task Scheduler, see “Scheduling
Automated Tasks with Task Scheduler” (page 44).
Creating Virtual Copies
43
Automating Tasks
You can use the Task Scheduler to schedule Recovery Manager to automatically create virtual
copies, remote virtual copies, and one-click backup.
You can use Task Manager to manage all scheduled virtual copies and backups for all Recovery
Manager products running on the servers.
Tasks are scheduled using Windows Task Scheduler API.
Scheduling Automated Tasks with Task Scheduler
To schedule automatic virtual copies and backups:
1. Set up a virtual copy creation or backup creation task as desired. For more information, see:
2.
3.
4.
•
“Scheduling Automatic Virtual Copies” (page 43)
•
“Scheduling Automatic Backups of an Instance or a Database” (page 48)
In the Task Scheduler dialog box, select Schedule this task.
In the Windows Task Name text box, enter the name to be assigned to the task.
In the Script File Name text box, enter the name to be assigned to the script.
The Task Command shows the command for the task that is being scheduled.
5.
Enter a description in the Description text box.
The User Name shows the user for the task.
6.
7.
8.
9.
In the Password text box, enter a local user password for the backup server.
In the Password (confirm) text box, reenter the password.
From the Start Time list, select the hour at which you want Recovery Manager to start creating
automatic virtual copies.
To specify the frequency with which the automatic virtual copies are to be created, select the
appropriate radio button in the left pane of the Schedule Pattern area.
The right pane of the Schedule Pattern area displays a calendar with which you can specify
exactly when Recovery Manager is to automatically create virtual copies. The type of calendar
displayed depends on the frequency of the automatic virtual copies selected in the left pane
of the Schedule Pattern area.
•
Once - Schedules one automated virtual copy.
In the right pane, select the month and the year in which to create the virtual copy from
the list above the calendar view, then select the day on the calendar.
•
Hourly - Schedules automated virtual copies multiple times for specified number of days
at the interval you specify.
From the list in the right pane, select the number of hours you want to pass between
automated copies and number of days the schedule remains active.
Select Indefinitely option if you want the task to run indefinitely.
•
44
Daily - Schedules automated virtual copies on a daily basis at the interval you specify.
◦
To schedule copies at regular intervals during the week, select Every day in the right
pane and enter the number of days between copies.
◦
To schedule copies on a daily basis, select Every weekday in the right pane and, in
the Start Date text box, enter the start date or use the Calendar icon to select a start
date.
Using the Recovery Manager GUI
•
Weekly - Schedules automated virtual copies by the day of the week.
In the right pane, enter the number of weeks you want to pass between automated copies
and select the day of the week on which a virtual copy is to be created.
•
Monthly - To schedule copies on a specific date at a specific monthly or daily interval,
enter the date information in the calendar.
10. Click Finish.
NOTE: You can use the Task Manager to edit, run, delete, and view details of scheduled tasks.
For more information, see “Managing Automated Tasks with Task Manager” (page 45).
NOTE: All tasks created in Task Scheduler and their associated script files are not automatically
removed when you uninstall Recovery Manager. Retention of tasks allows you to upgrade your
version of Recovery Manager without losing scheduling information.
Managing Automated Tasks with Task Manager
You can use the Task Manager to manage all your scheduled virtual copies and backups for all
Recovery Manager products running on your servers.
1. In the node tree pane, ensure that a node is selected.
2. Select Scheduled Tasks→Task Manager.
Recovery Manager lists all scheduled tasks in the Task Name column of the Task Manager
dialog box.
Other columns show the name of the script associated with the task, the next time the task is
scheduled to run, and its current status.
3.
4.
To manage a scheduled task, select it and click one of the following buttons:
•
Edit - Opens the Task Scheduler, with which you can modify the task. To save your
changes, you must enter your password. For more information, see “Scheduling Automatic
Virtual Copies” (page 43).
•
Detail - Displays task information in the Task Detail dialog box.
•
Delete - Deletes the task and its associated script file.
•
Run Now - Performs the selected task immediately (in addition to its scheduled run time).
•
Refresh - Updates the list and status of scheduled tasks.
To exit the Task Manager dialog box, click OK.
Prerequisites for Attach and Detach Operation
Before you begin mounting or unmounting a virtual copy, verify the following prerequisites for an
attach operation to complete:
•
The SQL server must be in healthy state for attach operation
•
The disk residing on the database must be online and visible
•
The original database must be online for the attach operation to succeed
•
The name of target server and the SQL server must be same for attach operation to succeed
•
The secondary database files (.mdf), as a part of original database, are also available in the
attached database
•
The Instance is not running on a clustered disk because attaching a database to it cannot
succeed
NOTE:
disk.
You cannot attach a data onto a cluster SQL instance because the data is on a separate
Prerequisites for Attach and Detach Operation
45
Mounting a Virtual Copy
You can use Recovery Manager to mount a virtual copy at the instance or the Database level.
1. In the node tree pane, right-click the timestamp for the virtual copy you want to mount and
select Mount.
2. In the Mount Virtual Copy dialog box, ensure that the Target Server text box displays the server
name to which you want to mount the virtual copy.
3. In the Mount Point Only text box, select the mount point.
NOTE: Recovery Manager does not support mounting a virtual copy to a drive letter or to
a path involving a cluster shared drive letter.
4.
Optional when mounting a virtual copy at a Database level. Check Attach Database option
to attach a Database.
NOTE: By default, when the Attach Database checkbox option is selected and the default
database name appears as <Database Name>_<Timestamp>. If applicable, you can edit the
name of the default database.
NOTE: Virtual copies of databases part of the Availability Group will be attached to its own
instance, but the new database will not be a part of the Availability Group.
NOTE: Mount point on a shared folder or on reparse points, like SYMLINK, NFS mount and
CSV, is not supported.
5.
Click OK.
Recovery Manager:
•
Adds the mounted virtual copy to the list view in the informational pane
•
Displays the server to which the copy is mounted in the Exposure column
•
Displays the absolute path on which the copy is mounted in the Mount Point column
•
Displays the icon for the mounted virtual copy in green
Unmounting a Virtual Copy
1.
2.
In the node tree pane, right-click the timestamp for the virtual copy you want to unmount, and
select Unmount.
Recovery Manager displays a dialog box asking you to confirm the unmount. Click OK.
Recovery Manager:
•
Removes the mounted virtual copy from the list view in the informational pane
•
Displays Not Mounted in the Exposure column
•
Displays the icon for the mounted virtual copy in blue
•
Detaches the database and closes all the connections to the database
Backing Up a Virtual Copy
You can use Recovery Manager to back up virtual copies to media using HP Data Protector,
Symantec NetBackup, or Symantec Backup Exec.
To back up a virtual copy to media, you must first configure your backup software (Data Protector,
NetBackup, or Backup Exec) as described in “Configuring Backup Software” (page 26).
46
Using the Recovery Manager GUI
You can create a backup of an instance or a database on the instance or the database level or
at the timestamp level.
•
When you create a backup on either the instance or the database level, Recovery Manager
creates a new virtual copy, and your backup software backs it up.
NOTE: If the windows user performing the backup operation at the instance or the database
level does not have mount privilege due to absence of administrative privilege, the backup
creation will fail.
•
When you create a backup at the timestamp level, Recovery Manager mounts the existing
virtual copy, and your backup software backs it up using the same timestamp.
NOTE: If the windows user performing the backup operation at the timestamp level on an
unmounted virtual copy does not have mount priviledge due to absence of administrative
priviledge, the backup creation will fail.
You can also schedule Recovery Manager to automatically create backups of instances or databases
or both.
NOTE: You can configure Recovery Manager to automatically send email notifications when
backups are manually or automatically created. For more information, see “Configuring Email
Notifications” (page 40).
NOTE: You can execute concurrent backup jobs through Recovery Manager GUI and multiple
Recovery Manager CLI instances.
Manually Creating Backups at the Instance or the Database Level
When you create a backup of a virtual copy for an instance or a database, Recovery Manager
automatically creates a virtual copy and mounts it, your backup software backs the virtual copy
up to media, and Recovery Manager unmounts the virtual copy. By default, Recovery Manager
deletes the created virtual copy when the backup is complete. You can also choose to have Recovery
Manager retain the newly created virtual copy.
To create a backup of a virtual copy at the instance or the database level:
1. In the node tree pane, right-click the instance or the database you want to back up and select
Backup to Media.
2. From the Select Vendor list, select the backup software you are using:
•
Symantec NetBackup
•
HP Data Protector
•
Symantec Backup Exec
Backing Up a Virtual Copy
47
3.
In the Parameters area, enter the required information, depending on your backup software:
If you are using: Enter these parameters:
Symantec
NetBackup
• Master Server Name: The NBU master server
• NBU Policy Name: The name of the policy you are using
• NBU Full Schedule Name: The name of the schedule within the policy you are using
For more information, see Symantec NetBackup documentation and “Configuring Backup
Software” (page 26).
HP Data
Protector
• Data List: The name of the data list
Symantec
Backup Exec
• Media Server Name: Backup Exec media server name
For more information about data lists, see the description of backup specifications in HP Data
Protector documentation.
• Storage Device Name : Backup Exec device name configured for Backup
NOTE: Recovery Manager saves the information entered in the Parameters area and displays
it as the default the next time you create a backup.
4.
To retain the newly created virtual copy after backup, ensure that the Remove Virtual Copy
from Storage System after backup checkbox is not selected.
NOTE:
5.
Recovery Manager, by default, removes the virtual copy it creates during the backup.
To immediately create one backup, click Finish.
•
•
Recovery Manager creates the backup, names it as its timestamp, and adds it to the
Backup Management node under the relevant instance or database in the node tree pane
if:
◦
You are using an expiration-based policy, or
◦
You are using a numeric-based policy but either have not reached the maximum
number of virtual copies allowed or the policy is configured to remove old copies
as necessary (that is, the Remove the oldest Virtual Copies checkbox is selected).
Recovery Manager does not create the backup if you are using a numeric-based policy
and:
◦
The policy is not configured to remove the oldest virtual copies (that is, the Remove
the oldest Virtual Copies checkbox is not selected), and
◦
You have reached the maximum number of virtual copies allowed, and therefore
Recovery Manager cannot create a new virtual copy.
For more information, see “Setting the Recovery Manager Policy” (page 38).
Scheduling Automatic Backups of an Instance or a Database
To schedule automatic backups of an instance or a database:
1. In the node tree pane, right-click the instance or the database you want to back up, and select
Backup to Media.
2. In the Backup to Media dialog box, enter the appropriate information. For more information,
see “Manually Creating Backups at the Instance or the Database Level” (page 47).
3. Click Next.
48
Using the Recovery Manager GUI
4.
In the Task Scheduler, schedule backups as desired. For more information, see “Scheduling
Automated Tasks with Task Scheduler” (page 44).
Creating a Backup of a Virtual Copy
When you create a backup of one virtual copy, Recovery Manager copies the existing virtual copy,
and the backup software backs the copy up to the media using the same timestamp as the original
copy. Recovery Manager does not create a new virtual copy for a backup of an individual virtual
copy.
To create a backup of one virtual copy:
1. In the node tree pane, right-click the Virtual copy you want to back up and select Backup to
Media.
2. From the Select Vendor list, select the backup software you are using:
3.
•
Symantec NetBackup
•
HP Data Protector
•
Symantec Backup Exec
In the Parameters area, enter the required information, depending on your backup software:
If you are using: Enter these parameters:
Symantec
NetBackup
• Master Server Name: The NBU master server
• NBU Policy Name: The name of the policy you are using
• NBU Full Schedule Name: The name of the schedule within the policy you are using
For more information, see Symantec NetBackup documentation and “Configuring Backup
Software” (page 26).
HP Data
Protector
• Data List: The name of the data list
Symantec
Backup Exec
• Media Server Name: Backup Exec media server name
For more information about data lists, see the description of backup specifications in HP Data
Protector documentation.
• Storage Device Name : Backup Exec device name configured for Backup
NOTE: Recovery Manager saves the information entered in the Parameters area and displays
it as the default the next time you create a backup.
4.
To immediately create one backup, click Finish. Recovery Manager creates the backup, names
it as its timestamp, and adds it to the Backup Management node under the relevant instance
or database in the node tree pane.
For more information, see “Setting the Recovery Manager Policy” (page 38).
NOTE:
Recovery Manager does not support scheduling automated timestamp backups.
Removing a Backup from the Repository
To use Recovery Manager to remove a backup from the repository, right-click the backup and
select Delete Backup.
Restoring Instances, Databases, and Volumes
You can use either the volume restore feature or the file copy feature of Recovery Manager to
restore an instance or a database from a virtual copy, or you can perform a media restore from
a backup.
Removing a Backup from the Repository
49
NOTE: If the servers are configured in a shared volume environment such as a Microsoft cluster
environment, see the following sections for more information on performing a restore in a Failover
Cluster environment:
•
“Restoring an SQL Instance in an Failover Cluster Environment Using File Copy Restore”
(page 79)
•
“Restoring a Volume in Failover Cluster Environment Using Volume Restore” (page 79)
Alternatively, you can use CLI commands to promote the virtual copy to its parent base volume.
For more information, see the HP 3PAR Command Line Interface Administrator’s Manual.
TIP:
Volume restore is the fastest method.
NOTE:
Any type of restore operation on the secondary node in Availability Group is not supported.
Restoring an Instance or a Database with Volume Restore
WARNING! DO NOT perform a volume restore if the base volume to which you are promoting
the virtual copy contains files for other instances or databases.
The volume restore feature promotes the virtual copy to the base volume and overwrites all data
on the volume. If you perform a volume restore on a volume that hosts files for multiple instances
or databases, the operation deletes all data not contained in the promoted virtual copy.
NOTE: An SQL data restore failure can occur when an SQL server service is explicitly stopped
outside of Recovery Manager Software for Microsoft SQL and the disk path itself is not available
for the system in a standalone setup.
1.
2.
3.
4.
Schedule downtime for the SQL Server service; HP 3PAR Recovery Manager for SQL
automatically stops and starts the SQL Server service during a restore.
Under the Virtual Copy Management node in the node tree pane, right-click the timestamp for
the virtual copy you want to use for the restore, and select Restore Using→Volume.
To confirm that you want to continue with the restore process, select the Click to continue
checkbox.
Click OK.
The virtual copy completely overwrites the instance or the database. The instance or the
database is now restored.
NOTE: If the secondary replica node in the Microsoft SQL Server 2012 Availability Group
configuration becomes inaccessible during the restore process, then the user must manually
join the databases back to the Availability Group .
Restoring an Instance or a Database with File Copy Restore
The file copy restore feature enables you to restore a specific instance or a database from a virtual
copy. Unlike the volume restore feature, the file copy restore feature does not overwrite the entire
volume.
1. Schedule downtime for the SQL Server service; HP 3PAR Recovery Manager for SQL
automatically stops and starts the SQL Server service during a restore.
2. Under the Virtual Copy Management node in the node tree pane, right-click the timestamp of
the virtual copy you want to use for the restore, and select Restore Using→File Copy.
NOTE: The Vendor Restore Method field of the File Copy Restore dialog box automatically
displays Virtual Copy (File Copy).
50
Using the Recovery Manager GUI
By default, Recovery Manager restores the virtual copy to its parent instance or database
(specified in the Target Server field).
3.
To restore a virtual copy of a database to a database different from its parent database, you
can specify an alternate database as the target of the restore:
a. In the Database Restore Option area of the File Copy Restore dialog box, select Clone
Database.
b. In the Database Name text box, enter the name of the database to which you want the
virtual copy restored.
c. If you want to restore the clone database to a location other than its parent location, enter
the directory path to the alternate database In the Alternate Path text box. Note that if
you enter an alternate location, you must enter an alternate name in the Database Name
text box.
If you leave this text box blank, the clone database is restored to the parent location of
the original virtual copy.
d.
To use the point-of-failure recovery method to restore the database, select No Recovery.
For more information about completing a point-of-failure recovery, see “Recovering All
Data with Point-of-Failure Recovery” (page 80).
To use the auto-restore feature for restoring a database to the point of failure, select the
latest virtual copy and click the Point of failure radio button to proceed.
4.
5.
To confirm that you want to continue with the restore process, select Click to continue.
Click OK.
Depending on whether you restored the virtual copy to its parent location or created a clone
database, Recovery Manager does one of the following:
•
If you restored the virtual copy to its parent location, Recovery Manager completely
overwrites the instance or database with the virtual copy. The instance or database is
now restored.
•
If you restored the virtual copy with an alternate database name but you did not specify
an alternate database path, Recovery Manager copies the virtual copy to the specified
clone database name (at the parent location) and attaches the database.
•
If you restored the virtual copy with an alternate database name with an alternate database
path, Recovery Manager copies the virtual copy to the specified clone database name
at the alternate location and attaches the database.
NOTE: If the secondary replica node in the Microsoft SQL Server 2012 Availability Group
configuration becomes inaccessible during the restore process, then the user must manually
join the databases back to the Availability Group.
6.
To perform a selective database restore of an instance, locate the Virtual Copy Management
node under the node tree pane.
a. Select the instance level timestamp of the virtual copy for restore and right-click.
b. Select Restore Using→File Copy.
c. Clear any applicable databases not being restored before you proceed.
Restoring an Instance or a Database from Backup
You can restore backups to their original location (that is, to the instance or the database location
of the virtual copy that was used to create the backup, not to the original SQL database or instance
location), or you can specify an alternate location.
Restoring Instances, Databases, and Volumes
51
1.
Under the Backup Management node in the node tree pane, right-click the timestamp for the
backup you want to use for the restore, and select Restore.
By default, Recovery Manager restores the backed-up virtual copy to its original location,
which is displayed in the Alternate Location text box. The original location is the directory
<systemdrive>\3parSnapshot.
2.
3.
If you want to restore the virtual copy to a different location, enter the alternate location in the
Alternate Location text box or select a location from the file chooser.
Click OK.
The backup software mounts the backup to the specified location as a virtual copy. To complete
restoring of an instance or a database, move the virtual copy to the volume or the database.
Analyzing and Synchronizing the Repository
You can use Recovery Manager to compare and synchronize virtual copies in the Recovery Manager
repository with the HP 3PAR StoreServ Storage System.
1. In the node tree pane, right-click the SQL production server, and select Analyze.
2. To automatically synchronize the HP 3PAR StoreServ Storage System and the repository (if
necessary), select Synchronize result with Repository.
To analyze the repository without synchronizing it, clear Synchronize result with Repository.
3.
Click Yes.
Depending on whether you are analyzing and synchronizing the repository or just analyzing
the repository, Recovery Manager does the following:
•
If you opt to automatically synchronize the results, Recovery Manager analyzes the
repository, synchronizes the repository and the HP 3PAR StoreServ Storage System (if
necessary), and updates the list of virtual copies under the Virtual Copy Management
node in the node tree pane.
•
If you opt to only analyze the repository, Recovery Manager displays the Analyze
Repository dialog box and performs the analysis. To view the list of virtual copies not in
the repository, if any, click the Detail button in the Analyze Repository dialog box.
To synchronize the results (if necessary), repeat the above steps to launch the Analyze
Repository dialog box. Be sure to select Synchronize result with Repository before continuing.
Removing a Virtual Copy
1.
Check the Exposure column in the information pane and ensure the virtual copy detail displays
Not Mounted. If the virtual copy is mounted, unmount it.
For more information, see “Unmounting a Virtual Copy” (page 46).
2.
Right-click the virtual copy and select Remove.
Viewing Event Message Descriptions
You can view a description of all Recovery Manager error messages (also called as event messages),
including tips for troubleshooting each event.
1. In the node tree pane, select any node under Recovery Manager.
2. Select About→Event Messages.
Recovery Manager uses your default browser to display the Event Messages file. The file
contains all the events for HP 3PAR Recovery Manager Software for Microsoft SQL Server
arranged in order as per the event ID.
52
Using the Recovery Manager GUI
Viewing Online Help
To view online help for Recovery Manager for Microsoft SQL Server, select Help→Help.
Online Help for HP 3PAR Recovery Manager for Microsoft SQL Server appears in a web browser.
Viewing Online Help
53
6 Using the Recovery Manager CLI
HP 3PAR Recovery Manager for Microsoft SQL Server Command Line
Interface (CLI)
HP 3PAR Recovery Manager Software for Microsoft SQL Server provides a Command Line Interface
(CLI). The CLI allows users to manage Recovery Manager functionality using commands rather than
the Graphical User Interface (GUI).
To do the following:
Use this CLI command:
Create virtual copies
HpRmCli Sql create
Remove unmounted virtual copies
HpRmCli Sql remove
Mount virtual copies
HpRmCli Sql mount
Unmount virtual copies
HpRmCli Sql unmount
Backup virtual copies to media using Symantec NetBackup, HpRmCli Sql backup
HP Data Protector or Symantec Backup Exec
Restore from virtual copies
HpRmCli Sql restore
Display virtual copies currently in the repository
HpRmCli Sql display
List backup entries currently in the backup pool
HpRmCli Sql listbackup
Delete backup entries currently in the backup pool
HpRmCli Sql deletebackup
Query and change repository location
HpRmCli Sql repository
Query and change the port location
HpRmCli Sql portconfig
Change the wait time for backup, volume restore, and
analysis
HpRmCli Sql timeconfig
Gather the environmental statistics and create a log file for HpRmCli Sql report
diagnosis
Analyze and synchronize the volumes in the HP 3PAR
StoreServ Storage System and the virtual copies in the
repository
HpRmCli Sql analyze
Set Recovery Manager policies
HpRmCli Sql policy
Scan the SQL server for any changes
HpRmCli Sql rescan
Set policy for specified virtual copy
HpRmCli Sql setvc
NOTE: The previous syntax for Recovery Manager commands is supported for backward
compatibility. The previous syntax is as follows:
RmSql <Command_name> [Command_options] <arguments>
NOTE: Only NetBIOS names must be used while specifying values for any server type like
production server, backup server, mount server, target server, media server, or master server.
54
Using the Recovery Manager CLI
Recovery Manager Commands
The following sections describe how to administer HP 3PAR Recovery Manager for SQL from the
Command Line Interface.
HpRmCli Sql analyze
SYNTAX
HpRmCli Sql analyze -s <SQL server> [-sync] [-f]
DESCRIPTION
The HpRmCli Sql analyze command validates all virtual copy records by matching virtual
copies in the HP 3PAR StoreServ Storage System against records in the HP 3PAR Recovery Manager
for SQL repository. If any existing virtual copies in the system are missing from the repository, HP
3PAR Recovery Manager for SQL displays them as out-of-sync records. Likewise, if any existing
virtual copies in the repository are missing from the system, HP 3PAR Recovery Manager for SQL
also displays them as out-of-sync records.
PARAMETERS
The following options are supported:
-s <SQL Server>
The SQL server to which the database belongs.
-sync
Optional. Remove out-of-sync virtual copies from the repository. If not
specified, out-of-sync virtual copies remain in the repository.
-f
Optional. Forcefully remove out-of-sync records from the repository. You
must use this option in conjunction with the -sync option. If not specified,
the system prompts you to confirm the removal of out-of-sync virtual copies.
NOTE: When you use the -f option, Recovery Manager automatically removes out-of-sync
records without prompting for confirmation.
EXAMPLES
The following example validates all virtual copies under the specified SQL server.
HpRmCli Sql analyze -s <SQLserver>
Recovery Manager Commands
55
HpRmCli Sql backup
SYNTAX
HpRmCli Sql backup -s <SQL server> [-i <SQL instance>] [-d <database>]
[-t <timestamp> | -r ] [-ts <target server>][[-p <policyName> -u
<scheduleName> -M <masterServer>]|[-dl <datalistName>]|[-be mediaserver
<mediaservername> -device <devicename>]] [-noemail]
DESCRIPTION
The HpRmCli Sql backup command backs up a virtual copy to the specified media. The backup
can be an existing virtual copy, or it can be a new virtual copy created by this command.
PARAMETERS
The following options are supported:
-s <SQL Server>
The SQL server associated with the database.
-i <SQL instance>
Optional. The SQL server instance associated with the database.
If not specified, MSSQLSERVER (local) is used as the default value.
-d <database>
Optional. The database for the virtual copy. If not specified, the
instance for the virtual copy is used as the default value.
-t <timestamp>
Optional. The timestamp of the virtual copy to back up. If not
specified, the system creates a point-in-time virtual copy, uses it to
create the backup, and then removes this virtual copy after the
backup is complete. If specified, the system retains this timestamp
value after the backup is complete.
-r
Optional. Retain the virtual copy. Valid only if you do not use the
-t option. If not specified, the virtual copy is deleted after backup
is complete.
-ts <target server>
Optional. Target Server for the backups if the -r option is not
specified. To use this option, the following must be located at the
secondary site:
•
Recovery Manager Backup Component server, with HP 3PAR
Recovery Manager for Microsoft SQL Server installed
•
Symantec NetBackup client or HP Data Protector
If not specified, the local system is used as the default value.
-p <policyName>
Symantec NetBackup policy name. Only valid if Symantec
NetBackup software is in use.
-u <ScheduleName>
Name of the NetBackup backup schedule. Only valid if Symantec
NetBackup software is in use.
-M <masterServer>
NetBackup master server name. Only valid if Symantec NetBackup
software is in use.
-noemail
Optional. Do not send an email notification even if configured for
this operation. If not specified, Recovery Manager sends an email
notification of the backup if configured. For more information, see
Configuring Email Notifications.
-dl <DataListName>
Specifies the data list name (also called as the backup specification
name) and indicates that the backup software in use is HP Data
Protector.
Optional: If not specified, Recovery Manager proceeds as if the
backup software used is Symantec NetBackup.
56
Using the Recovery Manager CLI
Backup software specified is Symantec Backup Exec.
-be
Optional: If not specified, HP 3PAR Recovery Manager for SQL
proceeds as if the backup software used is Symantec NetBackup.
-mediaserver
<mediaservername>
Backup Exec media server name. Only valid if Symantec Backup
Exec software is in use.
-device <devicename>
Backup Exec device name configured for Backup. Only valid if
Symantec Backup Exec software is in use.
EXAMPLE
The following command performs a backup of virtual copy 020405162103 with the necessary
Symantec NetBackup parameters.
HpRmCli Sql backup -s inst1 -d test_db -t 020405162103 -p test -u full
-M host1
NOTE:
Use quotes ("") when an option value includes spaces.
NOTE: During backup, snapshot volumes of the virtual copy are surfaced to the operating system
with a default mount point under the <SystemDrive>:\3parsnapshot directory. Therefore,
<SystemDrive> must use NTFS in order to support the volume mount point.
NOTE:
You can execute concurrent backup jobs through multiple Recovery Manager CLI instances.
HpRmCli Sql create
SYNTAX
HpRmCli Sql create -s <SQL server> [-rc <target server> [-w
<waittime>]][-i <SQL instance>] [-d <database>] [-noemail] [-exp
<time>{h|H|d|D}] [-retain <time>{h|H|d|D}] [-f]
DESCRIPTION
The HpRmCli Sql create command creates a virtual copy of a SQL database or databases
under an instance on the primary host where the SQL server instance is running. (The virtual copy
can be mounted to a host later for off-host processing.)
The HpRmCli Sql create command used with –rc parameter synchronizes the volumes in
periodic Remote Copy group where a single SQL database or all of the SQL databases under an
instance reside and creates virtual copies at the secondary site as a backup.
As with HP 3PAR Recovery Manager for Microsoft SQL Server itself, this command only supports
the online backup of an entire SQL database. Therefore, you must make sure the database is online
before creating a virtual copy.
PARAMETERS
The following options are supported:
-s <SQL server>
SQL server to which the database belongs.
-i <SQL instance>
Optional. SQL server instance to which the database belongs. If
not specified, MSSQLSERVER is used as the default.
-d <database>
Optional. The database from which to create a virtual copy. If not
specified, the instance level of the virtual copy is used as the default.
-w <waittime>
Optional. Wait time in seconds. Recovery Manager uses this wait
time to poll the status of the remote copy before creating a virtual
Recovery Manager Commands
57
copy at the secondary site. If not specified, the wait time is 120
seconds by default.
-rc <target server>
Remote Copy target server. To use this option, the Recovery
Manager Backup Component server, with HP 3PAR Recovery
Manager for Microsoft SQL Server installed, must be located at the
secondary site.
-noemail
Optional. Do not send an email notification even if configured for
this operation. If not specified, Recovery Manager sends an email
notification of the virtual copy creation if configured. For more
information, see Configuring Email Notifications.
-exp <time>{h|H|d|D}
Optional. Set the expiration time for this virtual copy to the specified
time and time unit. Valid values are:
•
To set the expiration time in hours: 1-43800h (or H)
•
To set the expiration time in days: 1-1825d (or D)
•
To remove the expiration period: 0h (or 0H) or 0d (or 0D)
To use this option, the HP 3PAR Recovery Manager for SQL policy
must be set to an expiration-based policy.
If not specified, HP 3PAR Recovery Manager for SQL creates the
virtual copy using the expiration time specified in the current policy.
NOTE: During remote virtual copy creation for periodic mode,
the expiration time set at the secondary backup server is used as
the time based policy. The policy set at the primary backup server
is ignored. In case of synchronous mode, the expiration value is
applied to both, the local virtual copy and remote virtual copy.
Remote virtual copy creation cannot be done if primary backup
server and secondary backup server for different values are set for
expiration at synchronous mode.
-retain
<time>{h|H|d|D}
58
Using the Recovery Manager CLI
Optional. Set or extend the retention time for the specified virtual
copy to the specified time. The virtual copy cannot be removed
during this time period.
NOTE:
Retention time restrictions are:
•
You must have a Virtual Lock license to use the -retain option.
•
The minimum retention period is 1 hour; the maximum is
43,800 hours/1,825 days (5 years).
•
The default retention time is 336 hours (14 days).
•
The retention time cannot exceed the value of the StoreServ's
VVRetentionTimeMax.
•
You can set a retention time regardless of whether the policy
is numeric or expiration-based.
•
The retention time cannot be longer than the expiration time
(if the policy is expiration-based).
•
During remote virtual copy creation for periodic modes, the
retention time set at the secondary backup server is used as
the time based policy. The policy set at the primary backup
server is ignored. In case of synchronous mode, the retention
value is applied to both, the local virtual copy and remote
virtual copy. Remote virtual copy creation cannot be done if
different values are set for retention at primary backup server
and secondary backup server for synchronous mode.
•
The retention time cannot be removed or reduced after it is set.
•
To set no retention time for this virtual copy, use a value of 0h
(or 0H) or 0d (or 0D).
Optional. When used with the -retain option, does not request
confirmation for the retention time modification.
-f
EXAMPLES
The following command creates a virtual copy for the database test on the SQL server (SQLServer).
HpRmCli Sql create -s SQLServer -d test
The following command creates a virtual copy for the database test on a virtual SQL server
(SQLVirtualServer) on a cluster.
HpRmCli Sql create -s SQLVirtualServer -d test
The following command creates a Remote Copy snapshot for the database test on a virtual SQL
server (SQLVirtualServer) on a cluster to a secondary site server (SecondaryServer).
HpRmCli Sql create -s SQLVirtualServer -d test -rc SecondaryServer
NOTE:
Use quotes ("") when an option value includes spaces.
NOTE: HP 3PAR VSS Software waits up to 10 seconds for a virtual copy operation; and this
interval can not be configured. In most of the cases, 10 seconds is a sufficient interval to successfully
create a virtual copy. However, in some circumstances under very heavy loads, 10 seconds may
not be enough time, and the virtual copy might fail on this attempt. This failure is a VSS framework
requirement on Microsoft’s part.
If such a failure occurs, VSS does not automatically retry the shadow copy creation. You must use
the Recovery Manager GUI or CLI to reattempt to create the virtual copy.
During virtual copy creation, the system creates a backup document in XML format. This document
contains current system information and can be used for restore purposes.
Recovery Manager Commands
59
NOTE: The snapshot volume set is limited to up to 64 volumes. In other words, each database
(under database-level operation) or each instance (under instance-level operation) can spread over
a maximum of 64 volumes.
NOTE: You can only perform database- or instance-level operations if you have system admin
permissions for SQL Server.
Recovery Manager creates copy-only backup for availability databases on secondary replica.
You can execute concurrent virtual copy creation jobs through multiple Recovery Manager CLI
instances. In this case, HP 3PAR Recovery Manager for SQL queues the requests to the VSS so that
all the requests are serviced without any failure.
HpRmCli Sql deletebackup
SYNTAX
HpRmCli Sql deletebackup -s <SQL server> [-i <SQL instance>] [-d
<database>] -t <timestamp>
DESCRIPTION
The HpRmCli Sql deletebackup command removes the specified backup entry from the
Recovery Manager repository only. It does not remove the Symantec NetBackup or HP Data
Protector entry, nor does it remove the actual images backed up by the backup process.
PARAMETERS
The following options are supported:
-s <SQL server>
SQL server to which the backup belongs.
-i <SQL instance>
Optional. The SQL instance associated with the database. If not
specified, MSSQLSERVER (local) is used as the default value.
-d <database>
Optional. The database-level backup to be removed. If not specified,
the instance-level backup is removed by default.
-t <timestamp>
The backup entry timestamp.
EXAMPLE
The following command deletes the backup timestamp 020405162103:
HpRmCli Sql deletebackup -s server1 -d db1 -t 020405162103
60
Using the Recovery Manager CLI
HpRmCli Sql display
SYNTAX
HpRmCli Sql display -s <SQL server> [-rc <target server>] [-i <SQL
instance>] [-d <database>] [-t <timestamp>]
DESCRIPTION
The HpRmCli Sql display command displays all virtual copies in the server at a local site or
a remote site.
PARAMETERS
The following options are supported:
-s <SQL server>
SQL server associated with the database.
-i <SQL instance>
Optional. The SQL instance associated with the database. If not
specified, MSSQLSERVER is used as the default value.
-d <database>
Optional. Display the virtual copies created for a given database.
If not specified, all database and instance virtual copies belonging
to the SQL server are displayed by default.
-rc <target server>
Optional. The Remote Copy target server at secondary site. To use
this option, the Recovery Manager Backup Component server, with
HP 3PAR Recovery Manager for Microsoft SQL Server installed,
must be located at the secondary site. If not specified, the local site
is used as the default value. Availability Group information is not
displayed for virtual copies at a remote site.
-t <timestamp>
Optional. Display detailed information about a specific virtual copy
in the local repository. If no virtual copy is specified, Recovery
Manager displays information about all virtual copies. For
availability database virtual copy with the timestamp, the availability
group information is not displayed when this option is specified. If
this option is not specified, availability group information is
displayed for all the availability database virtual copies listed by
the command.
NOTE: Recovery Manager does not support using the command HpRmCli Sql display -t
for display of information about a virtual copy that exists at a secondary site.
The following command displays the virtual copies for server1.
HpRmCli Sql display -s server1
NOTE:
Use quotes ("") when an option value includes spaces.
NOTE: If you create an instance level virtual copy and then issue the HpRmCli Sql display
command, the Database column displays all to indicate that Recovery Manager has created
virtual copies of all databases except the Temp database.
Recovery Manager Commands
61
HpRmCli Sql listbackup
SYNTAX
HpRmCli Sql listbackup -s <SQL server> [-i <SQL instance>] [-d
<database>] [-t <timestamp>]
DESCRIPTION
The HpRmCli Sql listbackup command displays all virtual copies being backed up via
Symantec NetBackup or HP Data Protector.
PARAMETERS
The following options are supported:
-s <SQL server>
SQL server to which the database belongs.
-i <SQL instance>
Optional. SQL server instance to which the database belongs. If not
specified, MSSQLSERVER (local) is used as the default.
-d <database>
Optional. Database for which to display virtual copies. If not specified,
HP 3PAR Recovery Manager for SQL displays virtual copies being
backed up at the instance and the database level.
-t <timestamp>
Optional. The timestamp of a specific virtual copy to display. If not
specified, Recovery Manager displays all virtual copies being backed
up.
NOTE: When you specify a timestamp, HP 3PAR Recovery Manager for SQL displays detailed
information about the virtual copy being backed up.
62
Using the Recovery Manager CLI
HpRmCli Sql mount
Verify that the following conditions are complete before performing the mount operation:
•
The SQL server must be in healthy state for attach operation
•
The disk residing on the database must be online and visible
•
The original database must be online for the attach operation to succeed
•
The name of target server and the SQL server must be same for attach operation to succeed
•
The secondary database files (.mdf), as a part of original database, are also available in the
attached database
•
If an SQL instance is running in a clustered environment, the snapshots of databases taken
from a particular SQL instance cannot be attached to the SQL instance running on the cluster
environment.
NOTE:
disk.
You cannot attach a data onto a cluster SQL instance because the data is on a separate
SYNTAX
HpRmCli Sql mount -s <SQL server> -t <timestamp> [-m <mount point>]
[-ts <host name>] [-a <attachDatabaseName> -i <instanceName> -d
<OriginalDatabaseName> ]
DESCRIPTION
The HpRmCli Sql mount command mounts a virtual copy created by the HpRmCli Sql
create command.
To mount a virtual copy, you must create an available mount point on the NTFS volume before you
execute the command.
If necessary, use -a option to attach a database to the SQL server.
PARAMETERS
The following options are supported:
-s <SQL server>
The SQL server associated with the database.
-i <SQL instance>
Optional. SQL server instance belonging to the specified database. If
not specified, MSSQLSERVER (local) is used as the default and valid
only if –a option is specified.
-d <database>
Optional. Original Database to be attached. Valid only if –a option is
specified.
-t <timestamp>
The timestamp for the virtual copy to be mounted.
-m <mount point>
Optional. The mount point for virtual copy devices. If not specified,
%SystemDrive%\3parSnapshot is used as the default mount point.
-ts <hostname>
Optional. The name of the host on which to mount the virtual copy. If
not specified, the local host is used as the default mount point.
-a <attach
database>
Optional. New name of the database to be attached.
WARNING! If you mount a volume with the HpRmCli Sql mount command, you must unmount
the volume with the HpRmCli Sql unmount command. Do not manually unmount a volume that
was mounted with the HpRmCli Sql mount command.
Recovery Manager Commands
63
NOTE: When mounting in read-write mode, the system uses VDS API to make the volume read
and write enabled. However, if there is another operation on the disk and the device is locked,
you cannot unmount the volume. If you attempt to unmount a locked volume, the system displays
the following error message:
ERROR: COM call “pVolumeMF->Dismount(TRUE,FALSE)” failed.
Returned HRESULT = 0x80042413
Error text: <Unknown error code>
Error: There was an expected HRESULT error catched: 0x80042413 <Unknown
error code>
This error message indicates the same issue as VDS_E_DEVICE_IN_USE.
To resolve the issue, restart the VDS service or reboot the machine.
NOTE:
HP 3PAR Recovery Manager for SQL only supports snapshot exposure to a host.
Recovery Manager does not support mounting a virtual copy to a drive letter or to a path involving
a cluster shared drive letter.
64
Using the Recovery Manager CLI
HpRmCli Sql policy
SYNTAX
HpRmCli Sql policy -s <SQL server> [-i <SQL instance>] [-q] [-exp
<time>{h|H|d|D}] [-in <instance virtual copy limit>][-n <database virtual
copy limit>] [<-r>] [-retain <time>{h|H|d|D}] [-f]
DESCRIPTION
The HpRmCli Sql policy command sets the Recovery Manager policy at the instance and the
database level.
PARAMETERS
The following options are supported:
-s <SQL server>
SQL server to which the database belongs.
-i <SQL instance>
Optional. The SQL server instance to which
the database belongs. If not specified,
MSSQLSERVER (local) is used as the default.
-r
Optional. Retain the oldest virtual copy even
when the number of virtual copies exceeds the
limit set by the Recovery Manager policy. If
you specify this option, Recovery Manager
cannot create new virtual copies after the
maximum copies allowed is reached (unless
you manually remove one or more older virtual
copies). If not specified, Recovery Manager
removes virtual copies.
-q
Optional. Query current policy status. If not
specified, the current policy status is not
displayed.
-n <database virtual copy limit>
Optional. The maximum number of
database-level virtual copies to retain. If not
specified, a maximum of 10 is used as the
default.
-in <instance virtual copy limit>
Optional. The maximum number of
instance-level virtual copies to retain. If not
specified, a maximum of 10 is used as the
default.
NOTE: The sum of the values used for the
-n and -in options cannot exceed 500.
-exp <time>{h|H|d|D}
Optional. If the policy is expiration-based, set
the expiration time to the specified time and
time unit. Valid values are:
•
To set the expiration time in hours:
1-43800h (or H)
•
To set the expiration time in days:
1-1825d (or D)
If not specified, the expiration time does not
change.
Recovery Manager Commands
65
-retain <time>{h|H|d|D}
Optional. Set or extend the retention time for
the specified virtual copy to the specified time.
The virtual copy cannot be removed during
this time period.
NOTE:
-f
66
Using the Recovery Manager CLI
Retention time restrictions are:
•
You must have a Virtual Lock license to
use the -retain option.
•
The minimum retention period is 1 hour;
the maximum is 43,800 hours/1,825
days (5 years).
•
The default retention time is 336 hours
(14 days).
•
This option cannot be used with -rc.
•
The retention time cannot exceed the
value of the StoreServ's
VVRetentionTimeMax.
•
You can set a retention time regardless
of whether the policy is numeric-based or
expiration-based.
•
The retention time cannot be longer than
the expiration time (if the policy is
expiration-based).
•
During remote virtual copy creation for
asynchronous periodic modes, the
retention time set at the secondary backup
server is used as the time based policy.
The policy set at primary backup server
is ignored. In case synchronous mode,
the retention value is applied to both the
local virtual copy and remote virtual copy.
Remote virtual copy creation cannot be
done if different values are set for
retention at primary backup server and
secondary backup server for synchronous
mode.
•
The retention time cannot be removed or
reduced after it is set.
•
To set no retention time for this virtual
copy, use a value of 0h.
Optional. When used with the -retain option,
does not request confirmation for the retention
time modification.
EXAMPLE
The following command sets the maximum number of virtual copies to 5 at all times for the default
SQL instance:
HpRmCli Sql policy –n 5 -s <SQL server>
The following command sets the expiration time of virtual copies to 30 days for the default SQL
instance:
HpRmCli Sql policy -exp 30d -s <SQL server>
NOTE: By default, the HP 3PAR Recovery Manager for SQL policy is set to a maximum of 10
virtual copies each for the instance level and the database level. In addition, the option to delete
the oldest virtual copy is, by default, set to ‘No’. Therefore, when the virtual copy limit is reached,
HP 3PAR Recovery Manager for SQL retains the oldest virtual copy.
You can use the above example command either to expand the policy limit (by specifying a larger
value for the -n option) or to enable removal of the oldest virtual copy if the limit has already been
reached (by not using the -r option).
Use quotes ("") when an option value includes spaces
HpRmCli Sql portconfig
SYNTAX
HpRmCli Sql portconfig [-s <WindowsHost>] [-n <number>]
DESCRIPTION
After HP 3PAR Recovery Manager for SQL is installed, the default port used for communication
between the backup server and production server is 9932. If necessary, you can specify an alternate
port.
PARAMETERS
The following options are supported:
-s <WindowsHost>
Optional: Specifies a RM Windows Host to list or configure the port
settings. Defaults to "localhost" if unspecified.
-n <number>
Optional: If specified, then the command will update the port used. If
not specified, then the command will show the current configuration.
Accepted port range is from 1024-65535. (Default port: 9932)
EXAMPLES
The following command changes the local port to 9999.
HpRmCli Sql portconfig -n 9999
The following command changes the port on the specified SQL server to 9999.
HpRmCli Sql portconfig -s <WindowsHost> -n 9999
NOTE: After you execute the portconfig command, you must restart Recovery Manager
Services.
NOTE: If you change the port value on one server, you must update the port value for every HP
3PAR Recovery Manager for SQL system (including the Recovery Manager backup server) managed
by the same Recovery Manager backup server.
NOTE: If a port number specified is already being used by another application, this command
reports error.
Recovery Manager Commands
67
HpRmCli Sql remove
SYNTAX
HpRmCli Sql remove -s <SQL server> -t <timestamp>
DESCRIPTION
The HpRmCli Sql remove command removes a virtual copy from the system and the Recovery
Manager repository. The virtual copy must not be mounted; if the virtual copy is mounted, HP 3PAR
Recovery Manager for SQL does not remove it.
PARAMETERS
The following options are supported:
-s <SQL server>
The SQL server to which the database belongs.
-t <timstamp>
The timestamp of the virtual copy to remove.
NOTE: After a virtual copy is removed, it cannot be used to restore data from the HP 3PAR
Recovery Manager for SQL repository. However, you can restore a removed virtual copy from the
backup media if the virtual copy was backed up with the HpRmCli Sql backup command and
the backup entry is still available.
HpRmCli Sql report
SYNTAX
HpRmCli Sql report -s <WindowsHost> -output <OutputDirectory>
DESCRIPTION
The HpRmCli Sql report command collects the environmental information from a specified
Windows host and creates a report for diagnostic purposes.
PARAMETERS
The following options are supported:
-output <OutputFolder>
Full path to the folder in which to generate the report.
-s <WindowsHost>
Name of the HP 3PAR Recovery Manager for SQL host.
EXAMPLE
The following command retrieves platform information from the host Grampus and saves the report
in c:\MyReport.
HpRmCli Sql report -s Grampus -output c:\MyReport
68
Using the Recovery Manager CLI
HpRmCli Sql repository
SYNTAX
HpRmCli Sql repository [-a <alter destination>] [-r]
DESCRIPTION
After HP 3PAR Recovery Manager for SQL is installed, by default the repository directory is located
under the Recovery Manager install directory. To provide the highest level access to the repository,
you can change the repository destination to the location of the HP 3PAR virtual volume.
PARAMETERS
The following options are supported:
-a <alter Destination>
Optional: Move the repository to an alternate location. If not
specified, HP 3PAR Recovery Manager for SQL retains the
current repository location.
NOTE: If you use the CLI to move the repository to an
alternate location, you must restart the Recovery Manager for
Microsoft SQL Server GUI to view the repository in its new
location.
-r
Optional. Retain the current repository location and only make
changes to the registry values. Use this option when HP 3PAR
Recovery Manager for SQL is reinstalled after operating under
an alternate location. Note that if you use this option, you
cannot move the repository path back to the alternate location.
EXAMPLE
The following command moves the repository directory to d:\3parvv and updates the registry
database as well.
HpRmCli Sql repository –a d:\3parvv
HpRmCli Sql rescan
SYNTAX
HpRmCli Sql rescan -s <SQL server> [-i <instance>]
DESCRIPTION
The command rescans the SQL server instance.
PARAMETERS
The following options are supported:
-s Server SQL server
The SQL server to which the database belongs.
-i instance name (default is
MSSQLSERVER
The SQL server instance to which the database belongs. If
not specified, MSSQLSERVER is used as the default.
EXAMPLE
The following rescans the SQLserverA with default instance
HpRmCli Sql rescan -s SQLserverA.
Recovery Manager Commands
69
EXAMPLE
The following rescans the SQLserverA with instanceB
HpRmCli Sql rescan -s SQLserverA -i instanceB.
NOTE: In SQL 2012, by default, sysadmin role is not selected for NT account. For HP 3PAR
Recovery Manager for SQL to work, user has to explicitly configure the sysadmin role.
HpRmCli Sql restore
SYNTAX
HpRmCli Sql restore -s <SQL Server> [-i <instance>] [-d <database>] <-t
timestamp> [-ts <target server>] [[-M <masterServer>]|
[-dp]|[-be]][-clonedb <database name>] [-a <altLocation>] [-snap]
[-norecovery] [-f] [-noemail]
NOTE: When performing -pointofFailure option, always use the latest version of a virtual
copy to complete the restoration successfully.
Any type of restore operation on the secondary node in Availability Group is not supported.
DESCRIPTION
You can use the HpRmCli Sql restore command to perform 3 different types of restore:
•
Media Restore - Using an existing backup entry, Recovery Manager for Microsoft SQL Server
issues a restore request to the backup software in use (Symantec NetBackup, HP Data Protector
or Symantec Backup Exec). The image associated with this backup entry is then restored to
the location you specify. If you do not specify an alternate location, data is restored to
SystemDrive:\3parSnapshot by default.
•
File Copy Restore - Using an existing virtual copy, Recovery Manager for Microsoft SQL Server
mounts the copy, extracts the database files, and copies the files back to their original locations.
Because the files are copied over one by one, File Copy Restore is a relatively slow but reliable
way of restoring data.
•
Volume Restore - Using an existing virtual copy, Recovery Manager for Microsoft SQL Server
removes the existing VLUNs, promotes the virtual copy back to its base volume, and recreates
the VLUNs back to the host. Volume Restore is relatively fast. However, you should not perform
this restore if the base volumes you are promoting contain data from other instances or
databases.
NOTE: For more information about performing an instance-level file copy restore in Failover
Cluster environment, see “Restoring an SQL Instance in an Failover Cluster Environment Using File
Copy Restore” (page 79).
NOTE: For more information about performing a volume restore in Failover Cluster environment,
see “Restoring a Volume in Failover Cluster Environment Using Volume Restore” (page 79).
PARAMETERS
The following options are supported:
70
-s <SQL server>
The SQL server to which the database belongs.
-i <SQL instance
Optional. The SQL server instance to which the database
belongs. If not specified, MSSQLSERVER is used as the
default.
-d database(s)
The database name of database level virtual copy or
multiple databases of a instance level virtual copy.
Using the Recovery Manager CLI
-t <timestamp>
The timestamp for the virtual copy to restore.
-ts <target server>
Optional. (Symantec NetBackup Media Restore only) The
target server for the restore request. If not specified, the
current server name is used as the default.
-M <masterServer>
Optional. (Media Restore only) The Symantec NetBackup
master server name. Valid only if the backup software in
use is Symantec NetBackup.
Optional: If not specified, the current server name is used
as the default.
-a <altLocation>
Optional. An alternate location to which to restore the
data. If not specified, data is restored to
<SystemDrive>:\3parSnapshot by default.
-snap
Optional. (Volume Restore only) Promotes the virtual copy
back to the base volume for a faster restore. You can only
promote a base volume that is exposed to a host. If not
specified, the virtual copy is not promoted to the base
volume.
-noemail
Optional. Do not send an email notification even if
configured for this operation. If not specified, Recovery
Manager sends an email notification of the restore if
configured. For more information, see Configuring Email
Notifications.
-norecovery
Restore database with the SQL Server norecovery
option. For more information, see Recovering All Data with
Point-of-Failure Recovery.
-clonedb <database name>
Optional. Restore the database to a different database
name. If not specified, HP 3PAR Recovery Manager for
SQL restores the database to the original database name.
-dp
Specifies that HP Data Protector is to be used for the
restore.
Optional: If not specified, Recovery Manager proceeds
as if the backup software used is Symantec NetBackup.
-pointofFailure
Specifies restoring to a point-of-failure.
-be
Use Backup Exec restore method
NOTE: If you are restoring a volume that is part of a Remote Copy target system, you must restore
the virtual copy to the Remote Copy volume group that is part of the same Remote Copy target
system as the virtual copy.
EXAMPLES
The following command performs a media restore of virtual copy 020405162103 from media
backup to drive j:\.
HpRmCli Sql restore -s server1 -d test_db -t 020405162103 -M server1
-a J:\
The following command performs a file copy restore of virtual copy 020405162103.
HpRmCli Sql restore -s server1 -d test_db -t 020405162103
The following command performs a volume restore of virtual copy 020405162103.
HpRmCli Sql restore -snap -s server1 -d test_db -t 020405162103
Recovery Manager Commands
71
The following command performs a media restore of a virtual copy 020405162103 using Data
Protector.
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103 -dp
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103 -dp
-a J:\Test
The following command performs a media restore of a virtual copy 020405162103 using NBU.
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103 -M
server1
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103 -M
server1 -a J:\Test
The following command performs a restore to a point-of-failure of virtual copy 020405162103
HpRmCli Sql restore -s server1 -i inst -t 020405162103 -pointofFailure
The following command performs a restore of multiple databases from a instance level virtual copy
020405162103.
HpRmCli Sql restore -s server1 -i inst -t 020405162103 –d "machinename1,
machine1, mach1"
NOTE:
72
Use quotes ("") when an option value includes spaces.
Using the Recovery Manager CLI
HpRmCli Sql setvc
SYNTAX
HpRmCli Sql setvc
-s <SQL server> [-i <instance>] [-d <database>] -t <timestamp> -exp
<time>{h|H|d|D} [-retain <time>{h|H|d|D} [-f]]
DESCRIPTION
The HpRmCli Sql setvc command sets time constraints for an existing virtual copy. To use this
command, the policy must be an expiration-based policy.
PARAMETERS
The following options are supported:
-s <SQL Server>
The SQL server to which the existing virtual copy belongs.
-i <SQL instance>
Optional. The SQL server instance to which the existing virtual
copy belongs. If not specified, MSSQLSERVER is used as the
default.
-d <database>
Optional. The database of the existing virtual copy. If not specified,
the timestamp is assumed to be at the instance level.
-t <timestamp>
The timestamp of the virtual copy for which you are changing the
expiration time.
-exp <time>{h|H|d|D}
Set the expiration time for this virtual copy to the specified time
and time unit. Valid values are:
-retain
<time>{h|H|d|D}
•
To set the expiration time in hours: 1-43800h (or H)
•
To set the expiration time in days: 1-1825d (or D)
Optional. Set or extend the retention time for the specified virtual
copy to the specified time. The virtual copy cannot be removed
during this time period.
Recovery Manager Commands
73
NOTE:
Retention time restrictions are:
•
You must have a Virtual Lock license to use the -retain option.
•
The minimum retention period is 1 hour; the maximum is
43,800 hours/1,825 days (5 years).
•
The default retention time is 336 hours (14 days).
•
The retention time cannot exceed the value of the StoreServ's
VVRetentionTimeMax.
•
You can set a retention time regardless of whether the policy
is numeric-based or expiration-based.
•
The retention time cannot be longer than the expiration time
(if the policy is expiration-based).
•
If you create a remote virtual copy and Remote Copy is set
up in asynchronous periodic mode, the retention time is
applied to the remote copy on the Remote Copy backup
server only. If Remote Copy is set up in synchronous mode,
the retention time is applied to both the remote copy on the
Remote Copy backup server and the virtual copy on the
Remote Copy primary server.
•
The retention time cannot be removed or reduced after it is
set.
Optional. When used with the -retain option, does not request
confirmation for the retention time modification.
-f
NOTE: Setting the same expiration value and retention value for a virtual copy using setvc
command must be done at the same time.
EXAMPLE
The following command sets the expiration time for virtual copy 020409162103 to 2 hours:
HpRmCli Sql setvc -s server1 –t 020409162103 -exp 2h
The following command sets the expiration time for virtual copy 020409162103 to 30 days:
HpRmCli Sql setvc -s server1 –t 020409162103 -exp 30d
NOTE:
74
Use quotes ("") when an option value includes spaces.
Using the Recovery Manager CLI
HpRmCli Sql timeconfig
SYNTAX
HpRmCli Sql timeconfig [-s <WindowsHost>] [-prt <promotetime>][-bkt
<backuptime>] [-ai <analyzeinterval>]
DESCRIPTION
After you install Recovery Manager for SQL, by default, the wait time for snap volume restore is
30 seconds, the wait time for backup is 5 minutes, and the wait time for analysis of the repository
with the HP 3PAR StoreServ Storage System is 60 minutes. You can use this command to change
these values. If no parameters are specified, it queries the time value for each setting
PARAMETERS
-prt <promotetime>
Optional. The time in seconds to wait for volume promotion. If not
specified, 30 seconds is used as the default wait time.
-bkt <backuptime>
Optional. The time in minutes to wait for backup. If not specified,
5 minutes is used as the default wait time.
-s <WindowsHost>
Optional. The Windows host on which Recovery Manager is
installed. If not specified, the local host is used as the default.
-ai <analyzeinterval> Optional. The time in minutes to wait for automatically analysis of
the repository against the system. Valid values are 10-1440 (10
minutes to 24 hours). If not specified, 60 minutes is used as the
default.
NOTE: If you use the -ai command to modify the analyze interval, you must restart HP 3PAR
Recovery Manager for SQL for the change to take effect.
EXAMPLES
The following command queries the time value for each setting.
HpRmCli Sql timeconfig
The following command changes the promote time to 50 seconds.
HpRmCli Sql timeconfig -prt 50
The following command changes the backup time to 7 minutes.
HpRmCli Sql timeconfig -bkt 7
The following command will change the analyze interval to 30 minutes
HpRmCli Sql timeconfig -ai 30
NOTE: In most cases, there is no need to change these values unless the backup and/or volume
restore are taking an unusually long time to complete.
Recovery Manager Commands
75
HpRmCli Sql unmount
Verify that the following tasks are complete before performing the unmount operation:
•
The SQL server must be in healthy state for attach operation
•
The disk residing on the database must be online and visible
The following results of the unmount operation may occur:
•
Unmounting of a virtual copy does not occur if unmounting operation is unsuccessful
•
Detach operation proceeds automatically following the unmount operation
NOTE: There is not a separate command for attaching and detaching operations. Both commands
automatically follow after a mounting and unmounting operation.
SYNTAX
HpRmCli Sql unmount -s <SQL server> -t <timestamp> [-f <forceDetach>]
DESCRIPTION
The HpRmCli Sql unmount command unmounts a currently mounted virtual copy that was
mounted by the HpRmCli Sql mount command. HP 3PAR Recovery Manager for SQL can only
unmount a virtual copy if its mounted status is not “Available.”
PARAMETERS
The following options are supported:
-s <SQL server>
The SQL server to which the database belongs.
-t <timestamp>
The timestamp of the virtual copy to unmount.
-f <forceDetach>
Optional: Forces detach when there are active connections on database.
NOTE: During an unmount operation, HP 3PAR Recovery Manager for SQL detaches any attaching
databases, removes the mount point from the mounted volumes, and then removes the mount point
folder.
Running Recovery Manager as a Scheduled Job
In addition to creating virtual copies using the Command Line Interface, you can also use Windows
Scheduled Tasks (or Windows Task Scheduler, depending on your Windows OS) to schedule
automatic creation of virtual copies for a specific database.
NOTE: You can also use the HP 3PAR Recovery Manager for SQL GUI to schedule automatic
virtual copies. For more information, see Scheduling Automatic Virtual Copies.
Scheduling an Automated Task in Windows
To set up Windows Task Scheduler to automatically create virtual copies:
1. Click Start→Programs→Accessories→System Tools→Task Scheduler.
2. Click Create Task.
3. In the Name text box on the General tab, enter a name for the task.
4. Select the desired options in the Security options area.
5. Select the Triggers tab.
6. Click New.
7. Enter scheduling information for the automatic creation of virtual records.
8. Select the Actions tab.
9. Click New.
76
Using the Recovery Manager CLI
10. In the New Action dialog box, click Browse.
11. Navigate to the Recovery Manager install location. The default location is:
C:\Program Files\3PAR\RM\SQL
12. In the Add arguments text box, enter:
HpRmCli.exe Sql create –s <SQL Server> –i <SQL Instance> -d <SQL
database>
If the name has spaces, use double-quotes (““) to surround the name.
For more information, see the HpRmCli Sql Create command.
For example:
“C:\Program Files\3par\RM\SQL\HpRmCli.exe” Sql create –i inst01–d
test -s SQLserver
13. In the Conditions and Settings tabs, refine the scheduled task as desired.
14. Click OK.
Result: Virtual copies are created as you have scheduled. Depending on the policy set with
the HP 3PAR Recovery Manager for SQL GUI or CLI command, older virtual copies on the
system might automatically be removed if the number of virtual copies exceeds your specified
maximum threshold (see “Setting the Recovery Manager Policy” (page 38)).
Scheduling an Automated Task in Windows
77
7 Recovery for Microsoft SQL Server
Microsoft SQL Server Recovery Models
Microsoft SQL Server offers three disaster-recovery models:
•
Simple Recovery Model - The Simple Recovery model enables you to restore a database to
the point at which a virtual copy or backup was created; it does not enable you to restore a
database to a specific point in time. Therefore, any data modifications made between the
time of the most recent backup and the time of the failure are lost. This recovery model uses
circular logging to minimize the amount of space used for transaction logs.
•
Full Recovery Model - The Full Recovery model enables you to restore a database to a specific
point in time; either to a virtual copy created before an error occurred or to the point just
before which a system failure occurred. Under this recovery model, transaction logs are saved
until a failure occurs, and therefore no data is lost.
•
Bulk-Logged Recovery Model - The Bulk-Logged Recovery model is used for high-performance
operations such as bulk copying and bulk data modification.
NOTE:
HP 3PAR Recovery Manager for Microsoft SQL Server supports only Full Recovery Model.
NOTE: If you are recovering data from SQL servers across multiple domains, ensure that you
have stored the login and password for each domain on your backup server. For more information,
see “Configuring Recovery Manager Policies” (page 21).
Recovering Data with HP 3PAR Recovery Manager
HP 3PAR Recovery Manager for Microsoft SQL Server supports both recovery from virtual copy
and recovery from media. However, only recovery from virtual copy enables you to perform a
point-in-time or point-of-failure recovery.
If you are running SQL Server under the Full Recovery model, you must perform a restore from a
virtual copy.
You can use manual method or auto-restore method to restore the data. To use the auto-restore
method, refer to “Recovering Data with Auto-Restore” (page 81).
Preparing for the Recovery Process
Before recovery begins, you must ensure the database can be taken offline.
1. Check whether database ID 9 is full.
When the SQL server takes a database offline, it writes a checkpoint record to database ID
9. After this log file becomes full, the SQL server cannot write the checkpoint record and
therefore cannot take the database offline.
2.
If database ID 9 is full, do one of the following:
•
Back up the transaction log for the database
•
Detach the database
NOTE:
Restoring a database or an instance on a filestream drive is not supported.
Recovery Manager uses the Volume Shadow Copy Service (VSS) framework to restore data.
Because the VSS framework takes a database offline before it allows you to restore it, you do not
need to place the database in single-user mode.
78
Recovery for Microsoft SQL Server
Recovering from Logical Errors with Point-in-Time Recovery
Point-in-time recovery is useful for recovering from logical errors. For example, if you accidentally
altered an entry or deleted a table, you can use a virtual copy to restore your instance or database
back to a consistent, known prior state. Point-in-time recovery restores the instance or database to
the state it was in at the time the virtual copy was created.
To perform a point-in-time recovery, use Recovery Manager to perform a file copy restore or a
volume restore. The restore steps depend on whether SQL servers are in clustered environment or
non-clustered environment.
1. Schedule downtime before performing the restore.
2. If you are performing a restore on a standalone SQL production server in a non-clustered
environment:
•
If you are performing a file copy or volume restore on an instance: Stop the SQL Server
service for the instance, perform a standard file copy restore or volume restore, and start
the SQL Server service.
•
If you are performing a volume restore on a database: Stop the SQL Server service,
perform a standard volume restore, and start the SQL Server service.
•
If you are performing a file copy restore on a database: Perform a standard file copy
restore. (Do NOT stop and start the SQL Server service.)
For more information about performing a standard restore using the Recovery Manager
GUI, see “Using the Recovery Manager GUI” (page 34). For more information about
performing a standard restore using the CLI HpRmCli Sql restore command, see
“Using the Recovery Manager CLI” (page 54).
If you are performing the restore in Failover Cluster environment, you must follow the instructions
provided in one of the following sections, depending on the type of restore you are performing:
•
“Restoring an SQL Instance in an Failover Cluster Environment Using File Copy Restore”
(page 79)
•
“Restoring a Volume in Failover Cluster Environment Using Volume Restore” (page 79)
Restoring an SQL Instance in an Failover Cluster Environment Using File Copy Restore
To perform a file copy restore on an SQL instance in Failover Cluster environment:
1. Schedule downtime. Recovery Manager automatically takes the SQL Server Agent and SQL
Instance Service offline.
2. Locate the instance-level virtual copy you want to use to restore the SQL instance.
3. Run the HpRmCli Sql restore command on this virtual copy. For more information on
Recovery Manager CLI commands, see “Using the Recovery Manager CLI” (page 54).
Restoring a Volume in Failover Cluster Environment Using Volume Restore
To perform a volume restore on an SQL server in Failover Cluster environment:
1. Schedule downtime. Recovery Manager automatically takes the relevant SQL services offline.
2. Log onto your backup server and perform a volume restore. To perform a volume restore, use
either the HpRmCli Sql restore command or the Recovery Manager GUI.
For more information about performing a restore using the Recovery Manager GUI, see “Using
the Recovery Manager GUI” (page 34). For more information about performing a restore
using the CLI HpRmCli Sql restore command, see “Using the Recovery Manager CLI”
(page 54).
Recovering from Logical Errors with Point-in-Time Recovery
79
Recovering All Data with Point-of-Failure Recovery
Point-of-failure recovery is useful if you cannot afford to lose any data in the event of a system
failure.
NOTE:
Point-of-failure recovery only supports a file copy restore at the database level.
Determining Whether You Can Perform a Point-of-Failure Recovery
In point-of-failure recovery, a database is completely recovered up to the point of the failure. You
can perform a point-of-failure recovery if all of the following conditions are met:
•
You have performed a full backup of the SQL database.
•
You have subsequently used the SQL backup utility to perform one or more transaction log
backups.
•
You have access to undamaged transaction log backups and active transaction logs (thata
is, even if one or more transaction log backups are damaged, undamaged copies of these
backups exist).
NOTE: A transaction log backup is a copy of all the log records written to the live transaction
log after the last full database backup or the last transaction log backup. If any transaction log
backups within the sequence are missing, the database can only be restored to the last consecutive
backup that exists in the sequence, and you cannot perform a full recovery.
For more information on how to roll a database forward using a transaction log, see:
http://msdn.microsoft.com/en-us/library/ms189596.aspx
Performing a Point-of-Failure Recovery
When you apply the backed-up transaction log to a database that has been restored using a virtual
copy, the system uses the STOPAT option to roll forward the database to a specific point in time.
To roll forward the transaction log, you can use either SQL Server Management Studio or a
command line tool such as OSQL. For example:
To perform a point-of-failure recovery:
1. Locate the most recent consistent full backup and determine the following information:
2.
•
Timestamp (e.g., 010106000000)
•
Server name (e.g., SQLserver01)
•
SQL instance name (e.g., SQLInstan01)
•
Database name (e.g., northwind)
At the command prompt, enter the following:
HpRmCli.exe Sql restore -s server name -i SQL instance name -d
database name -t timestamp -norecovery
For example:
80
Recovery for Microsoft SQL Server
HpRmCli.exe Sql restore -s SQLserver01 -i SQLInstan01 -d northwind
-t 010106000000 -norecovery
3.
To apply the transaction logs as well as to recover the database to the point in time desired,
enter the following restore commands at the command prompt:
a. Enter the following command for the first to the penultimate backed-up transaction logs
in the sequence:
RESTORE log database name from transaction log backup media with
norecovery;
The database is still in “no recovery” mode. You can now apply the backed-up transaction
logs to update the database to the point of failure.
b.
Enter the following command for the last backed-up transaction log:
RESTORE log database name from transaction log backup media with
recovery; -stopat “timestamp"
For example:
RESTORE log northwind from Disk='G:\log1.bak' with norecovery;
RESTORE log northwind from Disk='G:\log2.bak' with norecovery;
RESTORE log northwind from Disk='G:\log3.bak' with recovery;
-stopat "Jun 28, 2006 5:44 PM"
Recovering Data with Auto-Restore
You can use an auto-restore feature to restore a database from a virtual copy to a point in failure
at database level and also use it for restoring multiple databases of a given instance level virtual
copy.
A database can be restored from using either a File Copy or Volume copy.
NOTE: If you have named your database log files to a non-default name, do not use a selective
database restore with the non-default database from a instance level virtual copy. For example, if
your database name is rmsdb.mdf, the log file name must be rmsdb_log.ldf and not any other
name. In some cases when the log file name is not a default name, use the file copy restore at a
database level or file copy restore of the complete instance level virtual copy.
Recovering Data with Auto-Restore
81
Performing a File Copy Restore
If you are performing a Point of Failure file copy restore, be sure to complete the following
prerequisite tasks before initializing restore:
•
Ensure that there is at least one virtual copy of the database available or create one before
performing the restore operation
•
Ensure to always select the latest virtual copy when performing a point-of-failure restore
•
Do not use third party tools, including SQL management studio, to create database backups
or transaction log backups
•
Verify if the database is online and visible under the Instance
1.
Locate the Virtual Copy Management timestamp at an Instance or Database level in the left
pane and right-click.
Select Restore Using→File Copy.
2.
Figure 8 Restore Using File Copy
82
Recovery for Microsoft SQL Server
3.
From an Instance level, select the applicable Database Names.
Figure 9 Restore Using File Copy at an Instance Level
From a Database level, select a restore option:
•
Clone Database
•
Point in time with No Recovery
•
Point of Failure: This option performs a tail log backup of the active transaction log;
restores in no recovery mode of specified point-in-time virtual copy; replays the tail log
backup on the restored database; and removes the tail log backup file when all the listed
operations result in success.
Figure 10 Restore Using File Copy at a Database Level
Recovering Data with Auto-Restore
83
NOTE:
SQL services remains active during a Point of Failure restoration operation.
NOTE: When multiple database restore option is selected, SQL services stops and restarts
when operation is complete. Only point-in-time restore option is available with this feature for
this release.
4.
5.
6.
Click Next.
Read the warning before checking the Click to continue box and clicking Finish to proceed
with restoration.
Review the Restore Virtual Copy log and click Ok.
Performing a Volume Restore
1.
2.
Locate the specific Virtual Copy Management timestamp at an Instance or Database level in
the left pane and right-click.
Select Restore Using→Volume.
Figure 11 Volume Restore at a Database Level
3.
4.
Read the warning before checking the Click to continue box and clicking OK to proceed with
restoration.
Review the Restore Virtual Copy log and click Ok.
NOTE: To ensure that all the disks are brought online after the volume restore operation, in the
DISKPART command set the parameter as san policy=online all.
Performing volume and file copy restore for availability databases
Restoring primary database will remove the database from the primary node and the secondary
nodes. HP 3PAR Recovery Manager for SQL restores database only at the primary node. All
84
Recovery for Microsoft SQL Server
secondary databases will be in restoring state. All secondary databases must be restored manually
after the restore operation is completed on primary node by HP 3PAR Recovery Manager for SQL.
To manually restore availability database on secondary replica node:
1. Take Full backup of the availability database and transaction log at primary replica node.
2. Manually restore the secondary availability database and its log from the backup taken at
primary replica node using RESTORE WITH NO RECOVERY option. If the primary database
and secondary database have different file paths, you must use the WITH MOVE option.
3. Perform this restore sequence on every server instance that hosts a secondary replica for the
availability group.
4. Join the database to the Availability group.
Recovering Data with Auto-Restore
85
8 Coexistence of HP 3PAR Recovery Manager for SQL and
HP 3PAR Recovery Manager for Exchange
Prerequisites
86
•
Only backup server component of HP 3PAR Recovery Manager for SQL and HP 3PAR Recovery
Manager for Exchange applications can be installed on the same server.
•
Mixing the backup server components and production server components in coexistence
scenario is not supported.
•
HP 3PAR Recovery Manager for SQL and HP 3PAR Recovery Manager for Exchange
applications must be installed and launched independently.
•
Recovery Manager for SQL must be in the same domain as Exchange server.
Coexistence of HP 3PAR Recovery Manager for SQL and HP 3PAR Recovery Manager for Exchange
9 Using HP 3PAR Peer Motion Manager Software with
Recovery Manager
HP 3PAR Peer Motion Manager is a feature of the HP 3PAR Software and manages the migration
of data in between existing storage systems or third party storage arrays. HP 3PAR Recovery
Manager now supports HP 3PAR Peer Motion Manager data migration activities without any
impact on host operations while monitoring the primary storage system.
NOTE: When using HP 3PAR Peer Motion Manager to move virtual volumes in between storage
systems, you must delete the data folder and subfolders from c:\program_files\3par\RM\sql
(default) folder and relaunch Recovery manager GUI.
For more information about performing Peer Motion data migration, refer to the HP 3PAR Peer
Motion User Guide. Go to http://www.hp.com/go/3par/, navigate to your product page, click
Support for your product, and then click Manuals.
NOTE:
•
Peer motion only from StoreServ to StoreServ is supported.
•
Peer motion from EVA to StoreServ is not supported.
•
After Peer motion from StoreServ to StoreServ is completed, the HP 3PAR VSS Provider must
be modified to point to the new StoreServ and HP 3PAR VSS Provider service must be restarted.
NOTE: If the device is presented using RDM (Raw Device Mapping) and if peer motion is
performed on that device, the device must ignore the SCSI INQUIRY Cache.
To configure the virtual machine with RDM to ignore the SCSI INQUIRY cache:
•
Add the following parameter to the .vmx file:
scsi x:y. ignoreDeviceInquiryCache = "true"
where x is the SCSI controller number and y is the SCSI target number of the RDM.
This parameter can be configured only on virtual machines with hardware version 8. Upgrade the
virtual machine to hardware version 8 before adding this parameter.
Enable this parameter only when it is recommended by the storage vendor. This parameter is
required for a limited number of storage arrays and only for specific guest operating systems. You
might need to reboot the system for the changes to take effect.
87
10 Using HP 3PAR CLX with Recovery Manager
SQL Server Failover Clustering is a shared storage failover cluster solution which consists of two
or more nodes. There is one copy of the SQL databases with this solution. However, because this
solution is based on a shared storage, third-party array-based replication solution like HP Remote
Copy, synchronous and asynchronous replication can be used to have more than one copy of the
SQL databases.
HP 3PAR Recovery Manager for SQL supports SQL server clustering with CLX configuration.
Recovery Manager supports SQL server clustering and HP 3PAR CLX configuration in conjunction
with Remote copy feature of Recovery Manager.
A backup server is required for each site corresponding to each array. If there are two arrays
configured in a local site and a remote site, there will be a need for two backup servers, one on
local site and one on the remote site.
Figure 12 describes an example of two site configurations.
Figure 12 Two Site Configuration
This figure is only an example, follow clustering best practices for implementation.
Recovery Manager supports only two-site configuration. Within each site, any number of nodes is
supported.
A backup server is required for each site corresponding to each array.
The backup server on each site must be configured only with the array connected to the nodes on
that site. For example, using provcfg configuration tool, ensure that you add only Site A array
configuration on the Site A backup server. Similarly on site B, configure only the site B array.
The backup server on each site can only manage the SQL server Instances or databases which
are owned by nodes on the respective sites.
88
Using HP 3PAR CLX with Recovery Manager
NOTE:
Ensure that only one array is configured on each backup server.
•
The Create Remote virtual copy operation should use “Remote Virtual Copy” option.
•
This will ensure corresponding virtual copy is created on other site.
•
The remote site backup server information is required to specify as input for remote virtual
copy operation. For more information on Recovery Manager remote copy, see “Remote Copy
for Recovery Manager” (page 90)
•
The corresponding virtual copy created on the remote site can be used for recovery operations
on the remote site.
Using Virtual Copy operation without Remote Copy, will only create a virtual copy on the local
site and that can be managed only by local site backup server. In case of a site disaster, the
production volume cannot be recovered on the remote site, as there would not be any virtual copy
on the remote site corresponding the local virtual copies.
Each backup server can only manage the SQL server and its Instance or databases that are currently
owned by the nodes on their respective sites.
NOTE:
Recovery Manager cross-site management is not supported.
For example. in Figure 12 (page 88), the site A backup server can perform all operations on the
nodes on site A. Example: create virtual copy on an instance or a database which are currently
owned by the nodes on site A, that is node 1 and node 2. Site A backup server will not be able
to perform any operation on site B nodes such as node 3 and node 4 as they are connected to a
different array on site B. Similarly the same rules apply to site B backup server.
WARNING!
Any attempt to perform cross-site operation will result in a failure.
SQL server and its Instance or databases owned by one site can failover to other site. In such a
scenario, the other site should be used for subsequent virtual copy operations.
Recovery operation can only be performed on a site using the virtual copy created on that site. If,
there is a failover of the SQL server after virtual copy creation, to use the virtual copy for recovery,
the SQL server must fail back or must be moved back to the earlier node where virtual copy was
created.
Cluster Virtual Network Name (VNN) must be used for registering SQL server to Recovery Manager.
Cluster VNN must be used when a mount needs to be done to an owning node. The command is
automatically directed to the owning node. However, if the current owning node has crossed over
to the other site (remote site) due to failover or planned movement, then the mount operation will
fail. In such a scenario, the other backup server must be used for the mount operation.
Recovery Manager supports Synchronous remote copy configurations.
In Synchronous remote copy, Recovery Manager creates virtual copy on the local site first and
then it creates virtual copy on remote site. Therefore, virtual copy management such as mount,
recovery, and backup can be performed on both the sites.
89
11 Remote Copy for Recovery Manager
Overview
HP 3PAR Remote Copy Software helps you to safeguard against disasters that might occur at one
location, by allowing you to keep copies of data on a separate server which can be placed at a
remote location. For example, if there were a fire or earthquake at one location, all of the data
stored there could be lost unless a backup copy can be recovered from a separate location not
affected by the disaster.
To maintain updated copies of data at a remote location, Remote Copy uses two HP 3PAR StoreServ
Storage Systems: a primary server (used for production) and a backup server, which can be located
anywhere. Therefore, when disaster strikes in one location, there is always a backup of your data
at the backup site.
For more information, see the HP 3PAR Remote Copy Software User’s Guide.
How Remote Copy Works
When you synchronize data between a production system (the Remote Copy primary system) on
one site and the backup server at another site, the systems involved perform the following steps in
sequence:
•
Recovery Manager leverages the VSS framework to freeze the I/O at the application level.
•
For asynchronous periodic mode Remote Copy, the VSS provider creates a virtual copy of
the database and log volumes.
•
Remote Copy issues the command to create coordinated snapshot at the source site. The
command is added in the log queue internally within the array and later issued to the
destination site.
•
Remote Copy synchronizes the data on the primary server with the data on the Remote Copy
backup server (thus updating the backup server).
•
After synchronization is complete, Remote Copy creates a virtual copy ( snapshot) on the
Remote Copy backup server.
•
The Remote Copy backup server saves the virtual copy in its repository at the remote site.
•
For asynchronous periodic mode Remote Copy, Recovery Manager removes the virtual copy
entry from its primary backup server repository and virtual copies created at the primary
StoreServ are retained.
NOTE: User can make use of the Expiration policy settings of Recover Manager. In this case,
the retained virtual copies are removed by the StoreServ after the expiration period has
elapsed.
NOTE: For the Recovery Manager GUI to manage virtual copies on the Remote Copy backup
server, you must configure Recovery Manager with the precise server and instance names for the
supported SQL servers. For more information, see “Configuring Recovery Manager” (page 20).
NOTE:
90
Remote copy is not supported for SQL Server 2012 Availability databases.
Remote Copy for Recovery Manager
Figure 13 Remote copy configuration
Setting Up Remote Copy
1.
Install and configure Remote Copy. For more information, see the HP 3PAR Remote Copy
Software User’s Guide.
NOTE: Be sure to configure the Remote Copy backup server with the same names, structure,
and Windows authentication mode settings as the primary server.
2.
3.
After you have set up Remote Copy on two HP 3PAR StoreServ Storage Systems, create a
Remote Copy volume group for testing purposes.
Configure the Remote Copy volume group for synchronization in synchronous mode or in
asynchronous periodic mode with a period value of zero.
Setting Up Remote Copy
91
Support for Remote Copy Modes and Policies
Recovery Manager supports Remote Copy in synchronous mode and asynchronous periodic mode.
•
If you are using synchronous Remote Copy, the policies on the production system (the Remote
Copy primary system) and the Remote Copy backup system must match. If the policies do not
match, Recovery Manager cannot create virtual copies on a synchronous Remote Copy system.
If you manually specify an expiration value, or a retention value, or both when you create a
virtual copy, Recovery Manager creates the virtual copy on a synchronous Remote Copy
system if
◦
the policy on both the Remote Copy primary server and backup servers is an expiration
based policy and
◦
all the policy values including retention values match
You can specify only the retention value when you create a virtual copy on synchronous Remote
Copy system, if the policy on both the Remote Copy primary servers and backup servers is
numeric and all the policy values, including retention values, match.
NOTE: For more information on specifying values at the time you create virtual copies, see
the description of the HpRmCli Sql create command in “Using the Recovery Manager
CLI” (page 54).
•
If you are using asynchronous periodic Remote Copy, you can create Recovery Manager
virtual copies even if policies on the servers do not match. If policies do not match, the virtual
copies use the policies on the Remote Copy backup server.
•
•
If you are running Remote Copy in a Synchronous Long Distance configuration, the virtual
copies on the synchronous Remote Copy backup servers have the same timestamp. The virtual
copies on the asynchronous periodic Remote Copy backup servers do not have the same
timestamp.
Setting Up Remote Copy Volume Groups
Setting Up a Remote Copy Volume Group for Databases
1.
2.
Identify the virtual volumes that contain the database and log files to be copied.
Create one (and only one) primary Remote Copy volume group per database.
NOTE: Recovery Manager supports multiple databases in one Remote Copy volume group
if all the databases in the group belong to the same instance.
3.
Add the virtual volumes belonging to the database and log files to the primary Remote Copy
volume group, and add the associated secondary virtual volumes to the secondary volume
group on the Remote Copy backup server.
CAUTION: Do not disperse files from one database over multiple primary Remote Copy
volume groups. Recovery Manager does not support database and log files from one database
existing in any location other than the one primary Remote Copy volume group created for
that database.
4.
Synchronize the Remote Copy primary and secondary volume groups.
Setting Up a Remote Copy Volume Group for Instances
1.
2.
92
Identify the virtual volumes that contain all databases and log files to be copied.
Create one primary Remote Copy volume group for this instance.
Remote Copy for Recovery Manager
3.
Add all virtual volumes that belong to this instance (all database and log files) to the primary
Remote Copy volume group, and add the associated secondary virtual volumes to the secondary
volume group on the Remote Copy backup server.
CAUTION:
The relationship between instances and Remote Copy volume groups is 1:1.
•
You must add files from only one instance to a primary Remote Copy volume group.
•
You must add files from only one instance to one primary volume group.
◦
Do not disperse files from one instance over multiple primary Remote Copy volume
groups.
◦
Do not add files from multiple instances to the same Remote Copy volume group.
If these system requirements are not met, you may encounter data corruption and loss.
4.
Synchronize the Remote Copy primary and secondary volume groups.
Recovering an SQL Database from a Remote Copy Backup Server
If an SQL database crashes at the site that holds the primary servers, you can recover the data
from the Remote Copy backup server at the remote site as long as it is set up in an identical manner
to the original production server.
NOTE: If you are performing a promote restore for volumes in a Synchronous Long Distance
Remote Copy relationship, you must manually stop Remote Copy before initiating the volume
promote restore.
1.
2.
3.
4.
5.
On the backup server, use Recovery Manager to mount the virtual copy to the production
server.
Log onto the production server and stop the SQL instance and its dependent services.
From the mounted virtual copy, manually copy all necessary database and log files to the
corresponding database location.
Restart the SQL instance and its dependent services.
Log back onto the backup server and unmount the virtual copy.
Recovering an SQL Database from a Remote Copy Backup Server
93
12 Support and Other Resources
Related Documents
For Information About…
Read the…
Using the HP 3PAR OS Command Line Interface (CLI) to
configure and manage the HP 3PAR StoreServ Storage
System
HP 3PAR Command Line Interface Administrator’s Manual
Using the HP 3PAR Management Console to configure and InForm Management Console Help Release 4.3
administer HP 3PAR StoreServ Storage Systems
Assigning the appropriate user roles and rights
HP 3PAR StoreServ Storage Concepts Guide (OS 3.1.3)
HP 3PAR Command Line Interface Administrator’s Manual
Identifying HP 3PAR StoreServ Storage System components HP 3PAR InForm OS Messages and Operator’s Guide
and fixing problems
Understanding the HP 3PAR StoreServ Storage System and HP 3PAR StoreServ Storage Concepts Guide (OS 3.1.2)
its features
Shadow copies using HP 3PAR VSS Provider Software for
Microsoft Windows
HP 3PAR VSS Provider Software for Microsoft Windows
User Guide
Platform-specific release levels
For information about supported hardware and software
platforms, see the Single Point of Connectivity Knowledge
for HP Storage Products (SPOCK) website: http://
www.hp.com/storage/spock.
Typographical Conventions
Typeface
Meaning
ABCDabcd
Used for dialog box elements such as Enter your system name in the Value
titles and button labels.
box and click OK.
ABCDabcd
Used for file names, paths, and screen Found < 12 > 73G disks. Enter
output, and for text you are to enter. cli at the Windows command prompt.
ABCDabcd
Used to contrast your input with system cli% removevv VV1 Removing vv
output.
VV1.
ABCDabcd
Used for variables in file names,
paths, and screen output, and for
variables in user input.
ABCDabcd
Example
[root@(systemID-nodeID)root] To
continue enter your system
name ==> systemname
NOTE: The InServ Storage Server is rebranded as HP 3PAR StoreServ Storage System. There
are instances in this document where screenshots or menu items or both and command output refer
to the HP 3PAR StoreServe Storage System as InServ or InServ Storage Server.
94
Support and Other Resources
Advisories
To avoid losing or damaging data, be sure to observe the cautions and warnings in this document.
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
document.
Advisories
95
13 Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the
documentation, send any errors, suggestions, or comments to Documentation Feedback
([email protected]). Include the document title and part number, version number, or the URL
when submitting your feedback.
96
Documentation feedback
A Server Virtualization Environments
VMware and Microsoft Hyper-V Environments
VMware and Microsoft Hyper-V environments are supported under specific conditions in an FC
configuration. For VMware and Microsoft Hyper-V support in a virtualization environment, the
setup must meet the following requirements in an FC configuration:
•
The disks presented to the SQL servers must be physical devices.
•
The backup server must be connected directly to the HP 3PAR StoreServ Storage System. The
backup server cannot be connected to the HP 3PAR StoreServ Storage System through VMware
or Microsoft Hyper-V in an FC configuration.
•
You cannot run the HpRmCli Sql mount command against a VMware or Microsoft Hyper-V
server in an FC configuration.
NOTE: New volumes presented to VMware and Microsoft Hyper-V servers are not surfaced
automatically. You must use the backup host to mount the servers with the HpRmCli Sql mount
command. Therefore, you cannot use either File Copy Restore or Volume Restore to directly restore
an SQL server that resides in a virtualized FC configuration environment.
NOTE: An iSCSI setup is supported in a backup server operating in a Microsoft Hyper-V and
VMware ESX(i) Virtual Machine.
Figure 14 (page 97) shows the relationships between the HP 3PAR StoreServ Storage System and
VMware and Microsoft Hyper-V servers in a virtualization environment.
Figure 14 Server Virtualization Environment
VMware and Microsoft Hyper-V Environments
97
B Troubleshooting
Known Issues
•
When HP 3PAR CLI is not installed using HP 3PAR Recovery Manager Software for SQL setup:
◦
If the certificate is not saved for current StoreServ username used by HP 3PAR Recovery
Manager Software for SQL, errors occur for all HP 3PAR Recovery Manager Software
for SQL tasks or HP 3PAR VSS Provider tasks, except for new StoreServ registration
command in HP 3PAR VSS Provider.
In such cases, to proceed further, the administrator must validate the certificate again
using the HP 3PAR VSS Provider provcfg.exe utility.
◦
If the certificate is expired or is invalid for configured StoreServ username in HP 3PAR
VSS Provider, errors occur for all HP 3PAR Recovery Manager Software for SQL tasks or
HP 3PAR VSS Provider tasks, except for new StoreServ registration command in HP 3PAR
VSS Provider.
In such cases, to proceed further, the administrator must validate the certificate again
using the HP 3PAR VSS Provider provcfg.exe utility.
98
•
If an array has a valid license but it expires, all Recovery Manager operations fail after license
expiry.
•
If the license is expired but it is in cache memory, then all Recovery Manager operations
succeed with the expired license. Administrator must ensure that a new certificate is generated
at the StoreServ and register the StoreServ again from HP 3PAR VSS Provider.
•
If there is any change in the certificate on the StoreServ, register the StoreServ again in the
HP 3PAR VSS Provider using the provcfg command.
Troubleshooting
•
•
•
When restore operation is performed using HP Data Protector or Symantec BackupExec,
snapshot files are restored to <Alternate_Location>/<Mount_Folder>/
__SNAPSHOT_FILES__.
For example, snapshot files are restored to C:\3parSnapshots\3parSnapshots\ when
◦
A snapshot is mounted at C: \3parSnapshots
◦
HP Data Protector or Symantec BackupExec media backup is performed and
◦
HP Data Protector or Symantec BackupExec media restore is performed with alternate
location C:\3parSnapshots (default location).
When restore operation is performed using Symantec NetBackup, snapshot files are restored
to <Alternate_Location>/__SNAPSHOT_FILES__.
For example, snapshot files are restored to C:\3parSnapshots\ when
◦
A snapshot is mounted at C: \3parSnapshots
◦
Symantec NetBackup media backup is performed and
◦
Symantec NetBackup media restore is performed with alternate location C:\
3parSnapshots (default location).
If a snapshot is already mounted, then media restore function using Symantec NetBackup
fails.
Troubleshooting
This appendix is designed to be used like a Frequently Asked Questions section. It will help you
find solutions to some of the common issues that might arise when running HP 3PAR Recovery
Manager Software for Microsoft SQL Server.
Problem:
Recovery Manager displays error message “VSS_E_PROVIDER_VETO.”
Suggestion:
Check the application event log and VSS provider log from the production server. If you see
“Maximum of 28 writable virtual copies per volume is allowed,” your virtual copy capacity might
be full.
This error usually occurs when you mount a virtual copy. Unmount several virtual copies and
continue the mount procedure.
Problem:
Even though Recovery Manager validated the configuration during operation, Recovery Manager
exits without any messages during the check of the HP 3PAR StoreServ Storage System.
Suggestion:
Validation might fail without proper notification. Restart the HpRmCli Sql agent service on the
backup and production servers.
Problem:
A restore of a backup, which was created using Symantec NetBackup via the Recovery Manager
GUI, fails.
Suggestion:
When you use the Recovery Manager GUI to back up a virtual copy using Symantec NetBackup
and a directory is specified for backup, you must enter the directory name and path precisely,
including the upper- and lower casing (for example, MuTenFF). If the names do not match exactly,
a restore of this backup will fail as Symantec NetBackup is case-sensitive.
When backing up a directory, specify the directory in exactly the same case as it exists on the file
system.
Problem:
Troubleshooting
99
When you create a virtual copy on a SAN boot disk, the virtual copy creation fails with error
“Error-VSS_E_HOLD_WRITES_TIMEOUT.” The in-box system writer that enumerates all operating
system and driver binaries is included as well. The error usually occurs because the I/O cannot
hold the system writer.
Suggestion:
HP does not recommend placing a database on the SAN boot disk. Place all important databases
on separate SAN disks.
Problem:
As data blocks are copied per the copy-on-write technology, the space for virtual copies on the
virtual volume might become 100% full either if virtual copy space was statistically allocated as a
percentage of the virtual volume, or if there is no additional space available for the CPG to
auto-grow. If the space for virtual copies on a virtual volume becomes 100% full, the virtual copies
on the virtual volume may become invalid and subject to the Recovery Manager policy.
Suggestion:
Allocate more virtual copy space when creating virtual volumes during base volume creation, or
use CPGs to manage the data generated by copy-on-write technology.
Problem:
You just installed Recovery Manager, but all GUI and CLI commands fail.
Suggestion:
If you install Recovery Manager via a remote desktop session, the newly added environment
variables do not go into effect until you log out of the session. (If Recovery Manager is installed
directly from the system console, these variables should be available immediately.)
Problem:
Symantec NetBackup takes a substantial amount of time to complete a backup process.
Suggestion:
Make sure you have the latest maintenance package installed for your NetBackup application.
Problem:
Recovery Manager is running in a Windows cluster environment and the application event log
displays the Volume Shadow Copy Service error: “Unexpected error querying for the
IVssWriterCallback interface. Access is denied.”
Suggestion:
Reconfigure the security settings for the cluster environment as follows:
1. Ensure that Failover Cluster MS DTC is installed. Failover Cluster MS DTC is required for the
following procedure.
2. Click Start→Run→dcomcnfg or Start→Administrative Tools→Component Services.
3. Expand Component Services and click Computers.
4. Right-click My Computer and select Properties.
5. Select the COM Security tab.
6. Under Access Permissions, click Edit Default.
7. Add a Cluster Service account and select Local Access and Remote Access.
8. Reboot the machine.
9. Perform these steps on the second node.
Problem:
You attempt to perform a media restore using the Recovery Manager CLI -ts command and the
attempt fails.
Suggestion:
If the restore log contains the error message: “client <client> peer name <peer name> is
invalid for restore request,” the restore client is different from the backup client. Configure Symantec
NetBackup to perform a redirected media restore as follows:
100 Troubleshooting
1.
Create an altnames directory on the NetBackup master server in the directory containing the
backup policy for other clients:
Install_path\NetBackup\db\
2.
Place an empty file named No.Restrictions in the altnames directory:
Install_path\NetBackup\db\altnames\No.Restrictions
Do not add a suffix to the files in the altnames directory.
3.
Ensure that the NetBackup client name on the requesting client matches the name of the client
for which the backup was created. (The peer name of the requesting client need not match
the NetBackup client name.)
Problem:
When using Symantec NetBackup, you see this message: 0x1: ERROR: Cannot connect to [NBU
server name]; socket error.
Suggestion:
Check whether you are using a different version of the NBU master server and the NBU client. If
so, upgrade the NBU client to the same version as the NBU master server.
Problem:
Error in communication between Production Server and Backup Server and the
vcdbasqlRMSQLAgent_1.log shows the following exception System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network
address/port) is normally permitted.
Suggestion:
By default, HP 3PAR Recovery Manager for Microsoft SQL Server uses port 9932. This port might
be used by other application, leading to a communication issue between backup server and
production servers.
If you continuously notice this issue, follow either of the following steps:
•
Change the default port used by Recovery Manager in the registry and restart HP 3PAR
Recovery manager for SQL service from services.msc.
NOTE:
•
The port used should be the same on both, backup server and production servers.
Find out the application using the default port and stop that application.
To find out the application using the default port:
◦
Open the command prompt
◦
Run netstat -ano | find "<port number>"
Example:
c:\>netstat -ano | find "9965"
UDP 10.10.5.32: 9932 *:* 1252
UDP 16.154.142.171: 9932 *:* 1252
UDP 127.0.0.1: 9932 *:* 1252
This will list the process id of the application that is using the default port. (The process id of
the application is 1252 in the example.).
Troubleshooting
101
To find out the application name for the process id which is using the port:
◦
Run tasklist | find "<port number>"
Example:
c:\ >tasklist | find "9932"
application.exe 1252 Services 0 23,228 K
If it is possible, stop this application to free up the port <port number> and Restart HP 3PAR
Recovery manager for SQL service from services.msc.
Problem:
While installing HP 3PAR Recovery Manager Software for SQL, the setup.exe prompts to uninstall
3PAR CLI though it is a supported version as per Single Point of Connectivity Knowledge for HP
Storage Products (SPOCK) document. The installer does not provide an option to install HP 3PAR
Recovery Manager Software for SQL .
Suggestion:
If you want to install only HP 3PAR Recovery Manager Software for SQL without its required
components, then run RMS_2k8_x64.msi/RMS_2k8_x86.msi directly from the folder
\HP3PAR\RecoveryManagerSQL.
Ensure that you have the supported configuration as per Single Point of Connectivity Knowledge
for HP Storage Products (SPOCK) document
Problem:
Backup Exec does not invoke post job command in the following cases:
•
Media configured for backup is offline
•
Media configured for backup is running with low space
•
Network issue
In such cases, The impact on HP 3PAR Recovery Manager for SQL is as follows:
1. GUI will show backup status in progress
2. Backup time stamp will be empty
3. In case of one click backup, though the virtual copy is marked for deletion, the virtual copy
does not get removed
4. Virtual copy will not be unmounted
Suggestion:
To overcome the above use case user have to manually run the postbackup commands
hprmcli sql postbackup –s <servername>[ -i <instancename> ] -t <timestamp> [ -d <database>] -r
<Backup status>
–s <servername>
The SQL server associated with the database.
-i <instancename>
Optional. The SQL server instance associated with the database. If
not specified, MSSQLSERVER (local) is used as the default value.
-t <timestamp>
The timestamp of the virtual copy to back up.
-d <database>
Optional. The database for the virtual copy. If not specified, the
instance for the virtual copy is used as the default value.
–r <Backup status>
Backup completion status in NBU, DP or BE. If backup completed
successfully then backup status will be 1 else it will be 0.
Problem:
After volume promote, on few occasions, the volume involved in the restore operation might not
come online.
Suggestion:
From the Disk Management utility of the server, select the volumes involved in Restore operation
and manually make them online. If the problem persists, present the LUN which was to be restored
102 Troubleshooting
to the same host again through HP 3PAR Management Console (MC) using a LUN ID different
from the original LUN ID.
Problem:
After Repository location change, previously scheduled tasks do not work and they do not appear
in Task Manager List.
Suggestion:
Delete those old tasks from Windows Task Scheduler. Clean up the Recovery Manager Tasks
folder and create those tasks again from the Recovery Manager.
Problem:
Point of failure (using Auto restore) fails if, earlier the virtual copy is recovered manually using
Point in time and No recovery option.
Suggestion:
Do not use any third party software or SQL management studio for backing up the transaction
logs. Doing so would result in Recovery Manager not having the Transaction log backup sequence
and this results in the failure of point-of-failure restore operation.
Problem:
If you are trying to uninstall HP 3PAR Recovery Manager for SQL , sometimes a window pops up
prompting for server reboot.
Suggestion:
It is recommended that you click Cancel button, stop the HP 3PAR Recovery Manager for SQL
service and HP 3PAR VSS Provider service and then try the uninstallation of the product again.
Problem:
If Recovery Manager for SQL server is in the workgroup and is managed by Recovery Manager
for Exchange backup server, then one click backup fails.
Suggestion:
Symantec NetBackup must be installed using custom installation option and registration of the
Symantec Netbackup service during the time of installation must be done explicitly using work
group privilege.
Problem:
You might encounter the following error in HP 3PAR Recovery Manager Software for SQL CLI or
GUI output or in the log files.
Suggestion:
Troubleshooting 103
Use the provcfg.exe utility provided with HP 3PAR VSS Provider to recreate an expired, an
invalid, or a new certificate.
Problem:
If you have configured StoreServ during HP 3PAR VSS Provider installation or using HP 3PAR VSS
Provider provcfg utility, and later changed the TPDCERTDIR environmental variable or moved
certificate from one location to another location, then you might encounter the following error:
Suggestion:
Use the provcfg.exe utility provided with HP 3PAR VSS Provider to recreate an expired, an
invalid, or a new certificate.
Problem:
If the certificate is not saved using the provcfg command provided by HP 3PAR VSS Provider,
but by using some other command (for example, using HP 3PAR CLI command), then HP 3PAR
Recovery Manager Software for SQL is dependent on the %USERPROFILE% or the TPDCERTDIR
environment variables. If a user modifies these two variables to an invalid value, then HP 3PAR
Recovery Manager Software for SQL does not work for that HP 3PAR CLI user.
Suggestion:
Use the provcfg.exe utility provided with HP 3PAR VSS Provider to recreate an expired, an
invalid, or a new certificate.
Problem:
Mounting of Recovery Manager for SQL snapshot fails with the following error:
Import snapshot information to backup server.
RME5189: ERROR: Fail to mount to specified mount point, in iSCSI
environment of RMS Configuration
Currently unmounted.
UnMount Successful
Suggestion:
Check if the iSCSI hostname of the Recovery Manager for SQL Production server or Backup servers
created on HP 3PAR StoreServ is same as the name mentioned in the iSCSI initiator's configuration
tab.
NOTE: The name is case sensitive. When checking iSCSI hostname, exclude the iqn number
from the name mentioned in the iSCSI initiator's configuration tab.
For example:
If host side iqn number is iqn.1991-05.com.microsoft:rmsbackupsvr.2k10vfc.com
Then hostname created on HP 3PAR Storeserv side should be rmsbackupsvr.2k10vfc.com
104 Troubleshooting
C Event Messages
This appendix provides information for the event messages generated by HP 3PAR Recovery
Manager Software for Microsoft SQL Server.
Table 4 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages
Event ID
Event Message
Description/Action
5312
RMS5312: ERROR: Some of your volumes Some of the target volumes are not HP 3PAR virtual volumes.
are either non-3PAR volumes or
All of the drives need to be HP 3PAR drives.
unsupported types of disk drives.
• Verify that all database and log destinations belong to an
HP 3PAR StoreServ Storage System.
5313
RMS5313: ERROR: Couldn't find the
Remote Copy group for the specified
volume.
The Remote Copy volume group is not configured for the
specified SQL database or instance.
• Check the Remote Copy configuration and HP 3PAR
StoreServ Storage System setup.
• Consult the HP 3PAR InForm OS CLI Administrator's Manual
or the HP 3PAR Management Console Help for details on
setting up and checking Remote Copy functionality.
5314
RMS5314: ERROR: The number of virtual
volumes used to create the virtual copy
does not match the number of virtual
volumes in the Remote Copy group.
To create a virtual copy of a SQL database or instance, the
virtual volumes configured to store SQL database and log files
must match the virtual volumes configured in the Remote Copy
volume group.
• Check the Remote Copy configuration and HP 3PAR
StoreServ Storage System setup.
• Consult the HP 3PAR InForm OS CLI Administrator's Manual
or the HP 3PAR Management Console Help for details on
setting up and checking Remote Copy functionality.
5319
5321
RMS5319: ERROR: The virtual copy was
not found in the repository.
The repository might be out of sync.
RMS5321: ERROR: The specified mount
directory does not exist.
To use an alternate (non-default) mount point directory in the
HpRmCli Sql mount command, you must first create the
mount point directory.
• Run HpRmCli Sql analyze to list the out-of-sync entries.
• Verify that the mount point directory exists.
• Alternatively, do not specify a mount directory. If an alternate
directory is not specified, Recovery Manager uses the default
mount directory.
105
Table 4 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued)
Event ID
Event Message
Description/Action
5325
RMS5325: ERROR: The virtual copy
timestamp does not exist for the
snapshotset ID.
When you created the virtual copy, Recovery Manager could
not store the virtual copy timestamp in the repository for the
specified snapshotset ID.
• Wait a few minutes and then retry the operation.
5326
RMS5326: ERROR: Volume Restore failed. A failure occurred when restoring data using the volume restore
feature. The failure might leave the HP 3PAR StoreServ Storage
System in an inconsistent state.
• If the VLUNs are missing, ensure that they are recreated.
5327
RMS5327: ERROR: One or more of your
volumes are on dynamic disks. Dynamic
disks are not supported.
Some of the database or log files are stored on volumes created
on dynamic disks.
• Ensure that the database and log files reside on volumes
created on basic disks.
5328
RMS5328: ERROR: One or more of your Some of the database or log files are stored on the system
databases are on the system volume. You volume.
cannot create virtual copies of system
• Ensure that the database and log files are on HP 3PAR virtual
volumes.
volumes.
5329
RMS5329: ERROR: The destination file
already exists. Please specify a different
restore location and try the operation
again.
Performing a restore from backup does not overwrite an existing
copy of the same file.
RMS5332: ERROR: Could not find the
SQL Writer. Either the Writer is not
installed or is currently not running.
SqlServerWriter was not found on the SQL Server.
5332
• Verify that the specified restore folder is empty and try the
operation again.
• Run the vssadmin list writers command and verify
that SqlServerWriter is listed.
• Ensure that the SQL Writer service is in the Running state.
5333
RMS5333: ERROR: Remote Copy groups
are not configured. A Remote Copy group
must be present in order to perform this
operation.
There are no Remote Copy volume groups configured on the
HP 3PAR StoreServ Storage System. Ensure the Remote Copy
volume group is configured before you create a remote virtual
copy.
• Check the Remote Copy configuration and HP 3PAR
StoreServ Storage System setup.
• Consult the HP 3PAR InForm OS CLI Administrator's Manual
or the HP 3PAR Management Console Help for details on
setting up and checking Remote Copy functionality.
5335
RMS5335: ERROR: Mount point drive
letter is already in use.
The specified mount point drive letter is already in use.
• Be sure to specify an unused drive letter as a mount point
when you enter the HpRmCli Sql mount command.
5336
RMS5336: ERROR: Mount point directory The specified mount point is not a directory.
is not a valid directory.
• Be sure to specify a valid directory as a mount point when
you enter the HpRmCli Sql mount command.
5337
RMS5337: ERROR: Mount point directory The mount point directory specified already contains files.
is not empty.
• Be sure to specify a valid directory as a mount point when
you enter the HpRmCli Sql mount command.
5339
RMS5339: ERROR: Failed to execute the
3PAR CLI.
The HP 3PAR Command Line Interface (CLI) command failed.
• Check the error message for more details on the failed
command.
• Verify that you can connect to the required HP 3PAR
StoreServ Storage System from the CLI command window.
106 Event Messages
Table 4 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued)
Event ID
Event Message
Description/Action
5341
RMS5341: ERROR: Could not find the
header information in the command
output.
Failed to parse the header information from the CLI command
output.
• Verify that you can connect to the required HP 3PAR
StoreServ Storage System from the CLI command window.
• Wait a few minutes and try the operation again.
5347
RMS5347: ERROR: Failed to locate
Symantec NetBackup installation information could not be
NetBackup installation. Please make sure retrieved from the registry.
NetBackup is correctly installed.
• Verify that NetBackup is properly installed and that you have
access to the registry entry.
• Use Add/Remove Programs to confirm that NetBackup is
installed.
5348
RMS5348: ERROR: Could not find
NetBackup start and end scripts.
The NetBackup start or end scripts could not be found in the
HP 3PAR Recovery Manager for SQL installation folder.
• Ensure that the bpstart_notify.bat and
bpend_notify.bat files are present in the HP 3PAR
Recovery Manager for SQL installation folder.
5349
RMS5349: ERROR: Failed to create or
open backup include file for NetBackup.
Unable to open or create the NetBackup include file for the
specified policy. You can run only one backup job per policy
at a time on a NetBackup client.
• Ensure that no other HpRmCli Sql backup command with
same policy is running. Wait for the prior backup command
to complete and try again.
5351
5354
RMS5351: ERROR: NetBackup restore
process has failed.
The NetBackup restore failed.
• On the NetBackup server, check the application event log
and NetBackup logs.
RMS5354: ERROR: The SQL database
SqlServerWriter could not find the specified database in its list
was not found in the SQL Writer database of databases supported for backup.
list.
• Verify that the database is online and attached.
• Ensure that the database is not a snapshot/mirrored
database.
5356
RMS5356: ERROR: The expiration time
is out of range (0h - 43,800h).
The expiration time for a virtual copy must be a value between
0 and 43,800 hours (or between 0 and 1825 days).
• Try again, using a value within the range allowed.
5364
RMS5364: ERROR: Failed to back up the The NetBackup backup process has failed.
virtual copy. Please consult the backup
• For more details, check the application event log and
progress logs for details.
NetBackup logs on the NetBackup server.
5367
RMS5367: ERROR: Unknown error
encountered. Please look at the logs for
more information.
An unexpected error occurred.
RMS5370: ERROR: The specified policy
does not exist in the NetBackup
configuration database.
The policy was not found in the NetBackup database.
5370
5371
• For more details, check the logs in the HP 3PAR Recovery
Manager for SQL installation folder and the event logs.
• Verify that the policy is valid.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
RMS5371: ERROR: The specified schedule The schedule was not found in the NetBackup database.
does not exist in the configuration
• Verify that the policy is valid.
database.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
107
Table 4 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued)
Event ID
Event Message
Description/Action
5372
RMS5372: ERROR: Failed to connect to
the NetBackup master server.
Recovery Manager could not connect to the NetBackup server.
• Ensure that you can connect to the NetBackup master server.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
5373
RMS5373: ERROR: No storage units
available for use.
The backup cannot be created because no storage units are
available.
• Ensure that the storage units are configured and available
for use.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
5374
RMS5374: ERROR: The specified policy
is not a valid client type.
The process cannot continue because the policy is not a valid
client type.
• Ensure that the policy is a valid client type.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
5375
RMS5375: ERROR: This operation is not
allowed at this time.
The NetBackup server is not currently allowing this operation.
• Wait some time and try the operation again.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
5376
RMS5376: ERROR: The specified client
does not exist in the specified policy.
Recovery Manager cannot locate the client in the policy
specified.
• Verify that the client is correctly configured for the specified
policy.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
5377
RMS5377: ERROR: The specified policy
is not active.
To create backups, the policy used to create the backup must
be active.
• Verify that the specified policy is active.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
5378
RMS5378: ERROR: The current InForm
OS does not support the specified
command.
The command you entered is not supported in this version of
the HP 3PAR Operating System Software.
• Ensure that the correct commands are used for the installed
InForm OS.
• Upgrade the InForm OS to a version that allows you to use
the specified command.
108 Event Messages
Table 4 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued)
Event ID
Event Message
Description/Action
5379
RMS5379: ERROR: Failed to mount virtual HP 3PAR Recovery Manager for SQL failed to mount the virtual
copy. Please check the application and
copy.
system event logs for the most recent error. • Check the application and system event logs for the most
recent error messages.
5380
RMS5380: ERROR: Failed to create virtual HP 3PAR Recovery Manager for SQL failed to create the virtual
copy. Please check the application and
copy.
system event logs on the SQL server for
• Check the application and system event logs on the SQL
the most recent error.
server for the most recent error messages.
5381
RMS5381: ERROR: Failed to locate Data
Protector installation. Please make sure
Data Protector is correctly installed.
The HP Data Protector installation information could not be
retrieved from the registry.
• Verify that Data Protector is properly installed and that you
have access to the registry entry.
• Use Add/Remove Programs to confirm that Data Protector
is installed.
5382
RMS5382: ERROR: Could not find Data
Protector post script.
The Data Protector post script could not be found in the HP 3PAR
Recovery Manager for SQL installation folder.
• Ensure that the dpend_notify.bat file is present in the
HP 3PAR Recovery Manager for SQL installation folder.
5383
RMS5383: ERROR: Datalist not found or The specified datalist could not be found or access was denied.
SYSTEM account does not permit backup • Ensure that the correct name is specified for the datalist.
from this client. Please select <Any> while
• Ensure that the SYSTEM account has permission to run backup
configuring the client system.
processes from the specified client.
• Use the Data Protector Manager GUI to configure client
permissions.
109
Table 4 HP 3PAR Recovery Manager Software for Microsoft SQL Server Event Messages (continued)
Event ID
Event Message
Description/Action
5384
RMS5384: ERROR: Error encountered
while running the Data Protector
command.
Data Protector failed to execute the specified command.
• For more details, check the Data Protector logs on the Data
Protector Cell Manager server.
5385
RMS5385: ERROR: The Data Protector
The Data Protector Session ID to restore was not found for the
Session ID was not found in the repository timestamp specified.
for the given timestamp. Please ensure
• Ensure that the backup timestamp does not belong to another
that the correct Vendor Type is specified.
backup vendor (for instance, Symantec NetBackup).
5386
RMS5386: ERROR The NetBackup policy The NetBackup policy to restore was not found for the timestamp
was not found in the repository for the
specified.
given timestamp. Please ensure that the
• Ensure that the backup timestamp does not belong to another
correct Vendor Type is specified.
backup vendor (for instance, HP Data Protector).
5387
RMS5387: ERROR: Failed to set the disk Could not set the disk in maintenance mode because the disk
in maintenance mode because the disk is is offline.
offline.
• Ensure that the disk to be restored is online before you run
the volume restore operation.
5388
RMS5388: ERROR: Failed to set the disk
in maintenance mode.
Could not set the disk in maintenance mode.
• Ensure the disk is online and can be put in maintenance
mode.
• Troubleshoot using the cluster command:
cluster res <resource-name> /maint:on
5391
RMS5391: ERROR: The synchronous
A synchronous HP 3PAR Remote Copy Software operation was
Remote Copy option is disabled in the HP requested, but the syncrc option is disabled in the HP 3PAR
3PAR VSS Provider configuration.
VSS Provider configuration.
• Enable the syncrc configuration for HP 3PAR VSS Provider
Software using the following command:
provcfg conn -syncrc Yes
110
Event Messages