advertisement
HPE Recovery Manager Central 4.0.0 for
Microsoft SQL User Guide
Abstract
The guide is intended for database administrators who are responsible for backing up databases.
This document provides information about how to install, configure, and use HPE Recovery
Manager Central for Microsoft SQL server databases with HPE 3PAR StoreServ Storage system and HPE Express Protect Backup.
Part Number: 837755-004
Published: April 2017
Edition: 1
©
2015, 2017 Hewlett Packard Enterprise Development, L.P.
Notices
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise 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. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise 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.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Microsoft
®
and Windows
®
are trademarks of the Microsoft group of companies.
VMware
®
, VMware
®
vCenter Server
®
, and VMware vSphere
®
Web Client are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.
Adobe
®
and Acrobat
®
are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
All other trademarks and registered trademarks are owned by their respective owners.
Contents
Overview.......................................................................................................8
Licensing.................................................................................................... 10
Installing RMC-S........................................................................................ 11
Upgrading and migrating to RMC-S.........................................................18
Configuring RMC-S....................................................................................21
Configuring Protect Software...................................................................25
Microsoft SQL server transaction logs....................................................32
Contents
3
Working with RMC-S graphical user interface........................................38
4 Contents
Using RMC-S Command Line Interface................................................... 87
Recovery for Microsoft SQL Server....................................................... 115
Coexistence of RMC-S and HPE 3PAR Recovery Manager for
Exchange..................................................................................................121
Using HPE 3PAR Peer Motion Manager Software with RMC-S............122
Contents
5
Remote Copy for RMC-S......................................................................... 123
Remote copy with and without peer persistence support using single RMC........................ 130
Using HPE 3PAR CLX with RMC-S.........................................................133
Troubleshooting.......................................................................................135
6 Contents
Websites................................................................................................... 147
Support and other resources................................................................. 148
RMC registration tool.............................................................................. 151
Server Virtualization Environments....................................................... 153
Importing/restoring interface server catalog dumps........................... 154
RMC-S error codes.................................................................................. 156
Event Messages.......................................................................................157
Glossary................................................................................................... 162
Contents
7
Overview
The HPE Recovery Manager Central for SQL (RMC-S) allows SQL Server administrators to protect SQL
Server instances and databases with application-consistent recovery points. The application-consistent snapshots are created, scheduled, and managed on HPE 3PAR StoreServ. The RMC Express Protect feature provides a second-tier of data protection with backup from HPE 3PAR StoreServ to HPE StoreOnce. Backups to HPE StoreOnce are self-contained volumes, de-duplicated to save space, and can be used to recover back to the original or a different HPE 3PAR StoreServ array, even if the original base volume is lost.
You can use RMC-S with either HPE StoreOnce, HPE Data Protector, Symantec NetBackup, or Symantec
Backup Exec to protect and restore the snapshot created by RMC-S.
RMC-S environment consists of:
• RMC VM. To deploy the RMC VM, see Recovery Manager Central User Guide.
• Interface server component.
• Agent component in interface and production servers.
To install the components, see Installing RMC-S.
NOTE:
RMC-S does not support Microsoft SQL Server offline backup.
Major features of RMC-S
• Volume Shadow Copy Service supports Full backup type, copy-only backup type for secondary
AlwaysOn databases.
• Recovery Manager CLI.
• MS SQL Server mixed mode authentication.
• Support for Snapshot and HPE StoreOnce protects of SQL transaction logs.
• Snapshot operations on SQL instance and database level.
• Remote Copy Snapshot
◦ Remote copy Snapshot for SQL AAG, SQL Cluster, and SQL Standalone Instance and database.
◦ HPE 3PAR Peer Persistence support for Remote Copy configurations.
◦ Remote Copy in synchronous mode, asynchronous mode, or asynchronous periodic mode.
• RMC-S Snapshot and Express Protect policy creation.
• Snapshot creation of Availability Group databases in Microsoft SQL Server 2012, 2014 and 2016.
• Database Snapshot consistency check support.
• Scheduling and management of automated tasks.
• Mount Snapshots locally or remotely.
• Attach or detach a database to any SQL Server.
◦ Remote mounting and verification of RMC-S snapshot.
• Unmount Snapshots.
• Delete Snapshots and Express Protects in bulk.
• Restore
◦ File copy restore with advance options.
◦ Selective restore of databases from instance level Snapshot.
◦ Automate the point of failure restoration process.
◦ Volume Restore.
• Virtual Copy creation of Availability Group databases in Microsoft SQL Server 2012, 2014.
• Protect using HPE StoreOnce, HPE Data Protector, Symantec NetBackup, or Symantec.
8 Overview
Backup Exec.
• Protect restore
◦ Protect restore using HPE StoreOnce
– StoreOnce Protect restore to parent volume.
– StoreOnce Protect restore to any volume.
◦ HPE Data Protector Media restore.
◦ Symantec NetBackup media restore.
◦ Symantec Backup Exec media restore.
• Support for using HPE 3PAR StoreVirtual virtual lock with RMC-S snapshots.
• Manage production servers having different versions of SQL Servers with single interface server.
• Support for Virtual FC (vFC) in production server and interface server.
• Coexistence of HPE 3PAR StoreServ VVSET and HOSTSET.
• Support for Server Virtualization using iSCSI, VMDirectpath.
• Support for HPE 3PAR Cluster Extension (CLX) configuration.
• Support for coexistence with HPE 3PAR StoreServ Recovery Manager for Exchange software.
• Support for SQL database residing on Volume Mount Point (HPE 3PAR volume mounted on a system drive or another HPE 3PAR StoreServ volume).
• Support for concurrent virtual copy or remote virtual copy creations, concurrent backup jobs, and concurrent Virtual Copy or remote Virtual Copy creation with interface jobs.
• Protection of different databases using HPE StoreOnce, Symantec NetBackup, Symantec Backup Exec, or
HPE Data Protector can be taken concurrently. For example, protect of database db1 using Symantec
NetBackup and backup of database db2 using HPE Data Protector can execute in parallel.
NOTE:
• Due to a 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.
Overview
9
Licensing
Licensing is used to enable Recovery Manager for MS SQL product functionality. HPE 3PAR StoreServ arrays are delivered with an All Inclusive license that includes license to use RMC-S. You need to purchase the
RMC Suite Application License if you are using HPE 3PAR StoreServ 7000 Storage and HPE 3PAR
StoreServ 10000 Storage arrays.
License models supported by RMC
Licenses required for accessing RMC-S features.
Recovery Manager for SQL
license or RMC Application
Suite license
HPE StoreOnce Catalyst license
Mandatory licenses required for the RMC-S appliance to communicate with HPE StoreOnce.
Other licenses
• Virtual Copy
• Virtual Lock
• Remote Copy
• Peer Persistence
Virtual Copy license is mandatory to create Snapshot of a volume.
Virtual Lock license is required (optional) to lock Snapshot for a specified time.
Remote Copy license is mandatory for Remote Copy operations.
Peer Persistence license is mandatory for using Remote Copy with
Peer Persistence feature.
For more information on licensing, see SPOCK.
10 Licensing
Installing RMC-S
The RMC-S installation components are:
• Agent component
—Agent or Client is lightweight component that is installed on a production server. Install the agent component on the server where the SQL Server is installed.
• Interface Server Component
—Interface server manages RMC-S jobs requested by user through HpRmCli command or RMC-S GUI. If protect jobs are used, the interface server can be a component (either as a client or a media server) of a backup application configuration. If protect jobs with a backup application are needed, the interface server can be virtual or physical, but must have either iSCSI or Fibre Channel access to HPE 3PAR.
Sample RMC-S connectivity
The following diagram shows the connectivity between various RMC-S components:
RMC VM HPE StoreOnce
HPE
3PAR
SQL
Production
Server
RMC-S Interface Server and ISV Client
Legend:
FC/iSCSI
IP
Deployment scenarios
• Standalone SQL Server
ISV
(DP/NBU/BE)
Installing RMC-S
11
• Availability group
RMC-S supports Microsoft SQL Server 2012, 2014, and 2016 Availability Group databases. In this configuration, each availability group replica is connected to only one HPE 3PAR StoreServ and the HPE
3PAR StoreServ can be same or different than other replicas.
Figure 1: RMC-S with Three Availability Replica Nodes
In figure, RMC-S 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. Snapshot can be created for availability database on primary replica node only through the RMC-S interface server 1 and snapshot for availability database on secondary replica node can be created only through RMC-S interface server 2. If both primary and secondary replica nodes are connected to the same HPE 3PAR StoreServ, then any interface server can be used to create a snapshot. Before you start configuring RMC-S for
Availability Group:
◦ Make sure all the prerequisites for Availability Group are met before discovering Availability Group in
RMC-S.
◦ 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:
Do not change the Availability Group configuration while RMC-S operations are in progress.
Otherwise, the results may be unpredictable.
12 Installing RMC-S
NOTE:
If SQL Server Alwayson group is configured with active primary and secondary readable replicas:
◦ Alwayson user databases on secondary replicas are not visible to RMC-S. You can only see system databases on secondary readable replicas.
NOTE:
If there is any change in the configuration of Availability Group, user must perform a manual rescan in RMC-S.
• Cluster
Enterprise customers deploy cluster environment to scale for failover support. Monitor all the nodes within the cluster. For example, if you have a four node cluster, it is acceptable if three nodes out of this cluster are active. Nodes that are part of SQL cluster must be installed with RMC-S Agent component.
NOTE:
If an RMC-S interface server is running on a Windows server failover clustered node, then RMC-S continues to function unless the cluster node is fully down. The cluster failover has no impact on
RMC-S running on the cluster node. It is because the RMC-S cluster nodes are not clustered aware resources.
Figure 2: Cluster environment
• Remote copy
HPE 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 the data stored there could be
Installing RMC-S
13
lost unless a backup copy can be recovered from a separate location not affected by the disaster. RMC
VM must have network interface configured with valid IP address and subnet for Remote Copy.
NOTE:
Make sure source and target RMC VSAs Network Interface -1 is configured with valid IP address for
Remote Copy to function with RMC-S. For more information on how to configure multi NIC, see HPE
Recovery Manager Central 4.0.0 User Guide.
Installation scenarios
SQL Server and interface server running on different systems – install the RMC-S Agent on MS SQL server, RMC-S Agent and interface server on the interface server, and deploy RMC VM.
Hewlett Packard Enterprise recommends you not to have MS SQL server and interface server running on the same system.
NOTE:
• You can install RMC-S on a local drive, HPE 3PAR StoreServ drive, or a volume mount point.
• You cannot install RMC-S on a mapped network drive.
Installing RMC-S
Prerequisites
For information on installing RMC, see HPE Recovery Manager Central 4.0.0 User Guide.
Ensure that the system and license requirements are met before starting the installation.
Procedure
1. Navigate to the folder containing the RMC-S installer and double-click HPE_RMCS_4.0.0.exe.
2. Click Next.
The License Agreement window appears.
3. Read the end-user license agreement, select I accept the terms in the license agreement, and then click Next.
The Destination Folder window appears.
4. To install RMC-S in the default folder <default drive>:\Program Files\HPE\RMC-S\, click Next .
The Custom Setup window appears. To install RMC-S in a different folder, click Change and select the required folder.
NOTE:
The RMC VSS provider is installed in the <default drive>:\Program Files\HPE\RMC
\Provider folder.
5. Choose one of the following installation types:
• Recovery Manager Agent for SQL Server: To install the agent component of RMC-S on the production server; selected by default.
• Recovery Manager for Interface Server: To install the server component of RMC-S on the interface server.
6. (Optional) Configure Web Extension Port. By default, the web service port number 50001 appears. You can edit this field.
14 Installation scenarios
7. By default, the check box Configure Web Service using HPE provided SSL certificate to configure the certificate is enabled.
The SSL certificate enforces certificate validation by the host (RMC) and client application (interface server) to establish a secure connection. Web server port is used for communication between RMC and the interface server to establish a secure connection.
NOTE:
• You can also use your own OpenSSL version 3 certificate and bind it to the web server port.
• For RMC-S to function, you have to enable the default port number 50001, 9932 (SQL service port) or other changed port numbers in the firewall.
8. Click Install.
9. Click Finish.
NOTE:
After the installation, if HpRmCli commands are not recognized on the interface server, log out and log in.
Verifying the installation
Verifying the RMC-S install
Procedure
1. Click Control Panel > Programs > Programs and Features.
2. Ensure that the following components are installed:
• HPE Recovery Manager Central VSS Provider v4.0.0
• HPE Recovery Manager Central for Microsoft SQL Server v4.0.0
Verifying the SSL certificate
1. Click Start and type mmc.exe in Search.
Console 1 window appears.
2. Click File > Add/Remove Snap-in.
Add or Remove Snap-ins window appears.
3. Click Certificates snap-ins and click Add >.
Certificates snap-ins window appears.
4. Select the option Computer account and click Next.
Select Computer window appears.
5. Click Finish with the default options.
6. Click OK in the Add or Remove Snap-ins window.
7. Click Certificates (Local Computer) > Personal > Certificates.
HPE RMC for SQL with the details appears on the right pane.
Verifying SQL connectivity
To verify that your SQL instances are reachable after you install and configure RMC-S on the interface server and all the production servers:
1. Log on to the interface server as the system administrator.
2. Launch SQL Server Management Studio.
3. In the Connect to Server window, enter or select the following:
Verifying the installation
15
• 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 or SQL Server Authentication.
4. Click Connect.
5. Ensure that the following window appears:
Uninstalling RMC-S
Procedure
1. Click Control Panel > Programs > Programs and Features.
2. Select and uninstall the following components:
a. HPE Recovery Manager Central VSS Provider v4.0.0
b. HPE Recovery Manager Central for Microsoft SQL Server v4.0.0
Creating OpenSSL v3 certificate and binding to web port
Create an OpenSSL v3 certificate only when you want to use your own certificate.
Creating OpenSSL v3 certificate
Run the following commands:
Procedure
1. openssl genrsa -des3 -out rmcs_interface_server.key 1024.
2. openssl req -new -x509 -days 1001 -key rmcs_interface_server.key -out rmcs_interface_server.cer
3. openssl pkcs12 -export -in rmcs_interface_server.cer -inkey rmcs_interface_server.key -out rmcs_interface_server.pfx
Importing the certificate to Windows store
16 Uninstalling RMC-S
1. Install the certificate in service account by selecting MMC > Add Snap-in > Certificates > Computer
Account.
2. To install the certificate, select the store.
3. Right-click the store All tasks > Import .
4. Add the .pfx certificate file.
Binding the certificate to web port
1. If the port is already bound with another certificate, delete the old binding using the command: netsh http delete sslcert ipport=0.0.0.0:[port no].
2. Bind the certificate to the port using the command: netsh http add sslcert ipport=0.0.0.0:
[port no] appId={GUID} certhash=[thumbprint of the certificate]
3. To verify the binding, run the following command netsh http show sslcert ipport=0.0.0.0:
[port no]
Installing RMC-S
17
Upgrading and migrating to RMC-S
Before you start the upgrade, ensure that scheduled jobs are not running in the RMC-S 2.0.0 or RMC-S 3.0.0
setup. If a scheduled job is running, then you must wait for the job to complete and then start the migration.
NOTE: Hewlett Packard Enterprise recommends you not to upgrade multiple RMC VMs in parallel. You should wait for one RMC upgrade to complete and then perform the other upgrades.
For information on upgrading and migrating from RMS 4.x to RMC-S 2.0.0, see HPE Recovery Manager
Central 2.0.0 for Microsoft SQL Migration Guide. For information on upgrading and migrating from RMS 4.x to
RMC-S 3.0.0, see HPE Recovery Manager Central 3.0.0 for Microsoft SQL Migration Guide.
NOTE: The term RMS 4.x used in this document refers to both RMS 4.6.0 and RMS 4.7.0.
You cannot do a direct upgrade from RMS 4.x to RMC-S 4.0.0. You have to first upgrade to RMC-S 2.0.0 or
RMC-S 3.0.0, perform data migration to migrate data to RMC-S 2.0.0 or RMC-S 3.0.0 and then upgrade from
RMC-S 2.0.0 or RMC-S 3.0.0 to RMC-S 4.0.0.
For information on upgrading and migrating from RMC-S 2.0.0 or RMC-S 3.0.0 to RMC-S 4.0.0, see
After you upgrade to RMC-S 4.0.0, the data is automatically made available on the latest version.
For information on upgrading RMC, see HPE Recovery Manager Central 4.0.0 User Guide.
Upgrading to RMC-S 4.0.0
Procedure
1. Perform the following procedure on interface server and SQL server:
a. Run the HPE_RMCS_4.0.0.exe installer package.
RMC-S prompts you to upgrade to the latest version.
b. Click Yes.
c. Follow the wizard and complete the package installation.
2. Perform the following procedure on interface server and SQL server:
a. Select HPE Recovery Manager Central > Settings > Action > Upgrade Appliance.
b. Choose RMC_Master-4.0.0-x.x.el6.noarch.rpm package.
NOTE: For more information on RMC VM upgrade, see HPE Recovery Manager Central 4.0.0
User Guide.
c. Clear the browser cache.
d. Verify that all your data is available on RMC-S 4.0.0 version.
Remote Copy snapshots
Migrating Remote Copy snapshots is similar to migrating local snapshots.
NOTE:
In a Remote Copy configuration, Hewlett Packard Enterprise recommends you not to use any secondary interface server as a production server on the primary interface server side.
18 Upgrading and migrating to RMC-S
Nonsynchronous long-distance configurations
This section describes migrating Remote Copy snapshots for nonsynchronous long distance (non-SLD) configurations.
Source Target
RMC-S GUI
RMC-S GUI
IP
IP
Interface
Server 1
Interface
Server 2
RMC VM-I RMC VM-II
Deploy RMC VM using vCenter Server/
Microsoft Hyper-V
IP
IP
Deploy RMC VM using vCenter Server/
Microsoft Hyper-V
Application
Servers
Network (IP)
Application
Servers
Figure 3: Nonsynchronous long-distance Remote Copy environment
Procedure
1. Install RMC-S 4.0.0:
a. Install RMC-S Agent on source SQL server.
b. Install RMC-S Agent and interface on source interface server.
c. Install RMC-S Agent on target SQL server.
d. Install RMC-S Agent and interface on target interface server.
2. Upgrade RMC VM-I and RMC VM-II as shown in figure.
NOTE:
After you upgrade to RMC-S 4.0.0, the Remote Copy data is automatically made available on the latest version.
Synchronous long-distance configurations
This section describes migration of Remote Copy snapshots for synchronous long distance (SLD) configurations.
Nonsynchronous long-distance configurations
19
Figure 4: Synchronous long-distance Remote Copy environment
Procedure
1. Navigate to the folder containing the RMC-S installer, double-click the HPE_RMCS_4.0.0.exe, and perform the following steps:
a. Install RMC-S Agent on the source application server.
b. Install RMC-S Agent and interface on the source interface server.
c. Install RMC-S Agent on Target–1 application server.
d. Install RMC-S Agent and interface on Target–1 interface server.
e. Install RMC-S Agent on Target–2 application server.
f. Install RMC-S Agent and interface on Target–2 interface server.
2. Upgrade RMC VM-I, RMC VM-II, and RMC VM-III as shown in figure.
NOTE:
After you upgrade to RMC-S 4.0.0, the Remote Copy data is automatically made available on the latest version.
Recommendation (Optional)
In the following scenarios, the new Remote Copy snapshot creation or migrated scheduled job snapshot creation might fail and display an error message:
• If you have SLD Remote Copy associated with an instance or database, then you must set the default storage system using RmcRegistration.exe on target interface if target interface server RMC manages both the target HPE 3PAR storage systems.
• If target interface server RMC manages only one target HPE 3PAR storage system, then you need not set the default storage system using RmcRegistration tool. You can ignore this step.
20 Upgrading and migrating to RMC-S
Configuring RMC-S
Before you configure RMC-S, ensure that the RMC VM, SQL server, and RMC-S Interface server are timesynced.
• Configure the following on the interface servers:
◦ TCP/IP port. For information see, Configuring the TCP/IP port.
◦ SQL Servers in the same active directory domain or across multiple domains.
◦ HPE 3PAR StoreServ shared drive for backing up transaction log backup.
• Configure the following on the SQL server:
◦ Maintain a 1:1 relationship between databases and volumes.
– Do not add more than one database and its transaction log files to a volume.
– Avoid adding files from a database to multiple volumes.
◦ SQL instance and database
◦ SQL server user login account with Sysadmin server role.
• Configure the following on both interface and SQL servers:
◦ Disable automount. For information, see Disabling automount.
◦ Set Windows PowerShell Remote Execution Policy. For more information see, Prerequisites.
• Configure one of the following for Remote Copy:
◦ Synchronous Remote Copy
◦ Asynchronous Streaming
◦ Asynchronous periodic Remote Copy
◦ Synchronous long distance (SLD) Remote Copy
NOTE:
• The HPE 3PAR StoreServ Storage System source volumes used by RMC-S must be base volumes.
RMC-S cannot use physical copies or snapshots as source volumes.
• RMC-S does not support non-English languages for domain, instance, database, and pathname.
Configuring the TCP/IP port
The RMC-S interface server uses 50001 as the default port to run the web service. If port 50001 is not available, you can use any available port from 50001–52000.
Procedure
1. Log in to the Interface Server, and use the HpRmCli portconfig command to change the web service port.
HpRmCli Sql portconfig -s <production_server> -s WebPort <port_number>
2. Bind the SSL certificate to the web port.
3. Log in to RMC GUI and select Add Interface Server .
4. Update the port number in the Port field.
5. From the Windows Service console, restart the HPE RMC for Microsoft SQL service.
NOTE:
Use the changed port number in the RMC GUI when registering the interface server. Also ensure that the new ports are enabled in the firewall.
Configuring RMC-S
21
Disabling automount
RMC-S is not compatible with Windows automount feature. To disable automount feature:
Procedure
1. Open a cmd window.
2. Enter diskpart.
3. Enter automount disable.
4. Exit the command prompt window.
Support for SQL servers across multiple Active Directories
Assume that you have multiple SQL servers in a domain. You may have two such nontrusted domains running in two different sites. RMC-S enables you to discover the active SQL server instances across different domains. RMC-S 4.0.0 does not mandate you to save cross domain hostname, username, and password in
Manage Windows Credential options available in the control panel.
Before you create Snapshots, Backups or schedule tasks, ensure the following:
• Systems in two nontrusted domains are able to resolve each other using the commands ping, nslookup and reverse nslookup test.
• For ISV backups, the ISV client, master server, media server, and cell manager must be in the same domain.
• In the AlwaysOn database configuration, your primary replica and secondary replica must be a part of same domain.
NOTE: When registering the interface server and SQL server, ensure that you specify the NETBIOS. If you do not configure RMC-S, then you might encounter unspecified error when executing RMC-S operation.
Grouping Volumes and Hosts into HPE 3PAR StoreServ
Autonomic Groups
You can group virtual volumes and hosts into HPE 3PAR StoreServ volume group and Host set group. In a volume or Host set, place one of the following:
• One database and its log files
• One instance and its related files
• Do not place unrelated volumes in a volume set.
Understanding the Registry
After RMC-S is successfully installed, information is written into the registry database in:
HKEY_LOCAL_MACHINE\SOFTWARE\HPE\RMC-S.
CAUTION:
Do not edit the registry key value unless asked by your local service provider for support purposes.
22 Disabling automount
Table 1: System Registry Values for RMC-S
Name
AnalyzeInterval backupTimeout
Build
DataFilePath
InstallPath
LogFilePath
PackageType
TraceHistory
TraceLevel
TraceLog
TraceLogSize
PortNo
PromoteTimeout
Version
VolumeRestoreMaxRetry
TransactionLogPath
VerificationTimeout
Value
Interval in minutes between automatic synchronization of the repository with
HPE 3PAR StoreServ. The default interval is 60 minutes.
To confirm that NetBackup has received the Protect request, Protect process timeout value in minutes.
Build number of the installed version of RMC-S.
Location of the XML repository.
HPE 3PAR StoreServ RMC-S installation path.
Tracing log files.
Specifies installed features of RMC-S.
Number of trace files to keep before deleting.
Trace level for the log file.
Information used to generate the trace file name.
Size of the log files.
Port used by RMC-S PortNo is set to 9932 by default.
Time interval in seconds to monitor the status of volume restore operation.
Current version of HPE Recovery Manager Central for Microsoft SQL.
The maximum number of retries to find the restored disks after a volume restore operation.
This field is created in the registry if you have configured the transaction log folder.
The time required to perform db integrity check using DBCC. The default is 24 hours.
NOTE:
• The DataFilePath field is created in the registry database only after you launch the RMC-S GUI for the first time.
• An installation log file is created in the %Temp% folder for troubleshooting purposes.
Link and launch RMC-S GUI from MS SQL Studio
You can integrate or launch the HPE RMC GUI from the MS SQL studio by using the Add-in feature.
To link RMC:
Link and launch RMC-S GUI from MS SQL Studio
23
Procedure
1. Close the MS SQL Management Studio GUI.
2. Run the batch script placed in the interface server location <installed directory>\RMC-S\SQL
\setup_HPERMCSQL_addin.bat or For Upgrade—The location is <installed directory>\3par
\RM\SQL\setup_HPERMCSQL_addin.bat.
3. Launch HPE RMC GUI as shown in Link and launch.
Figure 5: Link and launch
You can also launch the HPE RMC GUI from the Tools menu as shown in Link and launch — Tools
Figure 6: Link and launch — Tools
Considerations
• RMC link and launch are not supported for MS SQL Management Studio 2008 GUI.
• Do not remove or unload the HPE toolbar or menu option containing the link RMC Link and Launch. If removed, the Link and Launch MS SQL Add-in fails to reload or might behave unexpectedly.
• RMC link and launch is a third-party extension to SQL Server Management Studio. Microsoft does not support such extensibility, so there may be issues with backward/forward compatibility. For more information on the support extensibility, see For SQL Server 2012.
• Microsoft does not support SQL Server Management Studio installations with SQL Server Management
Studio extensions present. If you have installed SQL Server Management Studio extensions, remove them before calling Microsoft Customer Support about a SQL Server Management Studio issue.
• Remove the extension before upgrade.
24 Configuring RMC-S
Configuring Protect Software
You can configure either the HPE StoreOnce, HPE Data Protector, Symantec NetBackup, or Symantec
Backup Exec to protect and restore the snapshots created by RMC-S.
NOTE:
Make sure that your protect software and interface or production servers are in Active Directory. If the interface server is in one Active Directory and protect software is in another directory, then protect operation will fail.
Configuring Symantec NetBackup
RMC-S supports full backups when running on a Symantec NetBackup master server. RMC-S also supports user-defined backups when running on a NetBackup client machine.
Deployment scenarios for Symantec NetBackup provide the deployment scenarios for Symantec
NetBackup.
Table 2: Deployment scenarios for Symantec NetBackup
Scenario
1
2
3
4
Interface Server
Symantec NetBackup Client
Symantec NetBackup Client, Symantec
NetBackup Master Server, and Symantec
NetBackup Media Server
Symantec NetBackup Client and Symantec
NetBackup Master Server
Symantec NetBackup Client and Symantec
NetBackup Media Server
Other server
Symantec NetBackup Media Server and
Symantec NetBackup Master Server
Not Applicable
Symantec NetBackup Media Server
Symantec NetBackup Master Server
To configure Symantec NetBackup to protect and restore snapshots created by RMC-S, set the following parameters during the configuration process:
Backup Policy Parameter
Policy type
Clients
Setting
MS-Windows
Select the machine on which the RMC-S Interface Server component is installed.
Add the client to Protect policy by entering NetBIOS name.
Collect disaster recovery information for
Bare Metal Restore
Ensure that this option is not selected.
Table Continued
Configuring Protect Software
25
Backup Policy Parameter
Type of backup
Starting times for backups
Setting
Full backup
Add a user-defined backup.
Activate all the time slots:
• Modify Day : Monday
• Start Time : 12:00:00
• End Day : Monday
• End Time : 12:00:00
• Duration (days) : 7
Considerations
• If the interface server is running on the same system as Symantec NetBackup client, Symantec
NetBackup cannot validate the policy.
• If you add the Symantec NetBackup path to the PATH environment variable after installing HPE 3PAR
StoreServ, you must restart the appliance for the changes to take effect.
• If RMC-S 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 HPE Data Protector
To use HPE Data Protector with RMC-S, you must set up a default backup specification. The backup specification specifies the default mount point and the necessary devices for tape backup. Each backup specification must be unique across the entire system.
Deployment scenarios for HPE Data Protector provide the deployment scenarios for HPE Data Protector.
Table 3: Deployment scenarios for HPE Data Protector
Scenario
1
2
Interface Server
HPE Data Protector Client
HPE Data Protector Client and HPE Data
Protector Cell Manager
Other server
HPE Data Protector Cell Manager
Not applicable
To configure HPE Data Protector to protect and restore snapshots created by RMC-S:
Procedure
1.
Open the Data Protector GUI.
2.
Select Backup > FileSystem > 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.
NOTE:
Create the device before you run the backup wizard.
6.
Click Next until the Manual add... appears.
7.
Click Manual add...
26 Configuring HPE Data Protector
8.
Select Windows filesystem and click Next.
9.
Enter the appropriate client system, mount point, and description. HPE recommends:
Client system
<server_used_as_backup_client>
Mount point
C:
Description
default
NOTE:
RMC-S uses this information only to create a backup template. RMC-S 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 (for example, DPbackup) as the value of the -dl option.
Configuring Cell Manager Access
To use HPE Data Protector with RMC-S, you must enable the system accounts on the registered client system to access the Data Protector Cell Manager.
Procedure
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>.
Configuring Symantec Backup Exec
Table 4: Deployment scenarios for Symantec Backup Exec
Scenari o
1
Interface Server
Symantec Backup Exec Remote Agent for Windows and Symantec Backup Exec Administration Console.
Other server
Symantec Backup Exec Remote Media
Server
2 Symantec Backup Exec Media Server and Symantec
Backup Exec Administration Console.
Not Applicable
Prerequisites
Procedure
1. Symantec Backup Exec Media server on RMC-S interface server
a. Symantec Backup Exec software
b. Symantec Backup Exec Media server user name and password must be same as the interface server, or you must add the current user to Backup Exec.
2. Symantec Backup Exec Remote Media server
Configuring Cell Manager Access
27
a. Symantec Backup Exec Remote media server must be installed on the same domain.
b. The interface server must be installed with Symantec Backup Exec Remote Agent for Windows.
I.
Install media server on RMC-S production server.
II.
Install remote agent from the production server to the interface server.
III.
(Optional) Install Backup Exec Administration Console on media server or RMC-S interface to perform Backup Exec administration task. The Backup Exec Administration Console is the interface to control a Backup Exec server.
NOTE:
If you are using a 2014 or 2015 version of Symantec Backup Exec, then the Set-
ExecutionPolicy in PowerShell cmdlet enables you to determine the Windows PowerShell scripts (if any) that are allowed to run on your computer. For 2014 and 2015 versions of Symantec
Backup Exec support, if remote execution policy is disabled, then enable it by running Set-
ExecutionPolicy RemoteSigned on RMC-S interface server.
c. Add the Symantec Backup Exec agent using host NetBIOS name.
d. To enable MS PowerShell Remoting feature in Symantec Backup Exec media server, do the following:
I.
Start the Windows PowerShell commandlet as an administrator.
II.
Run the command Enable-PSRemoting –force.
III.
Run the command winrm s winrm/config/client
'@{TrustedHosts="RemoteComputer"}'
Remote computer is the NetBIOS name of RMC-S interface Server.
IV.
Run the command winrm quickconfig.
e. To execute the PowerShell commands remotely, increase the memory of PowerShell commandlet. Do the following:
I.
Run the command sl WSMan:\localhost\Shell
II.
Run the command Set-Item .\MaxMemoryPerShellMB 2048
III.
Exit the PowerShell prompt using the command exit.
IV.
Restart Windows remote management (WS-Management) on media server.
f. Do the following on RMC-S interface server:
I.
Start the Windows PowerShell commandlet as an administrator.
II.
Run the command Enable-PSRemoting –force.
III.
Run the command winrm s winrm/config/client
'@{TrustedHosts="RemoteComputer"}'
IV.
Run the command winrm quickconfig.
g. To support Symantec Backup Exec Remote media server, RMC-S must run with domain administrator privileges. To run the RMC-S with domain administrator privileges:
I.
To open the services, select Windows > Control Panel > Administrative Tools > Services.
II.
Locate and double-click RMC-S service.
28 Configuring Protect Software
Figure 7: RMC-S service
III.
Select Log On tab.
Figure 8: RMC-S SQL Properties
NOTE:
For upgrade, the default installation path is C:\Program Files\3PAR\RM\SQL
\RMListeningAgent_s.exe.
IV.
Select This account. Enter the domain administrator username and password.
Configuring Protect Software
29
Figure 9: RMC-S Properties Account
V.
Click Apply and then select OK. Rrestart the service when asked for.
NOTE:
These changes must be done on all the servers running RMC-S.
3. Symantec Backup Exec
4. Media server user name and password must be the same as the interface server, or you must add the current user to Backup Exec.
Configuring device backups
To use Symantec Backup Exec with RMC-S, either remote administrator console or typical setup
(mediaserver, administrator console) must be installed on the interface server. Device must be configured in
Backup Exec for backup.
Procedure
1. Open Symantec Backup Exec administrator console.
2. From the tool bar, select the device you want to back up.
3. To configure the device for backup, follow the onscreen instructions.
Backup considerations
Consider the following while configuring backups:
• Synchronize the backups. Remove protects from RMC-S when they expire.
• If you remove a valid backup from RMC-S, remove the protect from your protect software.
• RMC-S does not track restore progress. Use protect software to monitor restore progress.
• You can use the CLI commands HpRmCli Sql backup, HpRmCli Sql deletebackup, HpRmCli
Sql listbackup, and HpRmCli Sql restore for backup and restore.
• For more information on protecting a snapshot, see Protecting a snapshot.
• For more information on restoring, see Restoring.
When performing concurrent backup operations:
30 Configuring device backups
• Backup of different databases with different policies is allowed when using Symantec NetBackup.
• Backup of different databases is allowed when using HPE Data Protector or Symantec Backup Exec.
• Backups of different databases can be taken concurrently using Symantec NetBackup, HPE Data
Protector, or Symantec Backup Exec. For example, backup of database db1 using Symantec NetBackup and database db2 using HPE Data Protector can execute simultaneously.
Symantec NetBackup considerations
Consider the following for Symantec NetBackup:
• Symantec NetBackup supports Master, Client, and Media modes for tape backups.
• Symantec NetBackup software is case-sensitive. Enter all the policy information proper case.
HPE Data Protector backup considerations
For each HPE 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:
RMC-S does not clean these postscripts. After a backup is complete (either successfully or with failures), remove the associated postscript batch file, if desired.
Symantec Backup Exec backup considerations
Symantec Backup Exec supports media server and remote administrator console for backups.
When backing up or restoring from the media server, monitor the progress using the administrator console.
Symantec NetBackup considerations
31
Microsoft SQL server transaction logs
RMC-S configuration for transaction log backup
RMC-S command-line interface and RMC-S GUI can be used to start or schedule a transaction log backup.
The capacity to retain transaction log backups in your system can also be configured in the update-to-the-
second restore ability.
A full database backup needs to exist each time you initiate a manual or schedule a transaction-log-only snapshot or protect. You can run RMC-S snapshot to perform full snapshot for the database in RMC-S command-line interface or RMC-S GUI.
Due to an SQL attach limitation, transaction log does not support the following:
• Attach and detach of HPE 3PAR StoreServ Snapshot with transaction log.
• Express Protect restore to another volume with transaction log. However you can use the parent Express
Protect time stamp to restore to parent volume or restore Express Protect to any volume.
• Restore with transaction log for Symantec NetBackup, Symantec Backup Exec, or HPE Data Protector
Backup.
NOTE:
• RMC-S supports MS SQL Server recovery model full for transaction log backup support.
• When you initiate a manual or scheduled transaction log backup using RMC-S, the database log is truncated.
HPE 3PAR StoreServ shared path configuration as a repository for transaction log backup
• All MS SQL server instances and database transaction log backup are saved centrally in a shared folder on an interface server.
• Hewlett Packard Enterprise recommends you to use an HPE 3PAR StoreServ LUN in RMC-S interface server for storing transaction log backup files.
NOTE:
Do not keep database or instance files in the transaction log folder. Keeping these files in transaction log drive folder may result in overwriting the instance or database files when a restore operation is performed.
• Share the transaction log drive folder with log in an administrator account.
• All transaction logs for MS SQL Server instance are saved to the transaction log folder. The same transaction log folder is used for backup and restore operation. You must retain transaction log folder and keep sufficient space to save new transaction log backups.
• When your interface server runs in a domain account, ensure that the RMC-S services running on production server runs in the same domain account to facilitate snapshot and transaction log backup.
Configuring RMC-S for transaction log backup
Procedure
1. To add an interface server, click HPE Recovery Manager Central > Interface Servers > +Interface
Servers.
2. Select an interface server from the list and click Actions > Configure Transaction Log Path.
32 Microsoft SQL server transaction logs
3. Enter the share path of transaction log folder that you have created in RMC-S interface server and then save the settings.
RMC-S supports NFS or shared folder with HPE 3PAR StoreServ disk as local drive or path on interface server.
NOTE:
The following Windows shared folder paths are not supported:
• Loopback path, for example, \\localhost\..\ or \\127.0.0.1\...\
• Administrative shares, for example, \\servername\x$
• Other UNC path formats such as \\?\x:\
• Mapped network drives, for example, file://<filename> not supported.
• Loopback or localhost name is not supported. Hidden or Administrative shares, for example, \
\servername\x$ are not supported.
If you have registered more than one interface servers in RMC-S, ensure that each interface server uses the same share drive path and folder for configuring the transaction log path.
4. To validate the path specified after the shared path for transaction log folder is added, click Validate.
Microsoft SQL server transaction logs
33
Figure 10: Transaction log path configuration
5. If validation path test fails, correct the path.
6. Change HPE RMC for Microsoft SQL service as domain administrator account on RMC-S interface server if you have registered RMC-S interface server using a domain account and SQL Servers are running in the same domain account.
7. After a successful validation test, the following details are populated automatically to reflect the following:
RMC Host
The hostname and IP address of registered RMC appliance.
Recovery Set Name
The configured transaction log volume Recovery Set name created by RMC.
Storage System Serial number
The serial number of the HPE 3PAR StoreServ system used to export volume to configure Transaction log folder.
Volume Name
The volume name created in RMC-S interface server for configuring transaction log.
Volume WWN
The WWN name of the configured transaction log volume configured in RMC-S interface server.
Assume that you have selected the transaction log option for Snapshot operation of SQL server database.
In this case, RMC-S first performs a full Snapshot that includes the transaction log backup Snapshot.
If the full Snapshot for SQL server database is available, the subsequent selection of transaction log type of snapshot performs a transaction log backup of SQL server database full snapshot.
Security permission for interface and production servers
Use case 1: RMC-S is configured with single RMC-S interface server
34 Security permission for interface and production servers
• The Interface server name is the host_interface_server.
• The Production server name is the host_production server.
• The HPE 3PAR StoreServ LUN is presented to Interface Server. For example, host_interface_server is configured and assigned a drive path. For example, S:\\TransLog which is a shared folder for administrator with R/W permissions.
• Create the same shared drive path. For example, S:\\TransLog in the interface server B with R/W permissions to the administration account.
• The shared folder path that appears on the interface server is \\host_interface_server\TransLog.
• The shared folder \\ host_interface_server\TransLog must have R/W access to administrator user on host_interface_server and host_production_server.
• The SQL instance service logged on user must have R/W permission on \\host_interface_server
\TransLog folder.
• When interface and production servers are standalone systems and have different administrator account, you must run HPE RMC for Microsoft SQL service on production server host_production_server as
Administrator account of production server host_production_server that has R/W access on shared folder \\host_interface_server\TransLog.
For configuring the transaction log folder using command-line option, see HpRmCli Sql repository
command.
Use case 2: RMC-S environment has two RMC-S interface servers in it. (Remote copy Non-SLD and
SLD configuration)
• At first, configure the transaction log folder on primary interface server IS_host_1. For example, you have configured as \\IS_Host_1\translog on the primary interface server.
• Configure transaction log folder on secondary interface server IS_host_2 same as primary interface server transaction log folder \\IS_Host_1\translog.
• Configure the same primary server shared folder \\IS_Host_1\translog on the second secondary interface server for SLD configuration.
NOTE:
All interface servers must have the same Windows shared folder configuration as transaction log folder for remote copy configuration.
Use case 3: When interface and production servers are cross domain and having different administrator password
Run the credential manager on production server host_production_server(Control Panel\User
Accounts\Credential Manager). Add host_interface_server with administrator account of host_interface_server.
Figure 11: Credential manager
Use case 4: Configuring SQL cluster
Microsoft SQL server transaction logs
35
In the case of SQL cluster configuration, configure the primary node SQL server by running the credential manager. If security issues occur during validation, you might have to perform the same on all other nodes.
NOTE:
If the CREATE DATABASE permission denied in database ‘master’ error occurs, add the sysadmin role in SQL server to the shared folder administrator account using the SQL management studio or any other tool.
Configuring transaction log shared folder
The transaction log folder is not configured by default. Hewlett Packard Enterprise recommends you not to store any database or instance files in the transaction log folder as there might be issues when restoring. The restore of transaction log folder Snapshot or Express Protect overwrites the database or instance files.
If you have already configured the transaction log folder and want to refresh it, do the following:
NOTE:
Refreshing the folder, updates any missing configuration. For example, if a Recovery Set is missing in
RMC, it is recreated.
• Using RMC-S CLI repository command: Use same configured shared path with –f option.
• Using RMC-S GUI:
◦ Reconfigure same configured shared path by appending with /.
◦ Click Validate.
◦ Click OK.
Transaction log creation
RMC-S supports Transaction log backup for a database if the recovery model is FULL. If you change the recovery model for a database, then SQL server prompts you to create a new full Snapshot before you perform a transaction log backup.
A transaction log backup can be initiated at the database level only. If a full Snapshot is unavailable, then the transaction log first creates a full Snapshot and then performs a transaction log backup.
When creating a transaction log backup, a new Snapshot is always created in the following cases:
• You have switched over Remote Copy group in the case of peer persistence configuration or Remote
Copy primary/secondary switching.
• Performing a transaction log backup on a different other interface server.
• If transaction log backup for database is initiated manually or scheduled using remote Snapshot options,
RMC-S ensures that the last Snapshot on local interface server is available on target interface server. If the last Snapshot is unavailable, then RMC-S creates a new remote Snapshot and performs transaction log backup.
• In periodic mode last full Snapshot, RMC-S validates if last Snapshot is available on target interface server. If you have performed transaction log backup after periodic mode Snapshot creation, then transaction log is available only on target interface server for given database. It is because there is no full
Snapshot on local interface server in periodic mode.
36
Transaction log policy
The policy for transaction log backups is derived from the parent full Snapshot. If the transaction log backup has a valid retention time as per the parent full snapshot retention time, then you cannot delete the transaction log backup.
For transaction log backups, the analyse command follows the same policy as that of a full Snapshot. If you can delete the parent full Snapshot using the analyse command, then the associated transaction log backups can also be deleted.
If you edit the time stamp of a transaction log backup for retention or expiration time, then the policy is set to that of parent Snapshot time stamp. It takes effect on all the associated transaction log backups.
Deleting transaction log
If you delete a time stamp that is last in sequence for a database, the new transaction log creation first creates a full Snapshot and then performs a transaction log backup. Deleting the time stamp of a full
Snapshot deletes the full Snapshot and all the associated transaction log backups from the configured transaction log folder. Deleting the time stamp of a transaction log deletes all the associated transaction log time stamp until the next full snapshot time stamp is available.
Transaction log policy
37
Working with RMC-S graphical user interface
The GUI features are a set of interactive tools that are grouped as:
• View
— Enables you to control the information displayed about a resource so that you can focus only on what you are interested in. The View menu is categorized into:
◦ Instance View
—This view displays the databases under the instance, instance level snapshot, and instance level protect.
◦ Database View
—This view displays the databases under the instance, database level snapshot, and database level protect.
NOTE:
For information on the supported browsers, see SPOCK for HPE Storage products.
HPE Storage Systems
HPE Storage Systems enable you to create a point-in-time snapshot of data used for backups. It is an effective way to back up live data or take a snapshot, and then resume live operations.
For more information on adding a storage system, see the HPE Recovery Manager Central User Guide.
HPE Backup Systems
HPE Backup Systems enable you to back up snapshots created on HPE Storage System and store it on HPE
StoreOnce device. It also allows user to create a store on the HPE StoreOnce devices that can be used for backup purpose through RMC.
For more information on adding a backup system, see the HPE Recovery Manager Central User Guide.
Registering a remote appliance
Registering the RMC appliance is a prerequisite for performing any Remote Copy operations. You can register up to eight appliances and also register the same appliance as remote. The appliance user credentials can be edited or the registered appliance can be unregistered.
For more information on adding a backup system, see the HPE Recovery Manager Central User Guide.
HPE Interface Server
Interface server manages RMC-S jobs requested by user through HpRmCli command or RMC-S GUI. If protect jobs are used, the interface server can be a component (either as a client or a media server) of a backup application configuration. If protect jobs with a backup application are needed, the interface server can be virtual or physical, but must have either iSCSI or Fibre Channel access to HPE 3PAR.
Registering an interface server
To register an appliance:
38 Working with RMC-S graphical user interface
Procedure
1. Click HPE Recovery Manager Central > Interface Servers.
2. Click +Interface Servers or Register from Actions menu. To add an appliance, enter the following details:
Figure 12: Registering an interface server
Table 5: Registering an interface server
Title
General
Name
IP Address or Host Name
Port
User Name
Password
Description
Enter the IP address or host name of the interface server.
The port used by the interface server to register.
The port number is set to 50001 by default. However, if you have changed the port number during interface server component installation, then update the port number.
The user name and password of the interface server.
Table Continued
Working with RMC-S graphical user interface
39
Title
Force Register
Name
Application Type
Force Register
Description
The default application type is SQL.
This force registers the RMC-S interface server.
You can force register an interface server in the following cases:
• You have registered the RMC-S interface in one RMC VM and then moved another RMC VM to register the same RMC-S interface Server.
• You have changed RMC VM IP address or hostname. You have to unregister the RMC-S interface server using force option and register the same interface again in the new
RMC VM using force option.
NOTE:
User with administrator privileges can register with the interface server on Windows NT and can manage snapshots (RMC-S operations, such as create, modify, delete) using the RMC-S GUI. You can also use HpRmCli commands, connect to the interface server using a different Windows NT account to manage all snapshots that are available in RMC-S. Also, all Windows NT users with the administrator privileges can manage snapshots (RMC-S operations, such as, create, modify, delete) created by other users and also by the user registered in the interface server. For Remote Copy periodic, synchronous, or asynchronous snapshots the target snapshots will always have the owner name as NT AUTHORITY\SYSTEM.
Figure 13: Owner of Remote Copy Snapshot on source and target Interface
40 Working with RMC-S graphical user interface
Multi user support
You can use hprmcli command to connect to the interface server using the different Windows NT account and to create snapshot. You can also create schedule hprmcli using Windows scheduler or other tool with different Windows NT account. The snapshots are created with different Windows NT user account that is not used during interface server registration in RMC-S.
For example, User_1 can manage User_2 snapshots and perform all the operations.
For Remote Copy periodic/sync/async snapshots, target snapshots have their owner name as NT
AUTHORITY\SYSTEM not as legacy RMS where it appears as connected user (configured through credential manager). Since the owner name is obsolete in RMC-S, this does not fail any operation.
Unregistering an interface server
Procedure
1. Select HPE Recovery Manager Central > Interface Servers.
2. Click Un-Register from Actions menu.
3. Click the check box Force Un-Register when the interface server has communication error with RMC and you want to detach it forcefully from RMC.
4. To unregister the server, click Yes.
NOTE:
You can force unregister an interface server in the following cases:
• RMC-S interface server component is uninstalled and the registered RMC VM remains unchanged.
• A registered RMC-S interface server is unavailable.
• Unregistering an interface server fails with network communication error.
Editing an interface server
Procedure
1. Select HPE Recovery Manager Central > Interface Servers.
2. Click Edit from Actions menu.
3. Make the required changes and click OK.
Connecting to SQL server instances using Windows or SQL
Authentication Mode
Before you begin performing any RMC-S operations using SQL instance or database, connect to your SQL server instances from RMC-S.
Procedure
1. Select HPE Recovery Manager Central > Microsoft SQL Server.
2. Click +SQL Instance.
3. In the Register MS SQL Server Instances screen, specify the following details:
Multi user support
41
Table 6: Register MS SQL Server Instances
Title
Interface Server
Name
Name
SQL Server
Instances
Select Instances
Description
Select Interface Server Name from dropdown list.
From the discovered list of SQL servers, select the SQL server instance that you want to manage.
Table Continued
42 Working with RMC-S graphical user interface
Title Name
Authentication
Add SQL Server
Instances
Add SQL Server
Description
Select the Authentication method for
RMC-S to connect to the SQL server.
• Windows Authentication: Connects to the SQL server using Windows account that runs the SQL server.
• SQL Server Authentication:
Connects to the SQL server using an account defined on the SQL server.
To select this method, the account must have sysadmin server role privileges on the SQL server instance. If selected, you have to specify the SQL authentication username and password.
Adds SQL Server Instances manually.
Specify the name in the format //
<appHostName>/
<appInstanceName>. For example, // host1/instance1.
NOTE:
• If the instance name is not applicable, then specify the name in the format //
<appHostName>. For example, //host1.
• If you have selected the SQL
Server Authentication mode, then specify the name in the format //<appHostName>/
<appInstanceName>/
<username>/<password>.
• For multiple instances, specify a comma-separated list of names.
Table Continued
Working with RMC-S graphical user interface
43
Title Name
Use for Remote Copy
Force Registration Force Register
4. Click OK.
The RMC-S GUI displays the registered SQL server mode:
Description
If enabled, registers the SQL instance as a Remote Copy instance.
Force registers the SQL instance.
You can force register an SQL instance in the following case:
Assume that you want to manage an
SQL server in RMC VM. However, the same SQL server is managed by another RMC VM. When registering the
SQL server in the second RMC, the error message The SQL server is already managed by another RMC
VM is displayed. You can force register the SQL server.
44 Working with RMC-S graphical user interface
NOTE:
• In Microsoft SQL Server, the role of system administrator is not selected by default for NT account
(NT AUTHORITY\SYSTEM), for 2014, 2012, 2008 R2, or 2008. For RMC-S to operate in the
Windows authentication mode, you must configure the system administrator role if it is not enabled.
• Assume that in a multi domain environment, one interface server runs in domain1 and the production server runs on domain2 (both are nontrusted but able to resolve each other using name resolution).
In this environment, when registering the SQL server instance in mixed windows mode of authentication, ensure that RMC-S service runs in domain2 account on the production server. It is because domain2 user account has login privileges in SQL server.
• RMC-S 4.0.0 does not support the following authentication types in Microsoft SQL Server 2016:
◦ Active Directory Universal Authentication
◦ Active Directory Password Authentication
◦ Active Directory Integrated Authentication
Changing the authentication mode
To change the authentication type of an already registered SQL server instance, do the following:
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Un-Register SQL Instance.
3. Click UnRegister.
4. Click OK.
5. Register the SQL Server Instance with a different authentication mode.
For more information on registering the SQL Server instance, see Connecting to SQL server instances
using Windows or SQL Authentication Mode.
NOTE:
By changing the authentication type of an SQL server instance, you do not lose the snapshots or protects created on the instance. After changing the authentication type, you can still use the same snapshots or protects on the instance to perform RMC-S operations.
Instance registration for Remote Copy
To register an instance:
Procedure
1. Register the same SQL instance on primary and secondary. Choose Use for Remote Copy option for secondary.
2. If there is new database to be included for Remote Copy, you must rescan the instance in the primary interface server as well on the remote interface server.
3. You must be able to perform other standalone operations on primary interface server for the same instance.
The following cases explain the instance registration for Remote Copy.
Case 1
• Modifying the existing registered standalone instance as remote copy Instance.
Changing the authentication mode
45
◦ If an instance is not registered on the primary site, you must register the instance using Force Register option. At the remote site, use Remote Copy to register the SQL instance.
◦ If an instance is registered (as managed/unmanaged) on the primary site, reregister the instance using
Force Register option on the primary site. At the remote site, use Remote Copy to register the SQL instance.
NOTE:
If instance is not listed, add the instance as it is already registered.
Case 2
Modifying the existing Remote Copy instance as standalone instance. Unregister the instance on the primary site and on the secondary site and register the instance on the required site with Force Register option.
Unregistering SQL Server instances
To remove a server instance from the list of registered servers:
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Un-Register SQL Instance.
Unregister MS SQL Server Instances page appears.
3. Click UnRegister.
Figure 14: Unregister MS SQL Server instances
46 Unregistering SQL Server instances
4. Select an instance and click Remove.
NOTE:
In SQL Server instance if snapshots or protect objects exist, then unregistering puts the SQL Server instance in an unmanaged state.
5. Click OK.
Setting RMC-S policy
RMC-S applies policy settings at the instance level where each instance can have its own policy. In addition, you can configure individual snapshot with their own policy settings.
How RMC-S policies work
The RMC-S 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 snapshot cannot be removed (if you have a Virtual Lock license).
NOTE:
Modifications made to an existing policy are not retroactive. Snapshots 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 snapshots and Express
Protect allowed per database and per instance. By default, all numeric based policy permits you to create a maximum of 10 snapshot and 10 Express Protect per database and instance.
To remove the oldest Snapshot for each database and instance, after the maximum limit of snapshot is reached, enable the fields Remove the oldest Snapshot and Express Protect before creating a snapshot and Express Protect.
NOTE:
In case the oldest Snapshot is in mounted state and you have already reached the policy limit, you may have to select lose policy check box in Create Snapshot or Create Protect windows that allows you to create Snapshot even though policy limit is reached and oldest snapshot is in mounted state.
Expiration-based policies
If you choose an expiration-based policy, you can set RMC-S to remove snapshot after a specified period has elapsed.
If you specify an expiration time for a remote snapshot:
• If Remote Copy is set up in periodic mode, RMC-S sets the expiration time for the remote snapshot on the
Remote Copy target interface server.
• If Remote Copy is set up in synchronous or asynchronous mode, RMC-S sets the expiration time for both the snapshot on the primary server and the remote snapshot on the Remote Copy target interface server.
For more information, see the HPE 3PAR StoreServ Remote Copy Software User’s Guide.
Setting RMC-S policy
47
The expiration-based policy option is only available if HPE 3PAR StoreServ Storage System is running HPE
3PAR Operating System Software 3.1.1 MU3 or later and a valid Virtual Lock license is available on HPE
3PAR StoreServ.
Retention Time Restrictions
If you have a Virtual Lock license, you can set a retention time for snapshot. The instance or the database and the associated snapshot created within the retention period cannot be removed during the retention period.
When setting a retention time:
• You must have a Virtual Lock license in HPE 3PAR StoreServ is set to retention time.
• The minimum retention time is 0 hour. The default maximum retention time is 43,800 hours (1,825 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 HPE 3PAR volume.
• The retention time cannot be longer than the expiration time (if the policy is expiration-based).
• If you create a remote snapshot and Remote Copy is set up in asynchronous periodic mode, the retention time is applied to the Remote Copy on the Remote Copy target interface server. If Remote Copy is set up in synchronous or asynchronous mode, the retention time is applied to the Remote Copy on the Remote
Copy interface server and the snapshot on the primary server.
• After the retention time is set, it can be increased, but it cannot be removed or reduced.
Setting RMC-S policies
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Policy Configuration.
The Policy Configuration dialog box appears.
48 Retention Time Restrictions
Figure 15: Policy Configuration
Working with RMC-S graphical user interface
49
3. 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 Configuration dialog box:
To set: Follow these steps:
Numeric a. Select Numeric from the list box.
b. In the Maximum Instance level Snapshots and Maximum
Database level Snapshots text boxes, enter the desired maximum for each as a number greater than one.
c. To remove the oldest Snapshot and backup each time a copy above the maximum is created, select the Remove the oldest Snapshots check box.
To keep the oldest Snapshot and backup (and therefore prevent new snapshot from being made after the maximum number is reached), clear the Remove the oldest Snapshots check box.
Expiration a. Select the Expiration from the list box.
b. In the Expiration Time text box, enter the number of hours or days after which you want RMC-S to remove each snapshot. The maximum expiration period is 43,800 hours (1,825 days).
c. In the Default Retention Time, select either Hours or Days.
4. To modify the default retention time for the instance and its snapshots, enter the number of hours or days you want to keep the instance and its contents.
5. Click OK.
6. The Snapshots policy is effective immediately for all future snapshot.
NOTE:
You can also use the RMC-S CLI command HpRmCli Sql policy to set RMC-S policies. For
more information, see Using RMC-S Command Line Interface.
Editing Numeric Policy
When editing a Numeric Policy for Snapshot, Protect, and Catalyst Copy the following table lists an example of the behavior (when the numeric count is reduced).
Feature Initial Numeric
Policy Count
Existing Number Reducing Numeric
Count to
Status
Snapshot
Protect
Catalyst Copy
M
M
M
N
N
N
P
P
P
Supported
Not supported
Supported
(The next operation will remove only one
Catalyst Copy).
Where, P<N<=M.
50 Editing Numeric Policy
For example, if the Initial Policy Count (M) is 10, the Existing number (N) is less or equal to 10, and the reduced Numeric Count (P) is less than N.
Policy configuration for Catalyst Copy
Numeric policy can be applied for Catalyst Copy operation. Policy can be defined at instance and database level. It is mandatory to create a Copy Policy before defining a numeric policy. Policy configuration can be achieved by associating Copy Policy along with Copy Count and Remove Oldest.
You can add, modify, and remove Copy Policy association from Add Copy Policy Instance Level and Add
Copy Policy Database Level for instance and database respectively.
NOTE:
Different Copy Policy can be associated at Instance and Database levels.
Modifying the Policy for a Snapshot
To modify the retention time or the expiration time or both for a snapshot:
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Edit Snapshot. The Policy Configuration dialog box appears.
Figure 16: Edit Snapshot
3. To set a new expiration time, select the Retention Time check box and enter a new value.
For more information on setting the retention and expiration time, see How RMC-S policies work.
4. Click OK.
NOTE:
• You can also use the CLI command HpRmCli Sql policy to modify RMC-S policies. For more
information, see Using RMC-S Command Line Interface.
• Setting the same expiration value and retention value for a snapshot using Time Constraints must be done at the same time.
• The policy of each transaction log is aligned with the Snapshot of parent HPE 3PAR StoreServ.
Policy configuration for Catalyst Copy
51
Creating Snapshot
You can use RMC-S to create snapshot at the instance and the database level. You can also schedule snapshot to make snapshot of instances or databases or both.
Install the SQL Server instance on an HPE 3PAR volume to create the instance snapshot. RMC-S takes the snapshot of all the instance databases from one HPE 3PAR array. If databases are spread across multiple
HPE 3PAR arrays, RMC-S returns an error. Ensure that the database data and log files reside on the HPE
3PAR volume to create a database level snapshot.
NOTE:
You can configure RMC-S to send email notifications when snapshots are created.
For information on Remote Data Collection, see HPE Recovery Manager Central 4.0.0 User Guide.
How snapshot creation works
When RMC-S creates a snapshot for an instance, it creates a snapshot of all databases under that instance, including the system databases for the instance. Similarly, when RMC-S creates a snapshot for a database, it creates a snapshot of the entire volume where the database and log files reside.
If you have Remote Copy set up, you can also create a snapshot to be saved on the Remote Copy interface server; this type of copy is called a remote snapshot.
NOTE:
• For more information about setting up instances, databases, and volumes to avoid data loss, see
Configuring the SQL Database.
• RMC-S creates copy-only backup for availability databases on secondary replica.
Creating a Snapshot
Procedure
1. Change the view to database view and select database for snapshot, similarly change the GUI view to instance view, and then select the instance for instance level snapshot.
2. Click HPE Recovery Manager Central > Microsoft SQL Server.
3. From the Actions menu, select Create Snapshot. The Create Snapshot dialog box appears.
52 Creating Snapshot
Figure 17: Create Snapshot - Database level
Working with RMC-S graphical user interface
53
Figure 18: Create Snapshot - Instance level
4. Specify the following details:
54 Working with RMC-S graphical user interface
Title
General
Name
Type
(Required for Transaction log backup)
Validate
MS SQL Server
MS SQL Server Instance
MS SQL Server Database
Loose Policy
Snapshot Verify
Verify Server and Instance
Description
Use the slider and select one of the following options:
• Full: Performs a full Snapshot.
• Transaction log backup: If selected, you can click the validate option to ensure that system prerequisite for transaction log backup is satisfied.
If used, validates the transaction log prerequisite and confirms the feasibility of performing a snapshot operation with transaction log backup. This option is available when you create a snapshot with transaction log support.
The name of the SQL server.
The name of the SQL server instance.
The name of the MS SQL server database.
If enabled, RMC-S allows to you to perform Snapshot operation even when policy limit is reached and the oldest
Snapshot is in mounted state. For more
information, see Loose policy.
If enabled, the database integrity check operation first performs snapshot operation then mounts and attaches the snapshot to a local or remote SQL
Server for integrity check.
NOTE:
This option is available only for database level Snapshot and is not supported for instance level
Snapshot operation.
The SQL Server and Instance name where Database Snapshot is attached for integrity checks.
Table Continued
Working with RMC-S graphical user interface
55
Title Name
Mount Point
Retain Snapshot
(Required only for Instance level
Snapshots) Exclude Database
(Required only for Instance level
Snapshots) Remove Selections
Time Constraint Retention TimeHours
(Optional) Remote
Copy Options
Remote Snapshot
Description
The Snapshot mount point for verification. For Clustered SQL Server, the verification mount point needs to be a clustered volume with the volume dependencies set in SQL Server resource in the Windows failover cluster manager.
The option to retain the unverified snapshot in case verification failed for
Snapshot.
You can select one or more databases to exclude from creating a Snapshot.
You can remove databases that are already selected in exclude database selection.
Specify the retention time.
Valid values are 0 {h|H|d|D} (for no retention time) to retention time is 43,800 hours (1825 days).
NOTE:
• For Availability Group databases, the policy settings for the selected server or instance are displayed. If the policy settings do not exist for the selected server or instance, the default settings are displayed.
• If user does not want to set the expiration value and retention value for the snapshot to be created, user will set value 0
{h|H|d|D}. If not set, the global expiration policy value and retention policy value will be used for the snapshot when expiration-based policy is configured.
Enable to create a Remote Copy
Snapshot
Table Continued
56 Working with RMC-S graphical user interface
Title Name Description
Schedule
Start Remote copy group
Target interface Server IP/ Host name
Schedule Now
Schedule Name
Schedule Description
Frequency
When enabled, if a Remote Copy group is stopped, RMC automatically restarts the Remote Copy group.
Specify the name of the Target Remote
Copy interface server.
Enable to create a schedule.
Specify a name for the schedule.
Specify a meaningful description.
Select the frequency with which you want automatic snapshots to be created.
Start Time Set the hour and minutes at which you want RMC-S to start creating automatic snapshots.
Day Select the day on which you want RMC-
S to start creating automatic snapshots.
5. To create a snapshot, click OK in the Create Snapshot dialog box.
NOTE:
For Microsoft SQL Server 2012 and later, the Availability Group configuration:
• You cannot create snapshot on all the replica sites at once. You can create snapshot on the replica sites only one at a time.
• You cannot create snapshot of the secondary replica databases which are not set for read mode.
They will not be displayed in the RMC-S GUI. They will also not be a part of instance level snapshot. However, you can create snapshot from the primary site by selecting the secondary replica site from RMC-S GUI or RMC-S CLI.
Loose policy
Loose policy allows you to create database or instance level Snapshots and Protects when the limit for numerical Snapshot and Protect policy is reached and the Remove Oldest Snapshot option is enabled. It is an RMC GUI feature and does not have a CLI flag.
With the loose policy option enabled, you can do the following:
• Create Snapshot or Protect even when the maximum policy limit is reached and the oldest Snapshot is in mounted state.
• Create Snapshot or Protect even when the oldest Snapshot has a retention time and the maximum numerical policy limit is already reached.
• Perform Express Protect when the Snapshot is in backing up state and the maximum numerical policy limit is already reached.
Mounting a Snapshot
You can use RMC-S to mount a Snapshot at the instance or database level.
Loose policy
57
NOTE:
When a Snapshot of a SQL Server instance or database must be mounted to a target server which is not a production server or an interface server, ensure that the RMC appliance associated with the target server is same as that of the interface server. If it is not the same, use the RmcRegistration.exe to
modify the appliance registry entries in the target server. For more details on how to modify RMC
registration tool. Register the RMC appliance IP and credential on the target server. The RMC
appliance is used by target server for various operations.
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Mount and Attach.
58 Working with RMC-S graphical user interface
3. In the Mount Snapshot page, specify the following details:
Working with RMC-S graphical user interface
59
Title
Mount Point
Information
Name
Target Server
Mount Point Only
Description
Specify the server on which the
Snapshot has to be mounted.
Specify the path or mount point where the Snapshot has to be mounted.
NOTE:
• RMC-S does not support mounting a snapshot to a drive letter or to a path involving a cluster shared drive letter.
• Mount point on a shared folder or on reparse points, such as
SYMLINK, NFS mount, and
CSV, are not supported.
Mount Option Attach Database Select to attach a database when mounting a Snapshot at the database level.
NOTE:
• Attach is not supported in the
Instance level.
• Snapshot of databases that are part of the Availability Group are attached to its own instance, but the new database will not be a part of the
Availability Group.
Database Name • By default, when the Attach Database check box option is selected, the default database name appears as
<Database Name>_<Timestamp>.
• If you do not specify a database name, then attach database is not performed.
4. Click Mount Now.
RMC-S:
• Adds the mounted Snapshot to the list view in the Activity pane.
• Displays the server to which the Snapshot is mounted in the Mounted Host column.
• Displays the absolute path on which the Snapshot is mounted in the Mount Point column.
60 Working with RMC-S graphical user interface
NOTE:
If the Snapshot is already mounted, no action is performed if the user tries to mount it again. RMC-S can reuse a mounted Snapshot:
◦ To attach the Snapshot to an SQL server instance.
◦ To perform a Snapshot verification.
Verifying a Snapshot
Procedure
1. Change the view to database view and select database for snapshot, similarly change the GUI view to instance view, and then select the instance for instance level snapshot.
2. Click HPE Recovery Manager Central > Microsoft SQL Server.
3. From the Actions menu, select Create Snapshot.
The Create Database Level Snapshot dialog box appears.
4. Specify the details in Creating a Snapshot.
Ensure that you select the TYPE as FULL and enable Snapshot Verify.
5. From the Verify Server & Instance the menu, select the SQL Server and instance name where the database Snapshot is attached for integrity checks.
6. Specify the Snapshot Mount Point that can be used for verification.
7. To retain the unverified snapshot in case verification failed for Snapshot, click Retain Snapshot.
8. Click OK.
Unmounting a snapshot
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select an instance and from the Action menu, select Unmount Snapshot.
3. Click Yes, Unmount.
4. RMC-S:
• Removes the mounted snapshot from the list view in the Activity pane.
• Displays Not Mounted in the Mounted Host column.
• To detach the database and close all the connections to the database, select Detach Database.
Protecting a snapshot
You can use RMC-S to back up snapshot to media using HPE Data Protector, HPE StoreOnce, Symantec
NetBackup, or Symantec Backup Exec.
To back up a snapshot to media, you must first configure your protect software (HPE Data Protector, HPE
StoreOnce, NetBackup, or Backup Exec) as described in Configuring Protect Software on page 25.
You can create a backup of an instance or a database on the instance or the database level and at the snapshot level.
• When you create a backup on either the instance or the database level, RMC-S creates a snapshot, and your protect software creates a backup.
Verifying a Snapshot
61
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 fails.
• When you create a backup at the time stamp level, RMC-S mounts the existing snapshot, and your protect software creates a backup using the same time stamp.
NOTE:
If the windows user performing the backup operation at the time stamp level on an unmounted snapshot does not have mount privilege due to absence of administrative privileges, the backup creation fails.
You can also schedule RMC-S to create backups of instances or databases or both.
NOTE:
• You can execute concurrent backup jobs through RMC-S GUI and multiple RMC-S CLI instances.
• You can configure RMC-S to send email notifications when backups are created.
• You can execute concurrent backup jobs through RMC-S GUI and multiple RMC-S CLI instances.
Snapshot and Express Protect integrity check
The RMC-S perform Snapshot operation of SQL server databases performs an integrity verification of the
Snapshot using Database Consistency Checker (DBCC). DBCC is a Microsoft SQL server utility that verifies the page-level integrity of databases. This check ensures that you can use the verified Snapshot to restore databases. You can perform this check only at SQL server database level.
The DBCC CHECKDB command is used to verify the integrity of live databases including protection features that protect the Snapshot to HPE StoreOnce, Symantec NetBackup, HPE Data protector, and Symantec
Backup Exec. You can verify the live databases after mounting the Snapshot to a local or remote server by assigning a mount path.
Performing DBCC check
Prerequisites
Ensure that the verification server (local or remote) have drive letters available, a mount point to mount the
Snapshot to the driver letter, or a folder for storing the database that you are verifying.
In the following procedure, step 1 to step 4 are applicable only when you are performing DBCC check on clustered SQL Server nodes.
Procedure
1. Export an HPE 3PAR StoreServ LUN to the clustered SQL Server nodes and assign a drive letter or a volume mount point to it.
2. Add the clustered drive to windows failover Cluster Manager.
3. Select the clustered SQL server name in Roles and add the clustered drive to it.
4. Go to Other resources SQL Server properties and then click Dependencies.
5. Mount the Snapshot to a clustered drive or folder within the driver for integrity check.
6. (If you are using a non clustered SQL server) Select a mount point where Snapshot can be mounted to perform verification.
NOTE: RMC-S doesn't support SMB shares to be a mount point for integrity check.
62 Snapshot and Express Protect integrity check
Creating Express Protect at the database level
When you create a backup of a Snapshot for an instance or a database, RMC-S automatically creates a
Snapshot and mounts it on your protect software and backs up the Snapshot to media server, and RMC-S unmounts the Snapshot. By default, RMC-S deletes the created Snapshot when the backup is complete. You can also choose to have RMC-S retain the newly created Snapshot.
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Protect.
The Express Protect dialog box appears.
3. The following fields are required to back up your Snapshot:
Title Field name Description
Protect Destination
Express Protect
Configuration
Express Protect
Target
MS SQL Server
MS SQL Server Instance
MS SQL Server Database
Snapshot Name
Express Protect Name
Backup Policy
Backup Type
Retain Snapshot after
Protect
Loose Policy
Displays the destination appliance HPE StoreOnce and Media to back up your snapshot. The default protect appliance is HPE StoreOnce.
The name of the SQL Server.
The name of the SQL Server instance, where the snapshot is taken.
The name of the MS SQL Server database.
If no snapshot is available for protect, automatically creates a snapshot
Enter the backup name that must reside on the target server.
This field is optional. If you do not specify a name, then name of the time stamp is same as that of an
Express Protect.
Select the backup policy from the drop-down that must be applied.
By default, the backup type is listed as Auto and
RMC decides on the type of backup, full, or incremental.
The snapshot will be retained even after the snapshot is taken.
If enabled, RMC-S allows to perform Express
Protect operation when policy limit is reached and oldest Express Protect is in mounted state. For
more information, see Loose policy.
Table Continued
Creating Express Protect at the database level
63
Title
Schedule
Field name
Schedule Now
Description
Schedules enable you to schedule data volume
Express Protect and backups. Check the text box and enter the details.
The name of the Express Protect is scheduled.
Schedule Name
Schedule Description
Frequency
The description of the Schedule.
Select the schedule frequency. The options are:
• Weekly —Express Protect is performed at the specified time and day of the week.
• Daily —Express Protect is performed at the specified time.
• Hourly —Express Protect is performed at the specific hour.
• Minutes —Express Protect is performed at specific minute intervals. Minimum frequency is
15 minutes.
• Monthly —Express Protect is performed at the specified time and day of the month.
• Yearly —Express Protect is performed once a year at the specified time, day, and month.
• One Off —A onetime Express Protect is performed.
Set the time for the scheduled snapshot to start.
Start Time
Day Set the day for the scheduled snapshot to start.
4. Change the Protect Destination to Media and enter the following details if you create a backup to Media:
a. From the Select Vendor list, select the protect software you are using:
• Symantec NetBackup
• HPE Data Protector
• Symantec Backup Exec
b. In the Verify Protect Parameters area, enter the required information, depending on your protect software:
64 Working with RMC-S graphical user interface
If you are using: Enter these parameters:
HPE Data Protector • Data List : The name of the data list.
For more information about data lists, see the description of backup specifications in HPE Data Protector documentation.
Symantec NetBackup • Policy Name: The name of the policy you are using.
• Schedule Name: The name of the schedule within the policy you are using.
• Master Server Name: The NBU master server.
For more information, see Symantec NetBackup documentation and
Symantec Backup
Exec
• Media Server: Backup Exec media server name
• Device Name: Backup Exec device name configured for Backup.
HPE StoreOnce The name of the Backup Policy.
c. To retain the newly created Snapshot after protect, ensure that the Retain Snapshot after Protect check box is not selected.
NOTE:
RMC-S, by default, removes the Snapshot it creates during the backup.
d. To create one protect, click OK.
• RMC-S creates the protect, names it as its time stamp 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 snapshots allowed or the policy is configured to remove old copies as necessary (that is, the
Remove the oldest snapshots check box is selected).
• RMC-S does not create the backup if you are using a numeric-based policy and:
◦ The policy is not configured to remove the oldest snapshot (that is, the Remove the oldest
snapshots check box is not selected), and
◦ You have reached the maximum number of snapshots allowed, and therefore RMC-S cannot create a snapshot.
Creating Express Protect at the instance level
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select an instance from the list and then select Database Level Snapshots or Instance Level
Snapshots.
3. Select a Snapshot.
4. From the Actions menu, select Protect.
5. Specify the following details:
Creating Express Protect at the instance level
65
Title Field name
Protect Destination
Description
Displays the destination appliance HPE StoreOnce and
Media to back up your snapshot. The default protect appliance is HPE StoreOnce.
The name of the SQL Server.
MS SQL Server
MS SQL Server Instance The name of the SQL Server instance, where the snapshot is taken.
MS SQL Server
Database
The name of the MS SQL Server database.
Snapshot Verify
Instance
Exclude Databases
The SQL Server, where the Snapshot is taken.
You may select one or more databases to be excluded from Express Protect operation.
Remove Selection
Express Protect
Configuration
Express Protect
Target
Snapshot Name
Express Protect Name
Backup Policy
Backup Type
Retain Snapshot after
Protect
Loose Policy
You can remove databases that are already selected in exclude database selection.
If no Snapshot is available for protect, automatically creates a Snapshot.
Enter the backup name that must reside on the target server. This field is optional. If you do not specify a name, then name of the time stamp is same as that of an
Express Protect.
Select the backup policy from the drop-down that must be applied.
By default, the backup type is listed as Auto and RMC decides on the type of backup, full, or incremental.
The Snapshot will be retained even after performing
Express Protect.
Schedule
Schedule Now
Schedule Name
Schedule Description
If enabled, RMC-S allows to perform Express Protect operation when policy limit is reached and oldest Express
Protect is in mounted state. For more information, see
Schedules enable you to schedule data volume Express
Protect and backups. Check the text box and enter the details.
The name of the Express Protect is scheduled.
The description of the Schedule.
Table Continued
66 Working with RMC-S graphical user interface
Title Field name
Frequency
Description
Select the schedule frequency. The options are:
• Weekly —Express Protect is performed at the specified time and day of the week.
• Daily —Express Protect is performed at the specified time.
• Hourly —Express Protect is performed at the specific hour.
• Minutes —Express Protect is performed at specific minute intervals. Minimum frequency is 15 minutes.
• Monthly —Express Protect is performed at the specified time and day of the month.
• Yearly —Express Protect is performed once a year at the specified time, day, and month.
• One Off —A onetime Express Protect is performed.
Start Time Set the time for the scheduled snapshot to start.
Day Set the day for the scheduled snapshot to start.
6. Change the Protect Destination to Media and enter the following details if you create a backup to Media:
a. From the Select Vendor list, select the protect software you are using:
• Symantec NetBackup
• HPE Data Protector
• Symantec Backup Exec
b. In the Verify Protect Parameters area, enter the required information, depending on your protect software:
If you are using: Enter these parameters:
HPE Data Protector • Data List : The name of the data list.
For more information about data lists, see the description of backup specifications in HPE Data Protector documentation.
Symantec NetBackup • Policy Name: The name of the policy you are using.
• Schedule Name: The name of the schedule within the policy you are using.
• Master Server Name: The NBU master server.
For more information, see Symantec NetBackup documentation and
Symantec Backup
Exec
• Media Server: Backup Exec media server name
• Device Name: Backup Exec device name configured for Backup.
HPE StoreOnce The name of the Backup Policy.
c. To retain the newly created Snapshot after protect, ensure that the Retain Snapshot after Protect check box is not selected.
Working with RMC-S graphical user interface
67
NOTE:
RMC-S, by default, removes the Snapshot it creates during the backup.
d. To create one protect, click OK.
• RMC-S creates the protect, names it as its time stamp 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 snapshots allowed or the policy is configured to remove old copies as necessary (that is, the
Remove the oldest snapshots check box is selected).
• RMC-S does not create the backup if you are using a numeric-based policy and:
◦ The policy is not configured to remove the oldest snapshot (that is, the Remove the oldest
snapshots check box is not selected), and
◦ You have reached the maximum number of snapshots allowed, and therefore RMC-S cannot create a snapshot.
Restoring a Protect
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select an Instance.
3. Select Databases View and then select Database Level Protects.
4. Select a Protect and then click Action > Restore.
5. The Restore dialog box appears.
6. Select either Restore Express Protect to parent volume or Restore Express Protect to another
volume in the Restore dialog:
a. For Restore Express Protect to parent volume,
• Select No Recovery and select either Point in Time or A specific date and time.
• Select Click to continue and click Restore to perform the restore operation.
b. For Restore Express Protect to another volume,
• Select the Name of the storage system.
• To select a data volume from the list of data volumes, click Select Volumes.
• To remove the selected data volume, click Change Selection . Alternatively, you can select x next to the data volume to remove the selected data volume.
• Select Click to continue.
7. To perform the restore operation, click Restore.
Editing a snapshot
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select an Instance.
3. Do one of the following:
• Select Databases View and then select Database Level Snapshots.
• Select Instances View and then select Instance Level Snapshots.
4. Select a Snapshot and then click Action > Edit.
5. The Edit Snapshot Databases Level dialog box appears.
6. Increase the retention time of the Snapshot.
68 Restoring a Protect
NOTE:
The retention time cannot be removed or reduced after it is set and the volume cannot be removed until the retention time expires.
7. Click OK.
Removing a Snapshot
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select an Instance.
3. Do one of the following:
• Select Databases View and then select Database Level Snapshots.
• Select Instances View and then select Instance Level Snapshots.
4. From the Action menu, select Remove.
5. The Remove Snapshot dialog box appears.
6. To delete the snapshot, click Yes, Delete.
You can also remove multiple Snapshots using the Bulk Remove option.
Figure 19: Bulk Remove - Snapshots
Analyzing and Synchronizing the Repository
You can use RMC-S to compare and synchronize snapshot in the RMC-S repository with the HPE 3PAR
StoreServ Storage System.
NOTE:
If changes are there in the HPE 3PAR StoreServ with respect to properties, such as name, size, associated with virtual volumes that are part of the RMC-S instance or database recovery set, perform
Analyze with the synchronize repository on that particular SQL Server from RMC-S.
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Analyze.
The Analyze dialog box appears.
3. To analyze the repository without synchronizing it, clear Synchronize Results with Repository.
4. Click Yes.
The success message appears and the completed task can be tracked through the Activity page.
Removing a Snapshot
69
Restoring
You can use either the volume restore feature or the file copy feature of RMC-S to restore an instance or a database from a snapshot, or you can perform a media restore from a backup.
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.
• You can use CLI commands to promote the snapshot to its parent base volume. For more information, see the HPE 3PAR Command Line Interface Administrator’s Manual.
• Any type of restore operation on the secondary node in Availability Group is not supported.
• Any type of restore operation from target interface server is not supported for periodic, synchronous, or asynchronous snapshot.
TIP:
Volume restore is the fastest method.
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 snapshot contains files for other instances or databases.
The volume restore feature promotes the snapshot 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 snapshot.
NOTE:
An SQL data restore failure can occur when an SQL Server service is stopped outside of RMC-S
Software for Microsoft SQL and the disk path itself is not available for the system in a standalone setup.
The volume restore operation does not alter the database state.
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select an instance from the list.
3. Select either Databases View or Protection View and then select Database Level Snapshots or Instance
Level Snapshots.
4. From the Actions menu, select Restore.
The Restore dialog box appears.
5. Enter the following information:
70 Restoring
Title
Restore Type
General
Database Restore Option
Name
Restore Type
Snapshot or Transaction Log
Name
MS SQL Server
MS SQL Server Instance
MS SQL Server Database
No Recovery
Description
Select volume from the dropdown box.
The name of the snapshot or transaction log to be restored.
Displays the name of the MS SQL
Server.
The name of the instance where the snapshot is restored.
The name of the database where the snapshot is restored.
To use the point-of-failure recovery method to restore the database.
Point-in-time
Point of Failure
The system creates a point-intime snapshot, uses it to create the protect, and then removes it after the snapshot is complete.
To use the auto-restore feature for restoring a database to the point of failure.
A specific date and time Enter a specific date and time to restore the database.
6. To validate whether the HPE StoreServ volume is primary or secondary at that time, click Validate.
7. Select or clear Click to Continue to continue with the restore operation.
8. Click Restore.
9. The snapshot 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 and 2014 Availability Group configuration becomes inaccessible during the restore process, then the user must 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 snapshot. Unlike the volume restore feature, the file copy restore feature does not overwrite the entire volume.
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select an instance from the list.
Restoring an Instance or a Database with File Copy Restore
71
3. Select either Databases View or Protection View and then select Database Level Snapshots or Instance
Level Snapshots.
4. From the Actions menu, select Restore.
The Restore dialog box appears.
5. Enter the following information:
Title
Restore Type
Name
File Copy
Description
Select file copy from the drop-down box.
General
Snapshot or Transaction Log
Name
MS SQL Server
MS SQL Server Instance
MS SQL Server Database
The name of the snapshot or transaction log to be restored.
Displays the name of the MS SQL Server.
The name of the instance where the snapshot is restored.
The name of the database where the snapshot is restored.
Database Restore
Option
Clone Database
Database Name
Alternate Path
No Recovery
Select to clone the database.
Enter the name of the database to which you want the snapshot restored.
If you want to restore the clone database to a location other than its parent location, enter the directory path to the alternate database.
To use the point-of-failure recovery method to restore the database.
Point-in-time
Point of Failure
The system creates a point-in-time snapshot, uses it to create the protect, and then removes this after the snapshot is complete.
To use the auto-restore feature for restoring a database to the point of failure.
A specific date and time Enter a specific date and time to restore the database.
6. Select or clear Click to Continue to continue with the restore operation.
7. Click Restore.
8. Depending on whether you restored the snapshot to its parent location or created a clone database, RMC-
S does one of the following:
72 Working with RMC-S graphical user interface
a. If you restored the snapshot to its parent location, RMC-S completely overwrites the instance or database with the snapshot. The instance or database is now restored.
b. If you restored the snapshot with an alternate database name but you did not specify an alternate database path, RMC-S copies the snapshot to the specified clone database name (at the parent location) and attaches the database.
c. If you restored the snapshot with an alternate database name with an alternate database path, RMC-S copies the snapshot 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 and 2014 Availability Group configuration becomes inaccessible during the restore process, then the user must join the databases back to the Availability Group.
Restoring an Instance or a Database from Media
You can restore backups to their original location (instance or database location of the snapshot used to create the backup, not to the original SQL database or instance location), or you can specify an alternate location.
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select an instance from the list.
3. Select either Databases View or Protection View and then select Database Level Snapshots or Instance
Level Snapshots.
4. From the Actions menu, select Restore.
The Restore dialog box appears.
5. Enter the following information:
Title
Restore Type
Name
Media
Description
Select media from the drop-down box.
General
Snapshot or Transaction Log
Name
MS SQL Server
Media Restore Option
MS SQL Server Instance
MS SQL Server Database
Snapshot Timestamp
The name of the snapshot or transaction log to be restored.
Displays the name of the MS SQL
Server.
The name of the instance where the snapshot is restored.
The name of the database where the snapshot is restored.
The time stamp details of the snapshot you want to restore.
Table Continued
Restoring an Instance or a Database from Media
73
Title Name Description
Vendor Restore Method The methods used by vendors to restore a snapshot.
Alternate Path If you want to restore the clone database to a location other than its parent location, enter the directory path to the alternate database.
6. Select or clear Click to Continue to continue with the restore operation.
7. Click Restore.
The protect software mounts the backup to the specified location as a snapshot. To complete restoring of an instance or a database, move the snapshot to the volume or the database.
Restoring Snapshot from transaction log backup
RMC-S needs transaction log backup to perform up-to-the-second restore operations. This restores your database to a point of time in the interval between two full snapshots. For example, if RMC-S performed one full Snapshot at the time x and another full snapshot at the time y, then RMC-S uses the latest transaction log backup to restore the database to a time in the interval between the times x and y. If the transaction logs are unavailable, then RMC-S can perform only point-in-time restore operations. This restores a database to the time that RMC-S completed a full snapshot.
Transaction log volume protection
When you configure the transaction log path using the RMC-S GUI or HPRmCli Sql repository command,
RMC-S automatically creates a Recovery Set.
If you use the HPE StoreOnce feature for protection, the SQL Server instance or database, the drive location where transaction log path is configured and the stored transaction log files are not included. However, you can use the Create Snapshot Set and Create Express Protect features in RMC GUI to perform manual
Snapshot or to schedule Snapshot and to protect the Recovery Set created by RMC-S.
Restoring SQL instance or database does not include the Recovery Set restore points. You have to restore the transaction log volume Recovery Set using the RMC GUI. For more information, see HPE Recovery
Manager Central 4.0.0 User Guide.
Assume that you have scheduled transaction log backup of SQL server database for every 15 minutes using
RMC-S scheduler and you have also scheduled an Express Protect backup every one hour. In this case, the
Express Protect time stamp also displays the corresponding transaction log snapshot performed in the last one hour, for example, every 15 minutes. When you select a transaction log time stamp to restore from the database level Express Protect list, RMC-S displays the restore type as Restore Express Protect to parent volume only.
NOTE:
RMC-S does not support restoring transaction log backup performed using the MS SQL Management
Studio. Hewlett Packard Enterprise recommends you to perform a SQL DB full snapshot and subsequent transaction log backup using RMC-S.
Rescan
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.
74 Restoring Snapshot from transaction log backup
To rescan an instance:
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Rescan.
3. The Rescan Server Configuration dialog box appears.
Figure 20: Rescan
4. Click Yes, Rescan to rescan the instance.
If Availability Group databases are configured on Microsoft SQL Server 2014, rescan is recommended in the following instances:
• There is a change in Availability Group configuration.
• An SQL Server is migrated to SQL 2014 from its previous versions.
NOTE:
When a new database is added or an existing database is removed from SQL instance, selecting
Rescan removes Availability Group information from the database information list.
Rescan All
To rescan an instance:
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Rescan All.
The Rescan All Server Configurations dialog box appears.
Rescan All
75
Figure 21: Rescan All
3. Click OK to rescan all the instances at the same time.
If Availability Group databases are configured on Microsoft SQL Server 2014, rescan is recommended in the following instances:
• There is a change in Availability Group configuration.
• An SQL Server is migrated to SQL 2014 from its previous versions.
NOTE:
When you perform Rescan All on all SQL instances from the interface server, SQL instances with same names are repeated. Select the appropriate instance of the interface server to perform SQL operations.
Catalyst Copy
Catalyst Copy enables you to copy Express Protect backup or backups from one HPE StoreOnce Backup to another HPE StoreOnce appliance. Catalyst Copy helps you to replicate backup at remote site that can be restored in a disaster scenario.
Creating a Catalyst Copy
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Select Create Catalyst Copy menu and then specify the following details:
76 Catalyst Copy
Figure 22: Catalyst Copy–Existing
Title
General
Name
Name
Description
MS SQL Server
MS SQL Server
Instance
MS SQL Server
Database
Copy Policy
Description
The name of the Catalyst Copy.
The description for the created Catalyst Copy.
Displays the name of the SQL Server.
Displays the name of the SQL instance.
Displays the name of the SQL database.
Displays the names of all the backup policies that was created for Protect.
Table Continued
Working with RMC-S graphical user interface
77
Title Name Description
Express Protect If a backup is created, by default, it is Existing.
If a backup does not exist, you can select Create New option to create Express Protect for RMC-S instance or database.
Express Protect Express Protect Lists all the available backups.
3. To create a Catalyst Copy from the existing Express Protect, click Add.
4. If an Express Protect is not available or must be created, then specify the following details:
78 Working with RMC-S graphical user interface
Figure 23: Catalyst Copy – Create New
Working with RMC-S graphical user interface
79
Title
General
Name
Name
Description
Description
The name of the Catalyst Copy.
The description for the created Catalyst Copy.
MS SQL Server
MS SQL Server
Instance
MS SQL Server
Database
Copy Policy
Displays the name of the SQL Server.
Displays the name of the SQL instance.
Displays the name of the SQL database.
Express Protect
Express Protect
Name
Schedule
Backup Policy
Backup Type
Displays the names of all the policies that was created for
Express Protect.
For creating an Express Protect.
The name of new Express Protect.
Displays the name of the backup policy created.
Auto is selected by default.
Retain Snapshot after
Protect
Retains the snapshot after backup is taken.
Scheduler will create New Snapshot, New Express Protect, and New Catalyst Copy.
NOTE:
• You cannot create a schedule of Catalyst Copy from one source to multiple targets at the same time.
• If the new option is selected to create Snapshot,
Express Protect, Catalyst Copy, then you must provide Scheduler details for the operation.
5. To create a Snapshot, Express Protect, and Catalyst Copy, click Add .
Removing Catalyst Copy
Helps to remove an express protect at the database or instance level.
Procedure
1. Select a database or instance.
2. From the Actions menu, select Remove Protect.
3. RMC-S displays a dialog box asking you to confirm. Click OK.
You can also remove multiple Express Protects using the Bulk Remove option.
80 Removing Catalyst Copy
Figure 24: Bulk Remove - Express Protect
Configuring Email Notifications
You can configure RMC–S to send an email when:
• You create a snapshot or remote snapshot, or RMC-S automatically creates a snapshot or remote snapshot according to the task schedule.
• You create a protect or RMC-S automatically creates a protect 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.
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Email Configuration.
The Email Configuration dialog box appears.
Configuring Email Notifications
81
Figure 25: Email Configuration
3. Enter the following information:
82 Working with RMC-S graphical user interface
Title
Email Configuration
Name
Email Type
SMTP Host Name
Description
By Default, the Email Type is SMTP.
Name of the email server.
Port Port of the email server.
Sender Email Address Email address of the sender.
Password
SSL
Password for the senders email address.
To send email notifications through the Secure
Sockets Layer protocol, select the check box.
Operations
Receiver Email Address Email address of the person to be notified of task activity or errors or both.
Create snapshot
Protect
Restore
• Info
—RMC-S sends informational emails for successful operations.
• Error
—RMC-S sends informational emails for operations that were not completed successfully.
Both informational and error emails contain the result of the operation and the related CLI output.
Remove Email
Configuration
4. Click OK.
Remove To stop email notification, select the check box.
RMC-S encrypts the password and saves the configuration as an XML file with the filename
servername_instancename_EmailConfig.xml . Each time a snapshot or backup is created or an instance is restored, RMC-S 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 anti-virus.
• If SMTP server is not enabled for authentication, then any password is accepted.
Support Ticket
If you have troubleshooting issues, you would be asked to generate a support ticket by HPE support. This ticket provides a log of everything that has happened on the RMC appliance, interface server, and SQL production servers.
The RMC appliance ticket option in GUI is a mandatory selection. However, selecting interface server and
SQL production server can be customized based on user need.
Support Ticket
83
NOTE:
Make sure that the browser security settings permit files to be transferred from the RMC appliance to the host machine.
Generating a support ticket
To create a support ticket:
Procedure
1. Click HPE Recovery Manager Central > Settings.
2. Select RMC-S and click the interface server from the drop-down.
3. To select the registered SQL Servers, click SQL Servers. To change the selection, click Change
Selection option.
4. To generate a support ticket, click Yes, Generate.
The success message Support ticket is being generated appears.
84 Generating a support ticket
Figure 26: Support Ticket
NOTE:
If the generated support ticket is not displayed on the RMC GUI, then it indicates that the ticket is being created.
5. After the ticket is generated, the ID appears on the RMC GUI and tracks the progress of the support ticket generation status through Activity monitor.
6. After completion, the ticket_id appears and the Download Support Ticket is enabled.
Working with RMC-S graphical user interface
85
Figure 27: Support Ticket format
• 20141031 — The first part of the ticket displays the year, month, date (yyyymmdd).
• Z162932 — The second part of the ticket displays the ticket identification number.
Downloading a support ticket
.
Click the
Deleting a support ticket
To delete the support ticket, click the icon.
Support ticket contents
• Extract the ticket to a file.
• ticket_id\logs\var\uploads\RMCS for RMC-S related log files.
• ticket_id\logs\var\log for viewing for RMC appliance-related log files.
86 Downloading a support ticket
Using RMC-S Command Line Interface
Use the RMC-S Command Line Interface (CLI) to manage RMC-S functionality using commands.
Logging in to the CLI
Before you can enter CLI commands, you must first log on to the appliance with a valid username (Admin) and password (admin).
HPE RMC-S CLI
The following table lists the CLI commands that you can use in RMC-S.
To do the following:
Scan the SQL Server for any changes
Use the CLI command:
Create Snapshots
Display Snapshots in the repository
Mount Snapshots
Remove unmounted Snapshots
Unmount Snapshots
Set Recovery Manager policies
Set policy for specified Snapshot
Back up Snapshots to media using Symantec
NetBackup, HPE Data Protector, Symantec Backup
Exec, or HPE StoreOnce
List backup entries in the backup pool
Restore from Snapshots
Delete backup entries in the backup pool
Change the wait time for backup, volume restore, and analysis
Analyze and synchronize the volumes in the HPE
3PAR StoreServ Storage System and the Virtual
Copies in the repository
Query and change repository location
HpRmCli Sql repository
Table Continued
Using RMC-S Command Line Interface
87
To do the following:
Query and change the port location
Gather the environmental statistics and create a log file for diagnosis
Use the CLI command:
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>
• Only NetBIOS names must be used while specifying values for any server type, such as production server, interface server, mount server, target server, media server, or master server.
RMC-S Commands
The section describes the CLI commands in detail.
HpRmCli Sql analyze
NOTE:
If there are changes in the HPE 3PAR StoreServ with respect to properties, such as name, size associated with virtual volumes that are part of the RMC-S instance or database recovery set, perform
Analyze with the synchronize repository on that particular SQL Server from RMC-S.
SYNTAX
HpRmCli Sql analyze -s <SQL Server> [-sync] [-f]
DESCRIPTION
The HpRmCli Sql analyze command validates all Snapshot records by matching Snapshots in the HPE
3PAR StoreServ Storage System against the records in the RMC-S repository. If any existing Snapshots in the system are missing from the repository and conversely, RMC-S 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 Snapshots from the repository. If not specified, out-of-sync Snapshots remain in the repository.
-f
Optional. Forcefully remove out-of-sync records from the repository. Use this option in conjunction with the -sync option. If not specified, the system prompts you to confirm the removal of out-of-sync
Snapshots.
88 RMC-S Commands
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 Snapshots under the specified SQL Server.
HpRmCli Sql analyze -s <SQLserver>
HpRmCli Sql backup
SYNTAX
HpRmCli sql backup
-s <SQL Server> [-i <SQL instance>] [-d <database>][-t <timestamp>
| -r ][-so][-ts <Target Server>][[-p <policyName> -u <scheduleName>
-M <masterServer>]|[-pn <StoreOnce backup Policy Name>]|[-dl <datalistName>]|
[-be -mediaserver <mediaservername> -device <devicename>]][-full][-noemail]
[-backupname <backup name>]|[-sverify][-vs <verificationservername> [-vi
<verification instance][-f][-m <mount point>]]
DESCRIPTION
The HpRmCli Sql backup command backs up a Snapshot to the specified media. The backup can be an existing Snapshot, or it can be a new Snapshot created by this command.
PARAMETERS
The following options are supported:
-s <SQL Server>
SQL Server name to which the database belongs.
-i <SQL instance>
SQL Server instance to which the database belongs.
Optional: Defaults to MSSQLSERVER if not specified.
-d <database>
Optional: The database to which snapshot belongs.
-t <timestamp>
The time stamp of snapshot to back up.
Optional: Without -t <timestamp> specified, a point-in-time snapshot will be created for backup purpose, and then removed after backup completion.
-r <retain>
Optional: Retain the snapshot created if <-t> is not specified.
Optional: This option is applicable only when -t <timestamp> to backup is not specified.
-ts
Target Server name to which the backup will be created.
Optional: Defaults to the local host.
HpRmCli Sql backup
89
-p <policyName>
NBU Policy name.
-u <scheduleName>
NBU backup schedule name.
-M <masterServer>
NBU master server name.
Optional: NBU parameters optional if datalist is specified.
-dl <DataList>
Data Protector datalist name.
Optional: datalist optional if NBU parameters specified.
-noemail
Optional: Suppresses email notification.
-mediaserver <mediaservername>
Backup Exec media Server.
-device <devicename>
Backup Exec device.
-be
Use Backup Exec to back up.
-so
Use StoreOnce to back up.
—full
Optional: StoreOnce full backup. If not mentioned default will be Auto backup.
-backupname
Optional: StoreOnce Backup Name (Snapshot time stamp will be used if backupname is not provided).
-pn <StoreOncepolicy>
The backup policy name in Recovery Manager Central.
-sverify
Optional: For Verification of database level snapshot.
-f
Optional: Forced to take a backup after the verification fails.
-vs <verificationserver>
Optional: For snapshot verification server.
-vi <verificationinstance>
Optional: For snapshot verification instance.
-m <mount point>
Optional: Mount point for snapshot, required for cluster instance.
EXAMPLE
90 Using RMC-S Command Line Interface
The following command performs a backup of snapshot 020405162103 on the server inst1 with SQL instance "instance 1" whose data is mounted to drives i:\ and j:\:
For NetBackup:
HpRmCli sql backup -s inst1 -i "instance 1" -d test_db -t 020405162103 -p test
-u Full -M host1
For HPE DataProtector:
HpRmCli sql backup -s inst1 -i "instance 1" -d test_db -t 020405162103 -dl datalist1
For Backup Exec:
HpRmCli sql backup -be -s inst1 -i "instance 1" -d test_db -mediaserver test device testDevice
HpRmCli sql backup -be -s inst1 -i "instance 1" -d test_db -t 020405162103 mediaserver test -device testDevice
For HPE StoreOnce:
HpRmCli sql backup -so -s inst1 -i "instance 1" -d test_db -backupname
"backupname" -pn "policyname"
HpRmCli sql backup -so -s inst1 -i "instance 1" -d test_db -t 020405162103 -pn
"policyname" -full
For backup with verification
HpRmCli sql backup -so -s inst1 -i "instance 1" -d test_db -backupname
"backupname" -pn "policyname" -sverify -vi "instance2"
HpRmCli sql backup -s inst1 -i "instance 1" -d test_db -t 020405162103 -dl datalist1 -sverify -vs "server1" -vi "instance2"
For Cluster Instance verification
HpRmCli sql backup -s inst1 -i "Clusterinst 1" -d test_db -t 020405162103 -dl datalist1 -sverify -vs "server1" -vi "instance2" -m "H:\folder"
HpRmCli Sql create
SYNTAX
HpRmCli Sql create -s <SQL Server> [-i <SQL instance>] [-d <database>]
[-noemail][-retain <time>{h|H|d|D}] [-f] [-rc <target server>]
[-tss <system id>][-sverify][-transLog][-vs <verification server>]
[-vi <verification instance>][-m <mount point>] [-startrcgroup]
DESCRIPTION
The HpRmCli Sql create command creates a Snapshot of a SQL database or databases under an instance on the primary host where the SQL Server instance is running. (The Snapshot 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 the SQL databases under an instance reside and creates Snapshots at the secondary site as a backup.
If a Remote Copy group is stopped during snapshot creation, a Remote Copy snapshot with -startrcgroup parameter starts the Remote Copy group in HPE 3PAR StoreServ. The -startrcgroup parameter starts the
Remote Copy group and syncs it. After the sync is complete, you can proceed to create snapshots.
HpRmCli Sql create
91
As with HPE Recovery Manager Central for Microsoft SQL Server itself, the command only supports the online backup of an entire SQL database. Therefore, you must make sure that the database is online before creating a Snapshot.
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 Snapshot.
-excludedb <database>
Optional: The list of databases separated by comma to be excluded with instance level snapshot.
-rc <target server>
Optional. For the Remote Copy Service, an HPE Recovery Manager Central for SQL Server at the secondary site with HPE Recovery Manager Central SQL installed must be provided.
-tss <system id>
Optional: For the Remote Copy Service, specify ID of the target Storage System configured at the secondary site in RMC. It is required if target interface server is managing both the HPE 3PAR StoreServ systems in SLD (Synchronous Long distance).
-exp <time>{h|H|d|D}
Optional. Specify the expiration time for the snapshot. Time is a positive integer in the range 0 to 43,800 hours (1,825 days). 0{h|H|d|D} implies that you need not apply retention.
To use this option, the RMC-S policy must be set to an expiration-based policy.
If not specified, RMC-S creates the Snapshot using the expiration time specified in the current policy.
NOTE:
During remote Snapshot creation for periodic mode, the expiration time set at the secondary interface server is used as the time-based policy. The policy set at the primary interface server is ignored. In synchronous mode, the expiration value is applied to both, the local Snapshot, and remote Snapshot. If primary interface server and secondary interface server for different values are set for expiration at synchronous mode, remote Snapshot creation cannot be done.
-retain <time>{h|H|d|D}
Optional. Specify the duration of time (from the current time) for which the snapshot has to be retained.
Time is a positive integer in the range 0 to 43,800 hours (1,825 days). 0{h|H|d|D} implies that you need not apply retention.
92 Using RMC-S Command Line Interface
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 default retention time is 336 hours (14 days).
• The retention time cannot exceed the value of HPE 3PAR StoreServ 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 Snapshot creation for periodic modes, the retention time set at the secondary interface server is used as the time-based policy. The policy set at the primary interface server is ignored. In synchronous mode, the retention value is applied to both, the local Snapshot, and remote Snapshot. If different values are set for retention at primary interface server and secondary interface server for synchronous mode, remote Snapshot creation cannot be done.
• The retention time cannot be removed or reduced after it is set.
• To set no retention time for the Snapshot, use a value of 0h (or 0H) or 0d (or 0D).
-f
Optional. Suppresses confirmation for retention time.
-noemail
Optional. Do not send an email notification even if configured for this operation.
-sverify
Optional: For Verification of database level snapshot.
-r retain
Optional. Retain the snapshot if verification failed.
-vs <verificationserver>
Optional: For snapshot verification server.
-vi <verificationinstance>
Optional: For snapshot verification instance.
-translog
Optional if only transaction logs backup is required. The option is valid for database only.
-m <mount point>
Optional. Mount point for snapshot, required for Cluster instance.
-startrcgroup
Optional. If this parameter is passed, then RMC-S starts Remote Copy group and syncs it. After the sync is complete, you can proceed to create snapshots. The option is valid for Remote Copy snapshot only.
EXAMPLES
• The following commands create a Snapshot for the database test on the SQL Server (SQLServer).
HpRmCli Sql create -s SQLServer -d test
HpRmCli Sql create -s SQLServer -d test verify
• The following command creates a Snapshot for the database db123 test on a virtual SQL Server
(SQLVirtualServer) on a cluster.
HpRmCli Sql create -s SQLVirtualServer -d "db 123"
Using RMC-S Command Line Interface
93
• 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
• The following command creates a snapshot for the database ”db 123” on virtual SQL server
(SQLVirtualServer) and verifies the snapshot on the verification server “srv2” and on instance ”instance2”.
HpRmCli Sql create -s SQLVirtualServer -d "db 123" -sverify -vs srv2 -vi instance2
• The following command creates a snapshot for the database ”db 123” on virtual SQL server
(SQLVirtualServer) and verifies the snapshot on the Cluster instance.
HpRmCli Sql create -s SQLVirtualServer -d "db 123" -sverify -vs srv2 -vi clusterinstance -m "H:\folder"
NOTE:
Use quotes ("") when an option value includes spaces.
NOTE:
RMC VSS waits up to 10 seconds for a snapshot operation and this interval cannot be configured. In most of the cases, 10 seconds is a sufficient interval to create a Snapshot. However, in some circumstances under heavy loads, 10 seconds may not be enough time, and the Snapshot might fail on this attempt. This failure is an RMC VSS framework requirement on Microsofts part.
If such a failure occurs, RMC VSS does not automatically retry the shadow copy creation. Use the
RMC-S GUI or CLI to reattempt to create the Snapshot.
During Snapshot creation, the system creates a backup document in XML format. This document contains current system information and can be used for restore purposes.
NOTE:
• The snapshot volume set is limited to 64 volumes. In other words, each database (under databaselevel operation) or each instance (under instance-level operation) can spread over a maximum of 64 volumes.
• You can only perform database or instance-level operations if you have system admin permissions for SQL Server.
RMC-S creates copy-only backup for availability databases on secondary replica.
You can execute concurrent snapshot creation jobs through multiple RMC-S CLI instances. In this case, RMC-S queues the requests to the RMC 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> [-so][-id <StoreOnce backup id>]
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 HPE Data Protector entry, nor does it remove the actual images backed up by the backup process.
PARAMETERS
94 HpRmCli Sql deletebackup
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 time stamp.
-id <BackupId>
Optional: The backup ID of HPE StoreOnce.
-so <StoreOnce>
Optional: Used for HPE StoreOnce Backup.
EXAMPLE
The following command deletes the backup time stamp 020405162103:
HpRmCli Sql deletebackup -s server1 -d db1 -t 020405162103
HpRmCli sql deletebackup -s server1 -d db1 -t 020405162103 -so -id 15478l5478-95li6-7894561
HpRmCli Sql display
SYNTAX
HpRmCli Sql display -s <SQL Server>[-i <SQL instance>] [-d <database>] [-t
<timestamp>][-rc <target server>] [-transLog [-pit] [-pof]]
DESCRIPTION
The HpRmCli Sql display command displays all Snapshots 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. The database of the snapshot record.
HpRmCli Sql display
95
-t <timestamp>
Optional. Display detailed information about a specific snapshot in the local repository. You cannot view information of a specific snapshot in the secondary site.
-rc <target server>
Optional. Required for the Remote Copy service. A server at the secondary site with HPE Recovery
Manager Central for SQL installed must be provided.
-translog
Optional. Required for transaction log backup display (if any).
-pit
Optional. Required for valid point in time transaction log backup display (if any) with [-t] time stamp option.
-pof
Optional. Required for point of failure transaction log backup display (if any). The [-t] option is not supported with this option.
NOTE:
• The combination of -rc and -t arguments is not supported.
• The combination of -rc and -transLog arguments is not supported.
NOTE:
RMC-S does not support using the command HpRmCli Sql display -t for display of information about a Snapshot that exists at a secondary site.
The following command displays the Snapshots for server1 and of the database instance db1
HpRmCli Sql display -s server1
NOTE:
Use quotes ("") when an option value includes spaces.
NOTE:
If you create an instance level Snapshot and then issue the HpRmCli Sql display command, the
Database column displays all to indicate that Recovery Manager has created Snapshots of all databases except the Temp database.
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 Snapshots being backed up through HPE
StoreOnce or Symantec NetBackup or HPE Data Protector.
PARAMETERS
The following options are supported:
96 HpRmCli Sql listbackup
-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 Snapshots. If not specified, RMC-S displays Snapshots being backed up at the instance and the database level.
-t <timestamp>
Optional. The time stamp of a specific Snapshot to display. If not specified, Recovery Manager displays all
Snapshots being backed up.
NOTE:
When you specify a time stamp, RMC-S displays detailed information about the Snapshot being backed up.
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 the 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:
• You cannot attach a data onto a cluster SQL instance because the data is on a separate disk.
• When a snapshot of a SQL Server instance or database must be mounted to a target server which is not a production server or an interface server, ensure that the RMC appliance associated with the target server is same as that of the interface server. If it is not the same, use the rmcregistratiotool.exe to modify the appliance registry entries in the target server. For more
details on how to modify RMC registration tool. Post the RMC appliance IP and credential in the
target server. The new RMC appliance will be used by target server for various operations.
SYNTAX
HpRmCli Sql mount -s <SQL Server> -t <timestamp> [-m <mount point>] [-ts
<hostname>]
[-i <instance name>][-d <database name>][-a <new database name>][-sverify] [f] [-ti <target instance>]
DESCRIPTION
The HpRmCli Sql mount command mounts a Snapshot created by the HpRmCli Sql create command.
To mount a Snapshot, you must create an available mount point on the NTFS volume before you execute the command.
HpRmCli Sql mount
97
If necessary, use -a option to attach a database to the SQL Server.
PARAMETERS
The following options are supported:
-s <SQL Server>
SQL server for which database belongs.
-i <SQL instance>
Optional. SQL Server instance for which database belongs. If not specified, MSSQLSERVER (local) is used as the default.
-d <database name>
Optional. Database of snapshot.
-t <timestamp>
The time stamp snapshot to be mounted.
-m <mount point>
Optional. The mount point for snapshot. If not specified, <SystemDrive>\3parSnapshot is used as the default mount point.
-ts <hostname>
Optional. The destination server where the Snapshot is mounted.
-a <attach database>
Optional. New name of the database to be attached.
-sverify
Optional. Verify the database level Snapshot.
-ti <targetinstance>
Optional. SQL server instance to which the database is attached.
-f
Optional. Force to run snapshot verification again.
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 unmount a volume that was mounted with the
HpRmCli Sql mount command.
98 Using RMC-S Command Line Interface
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:
RMC-S only supports snapshot exposure to a host.
RMC-S does not support mounting a Snapshot to a drive letter or to a path involving a cluster shared drive letter.
EXAMPLE
The following command performs a mount of snapshot 112233445566 to mount path j:\MNT from server1 to serv 2:
HpRmCli sql mount -s server1 -t 112233445566 -m J:\MNT -ts "serv 2"
The following command performs a mount of snapshot 112233445566 to mount path j:\MNT from server1 to server 1 and attaches a database:
HpRmCli sql mount -s server1 -t 112233445566 -m J:\MNT -ts "server 1" -i
"SQLINST" -d "ExampleDb" -a "ExampleCopy"
HpRmCli Sql policy
SYNTAX
HPRMCLI Sql policy -s <SQL Server> [-i <SQL instance>] [-d <SQL database>][-q]
[-exp <time>{h|H|d|D}] [-in <instance snapshot limit>] [-n <database snapshot limit>]
[-inb <instance backup limit>] [-nb <database backup limit>][-rb] [-bp
<database storeonce backup policy id>][-ipb <instance storeonce backup policy id>] [-inc <instance storeonce catalyst copies>]
[-nc <database storeonce catalyst copies>] [-rc <delete oldest database catalyst copy>]
[-resetRS <reset associated recoveryset>] [-irc <delete oldest instance catalyst copy]
[-cp <database catalyst copy policy id>] [-icp <instance catalyst copy policy id>]
[-r] [-retain <time>{h|H|d|D}] [-f] [-ts <target server>]
DESCRIPTION
The HpRmCli Sql policy command sets the RMC-S policy at the instance and the database level.
HpRmCli Sql policy
99
PARAMETERS
The following options are supported:
-s <SQL Server>
SQL Server to which database belongs.
-i <SQL instance>
SQL instance to which database belongs.
Optional: Defaults to MSSQLSERVER if not specified.
-q
Optional: Queries current policy status.
-in <number>
Optional: Number of instance snapshots to retain.
-n <number>
Optional: Number of database snapshots to retain.
-r
Optional: Retain the oldest snapshot when number of snapshots exceed its limit. Default is set to retain.
-inb <number>
Optional: Number of instance StoreOnce backups to retain
-nb <number>
Optional: Number of database StoreOnce backups to retain.
-rb
Optional: Retain the oldest StoreOnce Backup.
-bp
Optional: Id of the backup policy for StoreOnce Backup of database.
-ipb
Optional: Id of the backup policy for StoreOnce Backup of instance.
-inc
Optional: List of maximum number of instance level StoreOnce Catalyst Copies.
-nc
Optional: List of maximum number of database level StoreOnce Catalyst Copies.
-rc
Optional: List of Boolean values for deleting oldest copy when instance level StoreOnce Catalyst Copy count exceeds limit.
-irc
Optional: List of Boolean values for deleting oldest copy when database level StoreOnce Catalyst Copy count exceeds limit.
-cp
Optional: Id of Catalyst Copy policy for database.
100 Using RMC-S Command Line Interface
-icp
Optional: Id of Catalyst copy policy for instance.
-exp <time>{h|H|d|D}
Optional: Specifies the expiration time for the Snapshot.
<time> is a positive integer value and is in the range 1 - 43,800 hours (1825 days).
-retain <time>{h|H|d|D}
Optional: Specifies the amount of time from the current time that the Snapshot will be retained.
<time> is a positive integer within the range of 0 - 43,800 hours (1825 days).
NOTE:
0{h|H|d|D} implies no application of retention.
-f force
Optional — Suppresses retention time confirmation.
-ts target server
Optional: The destination server whose policy values will be displayed.
-resetRS
Optional: Reset associated recoveryset.
-d SQL database
Optional: SQL database.
NOTE:
No new snapshot will be created with combination of number of snapshots exceeding the limitation and
-r option specified.
EXAMPLE
The following command will change the policy of server1 to 12:
HPRMCLI Sql policy -s server1 -n 12
The following command will set the expiration and retention time on an instance "instance 1":
HPRMCLI Sql policy -s server1 -i "instance 1" -exp 12h -retain 5h
The following command will set number of StoreOnce Backup Limits on an instance "instance 1":
HPRMCLI Sql policy -s server1 -i "instance 1" -inb 12
The following command will set to retain the oldest StoreOnce Backup on an instance "instance 1":
HPRMCLI Sql policy -s server1 -i "instance 1" -rb true
The following command will set list of maximum number of instance level StoreOnce catalyst copies on an instance "instance 1":
HPRMCLI Sql policy -s server1 -i "instance -d 1" -inc "10,15,8"
The following command will set list of maximum number of database level StoreOnce catalyst copies on an instance "instance 1".
HPRMCLI Sql policy -s server1 -i "instance 1" -irc "false,true,true"
If the recovery set against an instance “instance 1” is deleted from RMC, the following command will reset the recovery set:
Using RMC-S Command Line Interface
101
HPRMCLI Sql policy -s server1 -i "instance 1" -resetRS
NOTE:
Use quotes ("") for arguments that include spaces.
HpRmCli Sql portconfig
SYNTAX
Hprmcli Sql portconfig [-s WindowsHost][-r SQL/WebPort][-n number]
DESCRIPTION
After RMC-S is installed, the default port used for communication between the interface server and production server is 9932. If necessary, you can specify an alternate port.
PARAMETERS
The following options are supported:
-s <WindowsHost>
Optional: Specifies an RM Windows Host to list or configure the port settings. Defaults to localhost if unspecified.
-r <SQL/webPort>
Optional: If specified then the command will update the SQL/web port. If not specified, then the command will show the current configuration.
-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 for SQL port is from 1024—65535. The default is: 9932.
Accepted port range for web port is from 50001—52000. The default is: 50001.
EXAMPLES
• The following command will query the port number that is using now:
Hprmcli Sql portconfig
• The following command will change the local SQL port to 9999:
Hprmcli Sql portconfig -r SQLPort -n 9999
• The following command will change the local web port to 51111:
Hprmcli Sql portconfig -r WebPort -n 51111
• The following command will change the server SQLserver port to 9999:
Hprmcli Sql portconfig -s SQLserver -r SQLPort -n 9999
• The following command will change the server SQLserver port to 51111:
Hprmcli Sql portconfig -s SQLserver -r WebPort -n 51111
HpRmCli Sql remove
SYNTAX
HpRmCli Sql remove -s <SQL Server> -t <timestamp>
DESCRIPTION
102 HpRmCli Sql portconfig
The HpRmCli Sql remove command removes a Snapshot from the system and the RMC-S repository. The virtual copy must not be mounted; if the Snapshot is mounted, RMC-S does not remove it.
PARAMETERS
The following options are supported:
-s <SQL Server>
The SQL Server to which the database belongs.
-t <timestamp>
The time stamp of the Snapshot to remove.
NOTE:
After a Snapshot is removed, it cannot be used to restore data from the RMC-S repository. However, you can restore a removed Snapshot from the backup media if the Snapshot 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 RMC-S 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
HpRmCli Sql repository
SYNTAX
HpRmCli Sql repository [-a <repository location>] [-r] [-transLog [-at
<transaction log destination>]] [-f]
DESCRIPTION
After RMC-S is installed, by default the repository directory is located under the RMC-S install directory. To provide the highest level access to the repository, you can change the repository destination to the location of the HPE 3PAR StoreVirtual volume.
PARAMETERS
HpRmCli Sql report
103
The following options are supported:
-a <alter Destination>
Optional: Move the repository to an alternate location.
NOTE:
If you use the CLI to move the repository to an alternate location, you must restart the RMC-S GUI to view the repository in its new location.
-r
Optional. Retains the current data, but changes the repository location to an alternate path.
-transLog
Optional. Display or configure the folder location of transaction log backup.
-at <transaction log destination>
Optional. Move the folder to an alternate location. This is valid with [-transLog] option only.
-f
Optional. Changes the destination of transaction log even if there is an issue with transaction log backups copy or path. It is valid with [-transLog] option only.
NOTE:
The [-r] option is not supported with [-transLog] option.
EXAMPLE
• The following command changes the repository location to "e:\3PAR Storage"
Hprmcli sql repository -a "e:\3PAR Storage"
• The following command changes the transaction repository location to "e:\3PAR Storage"
Hprmcli sql repository -transLog -at "e:\3PAR Storage"
HpRmCli Sql rescan
SYNTAX
HpRmCli Sql rescan -s <SQL server> [-i <instance>] [-authtype <sql/windows>]
[-user <sqlUsername>] [-passwd <password>][-d]
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.
104 HpRmCli Sql rescan
-authtype
The authentication type: Windows authentication or SQL authentication.
-user
Username. Required for SQL authentication.
-passwd
Password. Required for SQL authentication.
-d
Optional. Deletes the previously rescanned instance from repository in the case that there are no associated snapshots or backups. If associated snapshots or backups exist, the SQL instance becomes unmanaged.
-remoteInst
Optional. Used for registering an instance for Remote Copy.
EXAMPLE
• The following rescans the SQL server SQLserverA with default instance
HpRmCli Sql rescan -s SQLserverA.
• The following rescans the SQL server SQLserverA with instance instanceB using Windows authentication type
HpRmCli Sql rescan -s SQLserverA -i instanceB -authtype windows..
• The following rescans the SQL server SQLserverA with instance instanceB using SQL authentication type
HpRmCli Sql rescan -s SQLserverA -i instanceB -authtype SQL -user sa -passwd test
• The following deletes the SQL server SQLserverA with default instance
HpRmCli Sql rescan -s SQLserverA -d
• The following deletes the SQL server SQLserverA with instance instanceB
HpRmCli Sql rescan -s SQLserverA -i instanceB -d
• The following registers instance for Remote Copy
NOTE: It is valid only when used with the option [-authtype].
HpRmCli Sql rescan -s SQLseverA -i instanceB -authtype windows -remoteInst
NOTE:
In SQL 2014, by default, sysadmin role is not selected for NT account. For RMC-S to work in Windows
Authentication mode, user must 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>]
[-norecovery]|[-so] [-volume <volume names>][-pointofFailure][-sn
<storagesystem serialnumber>]
[-id <storeonce backup id>] [-snap] [-f] [-noemail][-pit <exact date and time>]
HpRmCli Sql restore
105
[-transLogOnly]
[-forcedRecovery]
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 three different types of restore:
• Media Restore — Using an existing backup entry, RMC-S Server issues a restore request to the protect software in use (HPE StoreOnce, Symantec NetBackup, HPE 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, RMC-S 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, RMC-S 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.
PARAMETERS
The following options are supported:
-s <SQL Server>
The SQL Server to which the database belongs.
-i <SQL instance>
The SQL Server instance to which the database belongs. If not specified, MSSQLSERVER is used as the default.
-d database(s)
The database of database level snapshot or multiple databases of an instance level snapshot.
If not specified, defaults to instance level restore.
-t <timestamp>
The time stamp of snapshot to restore.
-ts <target server>
Target Server to perform restore (NBU Media Restore only).
If not specified, defaults to local host.
-clonedb db name
Optional: Restores the database to a different database name.
-a altLocation
Optional: Alternate restore location.
-snap
Optional: Performs volume promote restore.
106 Using RMC-S Command Line Interface
-norecovery
Optional: Restores database with the SQL NORECOVERY. This option can be used for file copy and volume restore of a database snapshot. This option can also be used for file copy restore of an instant snapshot. Use - d db1, db2, db3 for multiple databases if there is instance level snapshot file copy restore.
-pointoffailure
Optional: Restores database with SQL NORECOVERY flag and applies the transaction log on the database.
-M <masterServer>
NBU master server name.
Optional: Defaults to restore from snapshot.
-dp
Use Data Protector restore method.
Optional: Defaults to restore from snapshot.
-noemail
Optional: Suppresses email notification.
-f
Optional: Suppresses confirmation for SQL Service stop.
-be
–so
Use Backup Exec restore method.
Use StoreOnce restore method.
-id storeonce backup id
StoreOnce Backup id.
-sn storagesystem serialnumber
Storage system serial number.
-volume volume names
Volume names.
-pit datetime
Optional: To restore to exact point in time. Not valid with [-t] parameter.
Use quotes ("") for [-pit] datetime value.
-transLogOnly
Optional: If full snapshot or transaction logs backup is restored with [-norecovery] option, replay only transaction log backups.
-forcedRecovery
Optional: If full snapshot or transaction log backup is restored with [-norecovery] option and current database is in the Restoring state, moves database to the normal state.
Using RMC-S Command Line Interface
107
NOTE:
• If you are restoring a volume that is part of a Remote Copy target system, you must restore the
Snapshot to the Remote Copy volume group that is part of the same Remote Copy target system as the Snapshot.
• Use listbackup command to find StoreOnce Backup ID.
• After restore from HPE StoreOnce Protect to volume, the Windows OS may ask you to scan and fix the volume for the disk. HPE recommends canceling the Scan and Fix dialog box and continue with your operation.
After successfully restoring Express Protect to any volume and presenting the volume to SQL Server, check the write protect status of the presented disk in SQL Server. You can use the DiskRW.exe tool located in
RMC VSS provider install directory (<default drive>:\Program Files\HPE\RMC\Provider) to clean up the disk write-protect mode.
Run the DiskRW.exe –o command to list the write-protect mode enabled volumes.
Run the DiskRW.exe –m command to set the mode for read-only volumes to read/write. If the command fails to clear the write-protect mode, run the DiskRW.exe –lw command to list the write-protect mode enabled disks.
Run DiskRW.exe –sw command to enable read/write mode for disks.
Run DiskRW.exe command for help on options.
EXAMPLES
• The following command performs a media restore 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 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 media restore using Backup Exec:
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103 -be
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103 -be -a J:
\Test
• The following command performs an Express Protect Restore using StoreOnce:
Restoring to parental volume: HpRmCli Sql restore -s server1 -i inst -d testdb -t
020405162103 -so -id 87t45612-7894r2123 -snap
Restoring to any volume: HpRmCli Sql restore -s server1 -i inst -d testdb -t
020405162103 -so -id 87t45612-7894r2123 -sn 7456121 -volume vol1,vol2
• The following command performs a Filecopy Restore (instance level, database level):
HpRmCli Sql restore -s server1 -i inst -t 020405162103
HpRmCli Sql restore -s server1 -i inst -t 020405162103 -d
"testdb1,testdb2,testdb3"
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103 -norecovery
108 Using RMC-S Command Line Interface
HpRmCli Sql restore -s server1 -i inst -t 020405162103 -d testdb pointoffailure
• The following command performs a Volume Restore:
HpRmCli Sql restore -s server1 -i inst -t 020405162103 -snap
HpRmCli Sql restore -s server1 -i inst -d testdb -t 020405162103 -snap
[ -norecovery] option with instance level file copy restore
The time stamp 020405162103 is of an instance level snapshot. The following command will put db1,db2,db3,db4 in 'Restoring' state after restore is successfully completed.
HpRmCli Sql restore -s server1 -i inst -d db1,db2,db3,db4 -t 020405162103 norecovery
• Restoring using transaction log for the following:
◦ The time stamp 020405162103 is of transaction log for database db1. The subsequent command performs a volume restore of parent full snapshot time stamp (e.g. 020405162100) first and then replay transaction log 020405162103. If there are transaction logs between full snapshot '020405162100' and transaction log '020405162103', then it replays all transaction logs. Use 'display' command with transLog option to view transaction logs database volume restore.
HpRmCli Sql restore -s server1 -i inst -d db1 -t 020405162103 -snap
◦ The following command will put database in 'Restoring' state after restore is completed successfully:
HpRmCli Sql restore -s server1 -i inst -d db1 -t 020405162103 -snap norecovery
◦ Database file copy restore
HpRmCli Sql restore -s server1 -i inst -d db1 -t 020405162103
◦ The following command will put database in 'Restoring' state after restore is completed successfully.
HpRmCli Sql restore -s server1 -i inst -d db1 -t 020405162103 -norecovery
• To specific date and time (using -pit option)
◦ You can use -pit option to restore a database to specific date and time. The supported format for pit option is "MM/dd/yy HH mm ss". For example, -pit "07/01/16 05 41 01" which, is July 01, 2016 05:41:01
AM. The time is in 24-hour format.
◦ The restore command automatically selects the correct full snapshot time stamp and transaction log(s) and restores the database to specific date and time. If it does not find transaction log, then, it restores to the nearest available full snapshot.
NOTE:
If you provide invalid date and time then it will show you valid start and end time for given input parameters.
• Database volume restore: HpRmCli Sql restore -s server1 -i inst -d db1 -pit
"02/04/05/ 16 21 03" -snap
The following command will put database in 'Restoring' state after restore is completed successfully:
HpRmCli Sql restore -s server1 -i inst -d db1 -pit "02/04/05/ 16 21 03" -snap
-norecovery
• Database file copy restore: HpRmCli Sql restore -s server1 -i inst -d db1 -pit
"02/04/05/ 16 21 03"
The following command will put database in 'Restoring' state after restore is completed successfully:
HpRmCli Sql restore -s server1 -i inst -d db1 -pit "02/04/05/ 16 21 03" norecovery
Using RMC-S Command Line Interface
109
NOTE:
• Do not use master database in above -d option with -norecovery option. The master database cannot be put in the 'Restoring' state.
• Use quotes ("") when an option value includes spaces.
• Restart the SQL Server service from SQL Server Configuration Manager after the snapshot volume restore operation for an SQL instance or database completes.
Replaying transaction log only if database is in 'Restoring' state (using -transLogOnly option).
You can use -transLogOnly option to replay transaction log(s) only if database is in 'Restoring' state.
NOTE:
If -t or - pit option value is not associated with last restored parent full snapshot time stamp, it is recommended to use correct time stamp.
• Database volume restore
HpRmCli Sql restore -s server1 -i inst -d db1 -t 020405162103 -snap transLogOnly
HpRmCli Sql restore -s server1 -i inst -d db1 -pit "02/04/05/ 16 21 03" -snap
-transLogOnly
• Database file copy restore
HpRmCli Sql restore -s server1 -i inst -d db1 -t 020405162103 -transLogOnly
HpRmCli Sql restore -s server1 -i inst -d db1 -pit "02/04/05/ 16 21 03" transLogOnly
• -forcedRecovery option (valid for full snapshot and transaction log time stamp both):
◦ Instance file copy restore
The time stamp 020405162103 is of instance snapshot and user used file copy restore with norecovery option first as following:
– HpRmCli Sql restore -s server1 -i inst -d db1,db2,db3 -t 020405162103 norecovery
The above command will put db1,db2,db3 in 'Restoring' state after restore is successfully completed.
– Use following command if you want to bring db1,db2, or db3 in 'normal' state from 'Restoring' state.
You can use db1 or db2 or db3 or more than one database names comma separated with -d option:
HpRmCli Sql restore -s server1 -i inst -d db1,db2,db3 -t 020405162103 forcedRecovery
◦ Database file copy restore
Use following command if you want to bring db1 in 'normal' state from 'Restoring' state:
HpRmCli Sql restore -s server1 -i inst -d db1 -t 020405162199 -snap forcedRecovery
Use quotes ("") when an option value includes spaces.
110 Using RMC-S Command Line Interface
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 time stamp is assumed to be at the instance level.
-t <timestamp>
The time stamp of the virtual copy for which you are changing the expiration time.
-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: 336h (or H)
• To set the expiration time in days: 14d (or D)
-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.
-f
Optional. When used with the -retain option, does not request confirmation for the retention time modification.
HpRmCli Sql setvc
111
NOTE:
Retention and expiration time restrictions are:
• The minimum retention period is 1 hour; maximum retention time is 43,800 hours (1,825 days).
• The default retention time is 336 hours (14 days).
• The retention time cannot exceed the value of the HPE 3PAR StoreServ 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 interface 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 interface server and the virtual copy on the Remote Copy primary server.
• The retention time cannot be removed or reduced after it is set.
• 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:
Use quotes ("") when an option value includes spaces.
HpRmCli Sql timeconfig
SYNTAX
HpRmCli Sql timeconfig [-s <WindowsHost>][-prt <promotetime>][-bkt <backuptime>]
[-ai <analyzeinterval>]
DESCRIPTION
After you install RMC-S, 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 HPE 3PAR StoreServ 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 RMC-S is installed. If not specified, the local host is used as the default.
112 HpRmCli Sql timeconfig
-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 -aicommand to modify the analyze interval, you must restart RMC-S 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, do not change these values unless the backup and/or volume restore are taking an unusually long time to complete.
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:
• If unmounting operation is unsuccessful, unmounting of a virtual copy fails.
• Detach operation proceeds automatically following the unmount operation.
NOTE:
There is not a separate command for attaching and detaching operations. Both commands automatically follow a mounting and unmounting operation.
SYNTAX
HpRmCli Sql unmount -s <SQL Server> -t <timestamp> [-f <forceDetach>]
DESCRIPTION
The HpRmCli Sql unmount command unmounts a mounted virtual copy that is mounted by the HpRmCli
Sql mount command. RMC-S can only unmount a virtual copy if its mounted status is not “Available.”
PARAMETERS
The following options are supported:
HpRmCli Sql unmount
113
-s <SQL Server>
The SQL Server to which the database belongs.
-t <timestamp>
The time stamp of the virtual copy to unmount.
-f <forceDetach>
Optional: Forces detach when there are active connections on database.
NOTE:
During an unmount operation, RMC-S detaches any attaching databases, removes the mount point from the mounted volumes, and then removes the mount point folder.
114 Using RMC-S Command Line Interface
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 snapshot or backup was created; it does not enable you to restore a database at 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 at a specific point in time; either to a snapshot created before the 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:
RMC-S supports only Full Recovery Model.
Recovering Data with RMC-S
RMC-S supports both recovery from snapshot and recovery from media. However, only recovery from snapshot enables you to perform a point-in-time or point-of-failure or a specific date and time recovery.
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 on page 117.
Preparing for the Recovery Process
Before recovery begins, you must ensure that the database can be taken offline.
Procedure
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, perform one of the following:
a. Back up the transaction log for the database.
b. Detach the database.
RMC-S uses the VSS framework to restore data. For the VSS framework takes a database offline before it is restored. Place the database in single-user mode.
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 snapshot 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 snapshot was created.
Recovery for Microsoft SQL Server
115
Recovering All Data with Point-of-Failure Recovery
Point-of-failure recovery is useful if you cannot afford to lose any data during system failure. Recovery consists of the following tasks:
• Determining Whether You Can Perform a Point-of-Failure Recovery
• Performing a Point-of-Failure Recovery
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 recovered up to the point of the failure. If all the following conditions are met, perform a point-of-failure recovery:
• 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 (that 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 forward a database using a transaction log, see: http://
msdn.microsoft.com/en-us/library/ms189596.aspx
Performing a Point-of-Failure Recovery
NOTE:
If you are using RMC-S transaction log feature for creating transaction log backup, then RMC-S performs point-of-failure recovery automatically. Use file copy restore option with point-of-failure.
When you apply the protect transaction log to a database that has been restored using a snapshot, 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.
The following procedure is required if you are using a third-party tool to back up the transaction log. You can also use the RMC-S GUI or CLI to take the transaction log backup of SQL database.
Procedure
1. Locate the most recent consistent full backup and determine the following information:
a. Timestamp (For example, 010106000000)
b. Server name (For example, SQLserver01)
116 Recovering All Data with Point-of-Failure Recovery
c. SQL instance name (For example, SQLInstan01)
d. Database name (For example, northwind)
2. 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,
HpRmCli.exe Sql restore -s SQLserver01 -i SQLInstan01 -d northwind -t
010106000000 -norecovery
3. To apply the transaction logs and 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"
NOTE:
T
Performing restore to a specific date and time
You can restore your Snapshot or Express Protect job to a specific date and time. It is available for instance level and database level Snapshot or Express Protect jobs.
Recovering Data with Auto-Restore
You can use the auto-restore feature to restore a database from a snapshot to a point of failure at database level and to restore multiple databases of a given instance level snapshot.
A database can be restored by using either a File Copy or Volume copy.
NOTE:
If you have named your database log files to a nondefault name, do not use a selective database restore with the nondefault database from an instance level snapshot. 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 snapshot.
Performing restore to a specific date and time
117
Performing a File Copy Restore
Prerequisites
• Ensure that there is at least one snapshot of the database available or create one before performing the restore operation.
• Select the latest snapshot 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.
Procedure
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
2. Locate the snapshot at an Instance or Database.
3. Select Actions > Restore.
4. In the Restore dialog, select File Copy in the Restore Type drop-down.
For Remote Copy snapshot, use the validate option (available only for Remote Copy snapshots) to ensure that snapshot restore operation is possible on primary or target interface server.
5. From a Database level, select any one of the following options:
• Clone Database
• Point in time
• No Recovery: No Recovery specifies that roll back cannot occur. It allows you to apply transaction log and roll forward to continue with the next statement in the sequence.
• Point of Failure: Performs a tail log backup of the active transaction log; restores in no recovery mode of specified point-in-time snapshot; replays the tail log backup on the restored database; and removes the tail log backup file when all the listed operations are successful.
• A specific date and time: Restores the database to specific date and time. You can specify the date and time in seconds. This option is useful if you have transaction log of a database else the option restores to nearest full Snapshot or Express Protect.
NOTE:
• SQL services remain active during a Point of Failure restoration operation.
• The Point of Failure restore is not supported for Instance-level snapshots.
6. Read the warning before checking the Click to continue box and click Restore to proceed with restoration.
7. You can monitor the Restore Snapshot logs in the Activity Page.
Performing a Volume Restore
Procedure
1. Click HPE Recovery Manager Central > Microsoft SQL Server.
All Snapshots are listed here.
118 Performing a File Copy Restore
Figure 28: Volume Restore at a Database Level
2. Locate the specific snapshot Management time stamp at an Instance or Database.
3. Read the warning before checking the Click to continue box and click OK to proceed with restoration.
4. You can monitor the Restore Snapshot logs in the Activity Page.
Performing volume and file copy restore for availability databases
Restoring primary database removes the database from the primary node and the secondary nodes. RMC-S restores database only at the primary node. All secondary databases will be in restoring state. All secondary databases must be restored after the restore operation is completed on primary node by RMC-S.
Performing volume and file copy restore for availability databases
119
To restore availability database on secondary replica node:
1. Take full backup of the availability database and transaction log to a shared disk that is accessible from all replica nodes at primary replica node.
2. Restore the secondary availability database and its log from the backup taken at the primary replica node using RESTORE WITH NO RECOVERY option. If the primary database and secondary database have different file paths, 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.
120 Recovery for Microsoft SQL Server
Coexistence of RMC-S and HPE 3PAR
Recovery Manager for Exchange
Prerequisites
• Only interface server component of RMC-S and HPE 3PAR Recovery Manager for Exchange applications can be installed on the same server.
• Mixing the interface server components and production server components in a coexistence scenario is not supported.
• RMC-S and HPE 3PAR Recovery Manager for Exchange applications must be installed and launched independently.
• RMC-S must be in the same domain as Exchange server.
Coexistence of RMC-S and HPE 3PAR Recovery Manager for Exchange
121
Using HPE 3PAR Peer Motion Manager
Software with RMC-S
HPE 3PAR Peer Motion Manager is a feature of the HPE 3PAR Software and manages the migration of data from a source storage system to a destination storage system. RMC-S now supports HPE 3PAR Peer Motion
Manager data migration activities without any impact on host operations while monitoring the primary storage system.
For more information about performing Peer Motion data migration, see the HPE 3PAR Peer Motion User
Guide. Go to HPE3PAR, navigate to your product page, click Support for your product, and then click
Manuals.
NOTE:
• Peer motion only from HPE 3PAR StoreServ to HPE 3PAR StoreServ is supported.
• RMC-S does not support volumes that are migrated from EVA to HPE 3PAR StoreServ.
• After the Peer Motion from HPE 3PAR StoreServ to HPE 3PAR StoreServ is completed, ensure that the new HPE 3PAR StoreServ is added to RMC as a storage system.
• Do an SQL Server Instance rescan before you perform any new operation.
NOTE:
If the device is presented using Raw Device Mapping (RDM) and if peer motion is performed on that device, the device must ignore the SCSI INQUIRY Cache.
To ignore the SCSI INQUIRY cache, configure the virtual machine using RDM as follows:
• 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.
Do not enable without storage vendor recommendation. This parameter is required for a limited number of storage arrays and only for specific guest operating systems. Reboot the system for the changes to take effect.
Peer Motion Migration does not migrate snapshots. Therefore, the existing snapshots after migration will not be available for use.
122 Using HPE 3PAR Peer Motion Manager Software with RMC-S
Remote Copy for RMC-S
How Remote Copy Works
RMC-S supports the following Remote Copy group modes:
• Synchronous
• Asynchronous
• Periodic
When you synchronize data between a production system (the Remote Copy primary system) on one site and the Remote Copy backup system at another site, the systems involved help you perform the following steps.
Synchronous or Asynchronous Periodic
Recovery Manager leverages the VSS framework to freeze the I/O at the application level and to take point in time snapshots.
For Synchronous or Asynchronous Remote Copy groups, HPE RMC VSS Provider leverages the coordinate snapshot technology provided by the HPE
3PAR StoreServ to create remote virtual copies
(internally uses RMC to connect with HPE 3PAR
StoreServ). The local RMC-S interface server saves the time stamp record of the Snapshots of a source
LUN and remote RMC-S interface server saves the same time stamp record of a remote Snapshot in their respective repositories.
For periodic Remote Copy groups, after the remote snapshots are created for the target LUNs, the remote RMC-S interface server repository is updated with the time stamp of the remote snapshot created.
The local RMC-S interface server does not retain any record of the snapshot time stamp for the source
LUNs of the Remote Copy group in its repository.
NOTE:
You can use the Expiration policy settings of RMC-S. HPE 3PAR StoreServ removes the retained Virtual
Copies after the expiration period elapses.
The following table explains the feature of Synchronous Long Distance (SLD):
Synchronous Long Distance
Recovery Manager leverages the VSS framework to freeze the I/O at the application level and to take point in time snapshots.
For SLD Remote Copy groups, the RMC-S creation and snapshot time stamp retention in local and remote
RMC-S interface servers, depends upon the target HPE 3PAR StoreServ during RMC-S snapshot creation.
If the target HPE 3PAR StoreServ which has Synchronous relationship with the source is selected, the behavior is same as that of synchronous or asynchronous Remote Copy groups. If the target HPE 3PAR
StoreServ which has periodic relationship with the source is selected, the behavior is same as that of periodic RC groups.
NOTE:
For SLD Remote Copy groups, RMC-S does not create Remote Virtual copies for the Synchronous,
Asynchronous, and Periodic target LUNs simultaneously. Remote Virtual Copy creation for the target
LUN depends upon the type of Remote Copy (sync/async/periodic) configured for SQL instance/ database.
Remote Copy for RMC-S
123
NOTE:
• For the RMC-S GUI to manage snapshots on the Remote Copy target interface server, you must configure RMC-S with the precise SQL Server and instance names for the supported SQL Servers.
RMC-VSA 1 RMC-VSA 1 RMC-VSA 2
HTTP/TCP/IP HTTP/TCP/IP
Production
Server
Interface
Server
Target
Interface
Server
A
Base Volume Virtual Copy
D
VSS
HPE 3PAR
StoreServ
B
Virtual Copy
Remote Copy
RC Target Volume
C
HPE 3PAR
StoreServ
Figure 29: Remote Copy configuration
Prerequisites
Before configuring the interface server, ensure that the following conditions are met:
• Recovery Manager for SQL license and Remote Copy license must be available on all registered HPE
3PAR StoreServ.
• The Remote copy group volumes are in either synced, started, or in stopped state. If Remote Copy group is in stopped state and you have enabled the Start Remote copy group option in Create Snapshot GUI or
CLI in RMC-S, then RMC- S starts the Remote Copy group and performs remote Snapshot operation. The
Start Remote copy group does not sync the LUNs, if the LUNs are not synced, you have to sync them manually.
• All RMC Appliances and Interface Servers (Primary and Target) must communicate with each other.
• For SLD Remote Copy configuration, you must configure two target interface servers for SLD Remote
Copy group associated with SQL Server instance/database. One for Synchronous mode and the other interface server for Periodic mode.
• Registering the RMC-S appliance that is managing target interface server is a prerequisite for performing
any Remote Copy operations. For more information on registering a Remote appliance, see Setting up a
124 Prerequisites
Setting Up Remote Copy
Procedure
1. Install and configure Remote Copy. For more information on installation and configuration, see HPE 3PAR
Remote Copy Software User Guide.
2. After you have set up Remote Copy on two HPE 3PAR StoreServ, create a Remote Copy volume group.
3. Configure the Remote Copy volume group for synchronization in synchronous, async, or asynchronous periodic mode with appropriate periodic value as supported by HPE 3PAR StoreServ.
5. In the source RMC-S GUI, register the SQL Remote Copy instances/database without the Remote Copy option selected.
6. In the target RMC-S GUI, register the SQL Remote Copy instances/database with the Remote Copy option selected.
7. For SLD Remote Copy configuration, repeat Step 6 on both target RMC-S GUI.
NOTE: There is no separate configuration required for Remote Copy SLD configuration. If the SQL
Server instance/database is configured for SLD Remote Copy, then you must select the required target interface server to create Synchronous or Periodic snapshot.
Setting up a Remote Appliance
Registering the target interface server is mandatory for setting up Remote Copy configuration.
Registering an appliance
Procedure
1. Select HPE Recovery Manager Central > Settings > Remote Appliances.
2. Click +Remote Appliance or Register from the Actions menu.
NOTE:
Actions menu appears only after a remote appliance is added.
Setting Up Remote Copy
125
Figure 30: Registering an appliance
Enter the following to add an appliance:
Title Name Description
Remote Enter the IP address or the host name of the appliance.
Local
IP Address or
Host Name
Username
Password
Use Local
Appliance to
Manage Remote
Array
Enter the user name.
Enter the password.
Register the local appliance as remote appliance.
Support for Remote Copy Modes and Policies
RMC-S supports Remote Copy in synchronous, asynchronous, and asynchronous periodic mode.
• If you are using synchronous or async mode, the policies on the production system (the Remote Copy primary system) and the Remote Copy interface server must match. If the policies do not match, RMC-S cannot create snapshots on a synchronous Remote Copy system.
MS-SQL instance.
• Connect to the remote RMC-S GUI and register the same MS-SQL instance. Select Remote Copy option while registering the MS-SQL instance.
• On the Remote Copy in RMC-S GUI, make sure that the policy is configured as the source MS-SQL instance (as in step1).
• If you specify an expiration value or a retention value or both when creating a snapshot, RMC-S creates the snapshot on a synchronous Remote Copy system if:
126 Support for Remote Copy Modes and Policies
◦ The policy on the Remote Copy primary server and interface servers is an expiration-based policy.
◦ All policy values including retention values match.
You can specify only the retention value when you create a snapshot on synchronous Remote Copy system. If the policy on both the Remote Copy primary servers and interface servers is numeric, ensure all the policy values, including retention values match.
NOTE:
For more information on specifying values snapshots, see the description of the HpRmCli Sql
create command in Using RMC-S Command Line Interface on page 87.
• If you are using asynchronous periodic Remote Copy, you can create RMC-S snapshots even if policies on the servers do not match. If policies do not match, the snapshots use the policies on the Remote Copy interface server.
• If you are running Remote Copy in a Synchronous Long-Distance configuration, the snapshots on the synchronous Remote Copy interface servers have the same time stamp. The snapshots on the asynchronous periodic Remote Copy interface servers do not have the same time stamp.
Setting Up Remote Copy Volume Groups
Setting Up a Remote Copy Volume Group for Databases
Procedure
1. Identify the virtual volumes that contain the database and log files to be copied.
NOTE:
If all databases in the group belong to the same instance, RMC-S supports multiple databases in one
Remote Copy volume group.
2. Add 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 interface server.
CAUTION:
Do not disperse files from one database over multiple primary Remote Copy volume groups. RMC-S 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.
3. Synchronize the Remote Copy primary and secondary volume groups.
Setting Up a Remote Copy Volume Group for Instances
Prerequisites
Ensure that the names of all virtual volumes in a synchronous Remote Copy group do not exceed 20 characters.
Procedure
1. Identify the virtual volumes that contain all databases and log files to be copied.
2. Create one primary Remote Copy volume group for this instance.
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 interface server.
Setting Up Remote Copy Volume Groups
127
CAUTION:
The relationship between instances and Remote Copy volume groups is 1:1.
• Add files from only one instance to a primary Remote Copy volume group.
• 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 might encounter data corruption and loss.
4. Synchronize the Remote Copy primary and secondary volume groups.
Recovering data from the secondary site
In a primary site disaster, the remote Virtual Copies created at the secondary site before the disaster can be used to restore the data through file copy/volume restore operations. Ensure that the SQL Server instance is online using the secondary site LUNs. The following table lists the required configurations:
Configuration Description
Configuration: 1
SQL Server cluster involving the nodes in primary and secondary site: All instance and database LUNs must be a part of the same Remote Copy group. The primary site nodes must have Remote Copy LUNs presented from the primary site and the secondary site nodes must have Remote Copy LUNs presented from the secondary site.
NOTE:
Only instance level Remote Virtual Copies can be created in this case.
Failover
In a disaster at the primary site, failover cluster brings up the SQL Server service online at Site B
(CLX can be used to switch the secondary site LUNs to read/write mode). In the absence of CLX, perform the failover using SSMC or CLI to switch secondary site LUNs to read/write mode and bring the SQL
Server cluster online on the secondary site nodes.
Failback
If CLX is used, the primary site Remote Copy LUNs are automatically switched to read/write mode. If not, fail back using SSMC or inform CLI to switch primary site Remote Copy LUNs to read/write mode and bring SQL Server cluster online to the primary site nodes.
Configuration: 2
The primary site standalone SQL Server must be configured using the primary site Remote Copy
LUNs and secondary site standalone SQL must be configured using secondary site Remote Copy LUNs.
In a disaster at the primary site, use IMC, or CLI to fail over so that the secondary site LUNs are switched to read/write mode. Bring the standalone
SQL Server online at the secondary site Windows host with identical hierarchical structure as described in Configuration: 1.
NOTE:
Depending on the requirement, either instance or database level Remote Virtual Copies can be created in this case.
Failover
Post fail over, during the Remote Virtual Copy restore process, ensure that the RMC appliance registered in the secondary site production server is the same as the RMC appliance registered in the secondary site interface server.
Failback
After the primary site recovers from the disaster condition, to resume snapshot creation or restore operations at the primary site, ensure that the setup is similar to how it was before the disaster. If there is standalone SQL Server, failback using SSMC or inform CLI such that primary site Remote Copy LUNs are switched to the read/write mode and bring the
Standalone SQL Server online at the primary site windows host.
128 Recovering data from the secondary site
NOTE:
• Depending on the requirement, either instance or database level remote Virtual Copies can be created in this case.
• If Remote Copy replication type is in periodic mode, and in the case that Remote Copy group has failed over without a Remote Copy group sync after Remote Copy snapshot, then you can perform only volume restore on target RMC-S interface server. You cannot perform file copy restore in this case.
Configuring nonsynchronous long-distance Remote Copy with and without peer persistence support
Source Target
RMC-S GUI
RMC-S GUI
IP
IP
Interface
Server 1
Interface
Server 2
RMC VM-I
RMC VM-II
Deploy RMC VM using vCenter Server/
Microsoft Hyper-V
IP
IP
Deploy RMC VM using vCenter Server/
Microsoft Hyper-V
Application
Servers
Network (IP)
Application
Servers
Figure 31: Nonsynchronous long-distance Remote Copy environment
Procedure
1. Install RMC-S on both source and target SQL Servers.
a. Deploy RMC VM-I and RMC VM-II as shown in Figure 31: Nonsynchronous long-distance Remote
b. Add source storage system to RMC VM-I.
c. Add target storage system to RMC VM-II.
2. Add remote appliance from RMC VM-I.
a. Log in to RMC VM-I and click HPE Recovery Manager Central > Remote Appliance > [+ Register
Appliance ].
3. Register the source interface server on RMC VM-I.
4. Register the target interface server on RMC VM-II.
5. In RMC VM-I, select source Interface server and register SQL server instance.
6. In RMC VM-II, select target Interface server and register SQL Server instance as Remote Copy instance.
NOTE:
To view or mount Remote Copy snapshots from target interface server:
From the RMC-S GUI, register the remote copy-related instance or database with the Remote Copy option selected on the target interface server.
Configuring nonsynchronous long-distance Remote Copy with and without peer persistence support
129
Remote copy with and without peer persistence support using single RMC
Source
Deploy RMC VM using vCenter Server/
Microsoft Hyper-V
Target
Interface
Server 1
RMC-S GUI
Interface
Server 2
Application
Servers
Network (IP)
Application
Servers
Figure 32: Remote copy with and without peer persistence support using single RMC
Procedure
1. Install RMC-S on both source and target SQL Servers.
a. Deploy RMC VM-I.
b. Add source storage system to RMC VM.
c. Add target storage system to RMC VM.
2. Add remote appliance from RMC VM.
a. Log in to RMC VM and click HPE Recovery Manager Central > Remote Appliance > [+ Register
Appliance ].
3. In the Register Appliance screen, check Use Local Appliance to Manage Remote Array.
4. Register the source interface server on RMC VM.
5. Register the target interface server on RMC VM.
6. In RMC VM, select source Interface server and register SQL server instance.
7. In RMC VM, select target Interface server and register SQL Server instance as Remote Copy instance.
130 Remote copy with and without peer persistence support using single RMC
Configuring synchronous long-distance Remote Copy
Source Target-1
RMC-S GUI RMC-S GUI
IP
Interface
Server 1
Interface
Server 2
IP
RMC VM-I RMC VM-II
IP
Deploy RMC VM for source using vCenter Server/
Microsoft Hyper-V
IP
Application
Servers
Application
Servers
Deploy RMC VM for target 1 using vCenter Server/
Microsoft Hyper-V
Target-2
RMC-S GUI
Interface
Server 3
IP
RMC VM-III
IP
Deploy RMC VM for target 2 using vCenter Server/
Microsoft Hyper-V
Network (IP)
Application
Servers
Figure 33: Synchronous long-distance Remote Copy environment
Procedure
1. Navigate to the folder containing the RMC-S installer, double-click the HPE_RMCS_4.0.0.exe, and perform the following steps:
a. Install RMC-S Agent on the source application server.
b. Install RMC-S Agent and interface on the source interface server.
c. Install RMC-S Agent on Target–1 application server.
d. Install RMC-S Agent and interface on Target–1 interface server.
e. Install RMC-S Agent on Target–2 application server.
f. Install RMC-S Agent and interface on Target–2 interface server.
2. To deploy RMC VMs:
a. Deploy RMC VM-I, RMC VM-II, and RMC VM-III as shown in thefigure.
b. Add the source storage system to RMC VM-I.
c. Add the Target–1 storage system to RMC VM-II.
d. Add the Target–2 storage system to RMC VM-III.
3. To add the remote appliance:
a. Log on to RMC VM-I and click HPE Recovery Manager Central > Remote Appliance > + Register
Appliance.
b. Add RMC VM-II as a remote appliance.
c. Add RMC VM-III as a remote appliance.
4. Register the source interface server on RMC VM-I.
5. Register the Target–1 interface server on RMC VM-II.
Configuring synchronous long-distance Remote Copy
131
6. Register the Target–2 interface server on RMC VM-III.
7. Repeat step 3 to step 6 for RMC VM-II and VM-III.
NOTE:
• To view or mount the Remote Copy snapshots from Target-I or Target-II interface servers, register the remote copy-related instance or database with the Remote Copy option selected using
RMC-S GUI on target I and II interface servers.
• Remote copy with HPE 3PAR StoreServ peer persistence is supported only for synchronous type of
Remote Copy replication.
Recommendation (Optional)
In the following scenarios, the new Remote Copy snapshot creation or scheduled job snapshot creation might fail and display an error message:
• If you have SLD Remote Copy group associated with an instance or database, set the default storage
system using RMC registration tool on target interface if RMC manages both the target HPE 3PAR
StoreServ storage systems.
• If target interface server RMC manages only one target HPE 3PAR StoreServ storage system, do not set
the default storage system using RMC registration tool.
132 Remote Copy for RMC-S
Using HPE 3PAR CLX with RMC-S
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 shared storage, third-party array-based replication solution like HPE Remote Copy, synchronous and asynchronous replication can be used to have more than one copy of the SQL databases.
RMC-S supports SQL Server clustering and HPE 3PAR CLX configuration in conjunction with Remote copy feature of RMC-S.
An interface server is required for each site corresponding to each array. If two arrays are configured—one on a local site and one on a remote site, then you require two interface servers, one at each site.
RMI Server 1
(Local)
RMI Server 2
(Remote)
RMC 1 RMC 2
Recovery Manager remote
virtual copy command
Site A Site B
SQL
Node 1
RMC 1
SQL
Node 2
RMC 1
SQL
Node 3
RMC 2
SQL
Node 4
RMC 2
Remote Copy
VC
VC
VC
VC
Figure 34: Two Site Configuration
This figure is only an example of a two site configuration.
RMC-S supports only two-site configuration. Within each site, any number of nodes is supported.
An interface server is required for each site corresponding to each array.
RMC VSA is required for each interface server. The interface server on each site must be configured only with
add only Site A array configuration on the Site A interface server. Similarly on site B, configure only the site B array.
Using HPE 3PAR CLX with RMC-S
133
The interface server on each site can only manage the SQL Server instances or databases, which are owned by nodes on the respective sites.
NOTE:
Ensure that only one array is configured on each interface server.
• The Create Remote snapshot operation must use “Remote snapshot” option. For more information on
using Remote Snapshot, see Creating a Snapshot on page 52.
• The remote site interface server information is required to specify as input for remote snapshot operation.
For more information on RMC-S Remote Copy, see Remote Copy for RMC-S on page 123.
• The corresponding snapshot created on the remote site can be used for recovery operations on the remote site.
Using snapshot operation without Remote Copy will only create a snapshot on the local site. Only local site interface server can manage the snapshot. In a site disaster, the production volume cannot be recovered on the remote site as there would not be any snapshot on the remote site corresponding the local Virtual Copies.
Each interface server can only manage the SQL Server and its instance or databases that are owned by the nodes on their respective sites.
NOTE:
RMC-S does not support cross-site management.
operations on the nodes on site A. For example, create snapshot on an instance or a database that are owned by the nodes on site A. Site A interface 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 interface 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 fail over to another site. In such a scenario, the other site must be used for subsequent snapshot operations.
Recovery operation can only be performed on a site using the snapshot created on that site. If there is a failover of the SQL Server after snapshot creation, to use the snapshot for recovery, the SQL Server must fail back or must be moved back to the earlier node where the snapshot was created.
Cluster Virtual Network Name (VNN) must be used for registering SQL Server to RMC-S. Cluster VNN must be used when an owning node is mounted. 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 fails. In such a scenario, the other interface server must be used for the mount operation.
RMC-S supports Synchronous remote copy configurations.
In Synchronous Remote Copy, RMC-S creates a snapshot first on the local site and then on the remote site.
Therefore, snapshot management such as mount, recovery, and backup can be performed on both the sites.
134 Using HPE 3PAR CLX with RMC-S
Troubleshooting
RMC configurations import is not supported on IE 9.0 and higher
Symptom
Importing RMC configuration on Internet Explorer (IE) versions of 9.0 and higher is unsuccessful.
Action
Procedure
1. Launch the IE browser.
2. Go to Internet Options > Security tab.
3. Select Local Internet icon and then click Custom level.
4. Navigate to Include local directory path when uploading files to a server and then select disable.
5. On the Internet Options dialog, click OK.
6. Refresh the browser.
7. On RMC, import RMC configuration.
Exceeding the snapshots per volume
Symptom
Recovery Manager displays error message “VSS_E_PROVIDER_VETO.”
Action
Procedure
• Check the application event log and VSS provider log from the production server.
If you see “Maximum of 28 writable snapshots per volume is allowed,” your snapshot capacity might be full.
• Occurs when you mount a snapshot.
Unmount several snapshots and continue the mount procedure.
Backup restore fails due to mismatch in names.
Symptom
A restore of a backup, which was created using Symantec NetBackup through the RMC for SQL GUI, fails.
Action
Procedure
• Enter the directory name and path precisely, including the upper and lowercase (for example, MuTenFF) when you use the Recovery Manager GUI to back up a snapshot using Symantec NetBackup and a directory is specified for backup.
Troubleshooting
135
If the names do not match, a restore of this backup fails as Symantec NetBackup is case-sensitive.
• When protecting a directory, specify the directory in the same case as it exists on the file system.
SAN Boot disk timeout error
Symptom
When you create a snapshot on a SAN boot disk, the snapshot 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.
Action
Procedure
• Place all important databases on separate SAN disks.
HPE does not recommend placing a database on the SAN boot disk.
Performing auto discovery of the registered MSSQL server does not show up in SQL server discovery list
Symptom
In RMC-S GUI, performing auto discovery of the registered MSSQL server instances does not show the intended SQL server in the SQL server discovery list.
Action
Procedure
1. Check the network configuration of your interface server system.
2. If a network card is in the state Network cable unplugged, disable the card. It is because your system is not using the card.
3. On the Windows PowerShell prompt, run the following command and verify if your SQL server is available:
[System.Data.Sql.SqlDataSourceEnumerator]::Instance.GetDataSources().
4. Check if your SQL Server instance is available in the command output list.
5. If the SQL Server instance is available in the command output list, open SQL Server Configuration
Manager GUI and then start SQL Server Browser Service (if it is in stopped State).
6. Discover the SQL Server using RMC-S GUI.
Snapshot space-creating virtual volumes
Symptom
As data blocks are copied, the space for Snapshots might become full if snapshot 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 Snapshots on a virtual volume becomes full, the Snapshots on the virtual volume might become invalid and subject to the RMC-S policy.
136 SAN Boot disk timeout error
Action
Procedure
• Allocate more snapshot space when creating virtual volumes during base volume creation.
• Use CPGs to manage the data generated by copy-on-write technology.
Symantec NetBackup consumes time to backup
Symptom
Symantec NetBackup takes a substantial amount of time to complete a backup process.
Action
Procedure
• Ensure that you have the latest maintenance package installed for your NetBackup application.
Volume Shadow Copy Service error in a Windows cluster environment
Symptom
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.”.
Action
Procedure
1. Reconfigure the security settings for the cluster environment as follows:
NOTE:
Ensure that Failover Cluster MS DTC is installed. Failover Cluster MS DTC is required to perform the security settings.
a. Click Start > Run > dcomcnfg or Start > Administrative Tools > Component Services..
b. Expand Component Services and click Computers.
c. Right-click My Computer and select Properties.
d. Select the COM Security tab.
e. Under Access Permissions, click Edit Default.
f. Add a Cluster Service account and select Local Access and Remote Access.
g. Reboot the machine.
h. Perform these steps on the second node.
Media restore using the Recovery Manager CLI command fails
Symptom
You attempt to perform a media restore using the Recovery Manager CLI -ts command and the attempt fails.
Symantec NetBackup consumes time to backup
137
Action
Procedure
1. Configure Symantec NetBackup to perform a redirected media restore as follows:
NOTE:
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.
1. Create an altnames directory on the NetBackup master server in the directory containing the backup policy for other clients:
2. Install_path\NetBackup\db\
3. Place an empty file named No.Restrictions in the altnames directory:
4. Install_path\NetBackup\db\altnames\No.Restrictions
5. Do not add a suffix to the files in the altnames directory.
6. 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.
NBU master server and NBU client version mismatch
Symptom
When using Symantec NetBackup, the following message appears: 0x1: ERROR: Cannot connect to [NBU server name]; socket error.
Action
Procedure
• 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.
Post job command is not invoked
Symptom
Symantec NetBackup, Backup Exec, and HPE Data Protector 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 RMC-S is:
1. Backup time stamp will be empty.
2. In one click backup, though the snapshot is marked for deletion, the snapshot does not get removed.
3. Snapshot will not be unmounted.
Action
Procedure
• Run the following postbackup commands:
138 NBU master server and NBU client version mismatch
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 time stamp of the Snapshot to back up.
-d <database>
Optional. The database for the snapshot. If not specified, the instance for the snapshot is used as the default value.
–r <Backup status>
Back up completion status in NBU, DP, or BE. If backup completed successfully, then backup status will be 1 else it will be 0.
Volume is still offline after restore operation
Symptom
After volume promote operation, on few occasions, the volume involved in the restore operation might not come online.
Action
Procedure
• From the Disk Management utility of the server, select the volumes involved in Restore operation and make them online. If the problem persists, present the LUN which was to be restored to the same host again through StoreServ Management Console (SSMC) using a LUN ID different from the original LUN ID.
SQL instance service is stopped after successful restore
Symptom
After database snapshot volume is restored or HPE StoreOnce Protect is restored or Catalyst Copy Express
Protect is restored on few occasions, the SQL instance service involved in the restore operation might be stopped after restore is successful.
Cause
This issue appears when the user and system databases are residing on the same HPE 3PAR volume (not a recommended configuration). The SQL instance service gets terminated during restore operation because underlying volume is unexported during restore process. This issue is also noticed in SQL cluster configuration on few occasions.
Volume is still offline after restore operation
139
Action
Procedure
• Restart the SQL instance and its dependent services after the restore is completed successfully.
Point of failure for snapshot recovery fails
Symptom
If, earlier the snapshot was recovered using Point in time and No recovery option, Point of failure using Auto restore fails.
Action
Procedure
• Do not use any third-party software or SQL management studio for protecting the transaction logs. If you use third-party software or SQL management studio for protecting the transaction logs, RMC-S will not have the transaction log backup sequence and point-of-failure restore operation fails.
One click protect fails if RMC-s server is in the same workgroup as RMC-s interface
Symptom
One click protect fails if RMC-S interface server manages the RMC-S server and RMC-S server is in the workgroup.
Action
Procedure
• Symantec NetBackup must be installed using custom installation option and registration of the Symantec
Netbackup service during the time of installation must be done using work group privilege.
NOTE:
The name is case-sensitive. When checking iSCSI hostname, exclude the iqn number from the name mentioned in the iSCSI initiator configuration tab.
For example
If host side iqn number is iqn.1991-05.com.microsoft:rmsbackupsvr.2k10vfc.com, Hostname created on HPE 3PAR StoreServ side must be rmsbackupsvr.2k10vfc.com.
NetBackup displays partial backup status
Symptom
NetBackup jobs sometimes complete with “Partial Backup status" as seen in NBU activity monitor.
140 Point of failure for snapshot recovery fails
Action
Procedure
• Set the Provider type value to 1 (System) and restart NBU services.
Recovery Set Update operation shows as failed in the activity page
Symptom
Recovery Set update operations culminate in failure and are declared as failed jobs in activity page during
NBU 7.5 backup operations despite a successful backup operation.
Action
Procedure
1. To avoid RMC-S performing the recovery set update operations during NBU 7.5 backup, perform the following steps:
1. Select the NBU policy created, right–click, and select Change.
2. Select Perform snapshot backups in the Snapshot Client section.
3. Click Options in Snapshot Client section.
4. Select VSS in the Snapshot method drop-down and change the provider type to 1.
5. To save changes, click OK.
Snapshot does not unmount automatically when attach operation fails
Symptom
When the attach operation fails during snapshot mount operation, the snapshot must be unmounted automatically.
Action
Procedure
• Attach mounted snapshot using SQL Management studio.
Using multiple credentials to connect the same UNC path
Symptom
If a user tried to use multiple user credentials with the same UNC path for login at the same time.
Action
Procedure
• The following are the suggestions to the problem:
• If you have to use a different user name to connect, then Microsoft recommends connecting to UNC using an IP address or other alias so that it seems like it is on a different path.
Recovery Set Update operation shows as failed in the activity page
141
• Release the control to the UNC path using net use /delete UNC command.
• Restart only the interface server.
RMCS 1100: Unknown internal error encountered, verify log error appears
Symptom
When you register an interface server from the RMC GUI, the following error message appears: RMCS 1100:
Unknown internal error encountered, verify log
Cause
If you use different login credentials for connecting to Universal Naming Convention (UNC) from one or more
RMC appliances, this error occurs.
Action
Procedure
• Workaround 1
Microsoft recommends connecting to UNC using an IP address or alias so that it appears to be from a different path. For more information, see Microsoft KB article 173199.
• Workaround 2
Release the UNC control path using net use /delete <UNC> command.
• Workaround 3 f the preceding workaround does not work, restart the interface server.
Unable to connect to SQL Server instance or SQL connectivity test fails
Symptom
Unable to connect to SQL Server instance or SQL connectivity test fails.
Cause
The reasons for the failure of the tests are:
• Network connectivity can be down.
• SQL service is down.
• Authentication problem.
Action
Procedure
1. Log in to the SQL production server as system administrator and check connectivity:
a. From the SQL production server, launch SQL Server Management Studio to make sure that the connection can be made locally.
b. From Management Studio, right-click SQL Server > Properties > Connections.
2. Make sure the Allow remote connections to this server box is selected.
a. Make sure the SQL Server for that instance has a status of started.
142 RMCS 1100: Unknown internal error encountered, verify log error appears
b. For named instances, make sure the SQL Server browser has a status of started.
c. Double-check the settings under Properties > Security.
d. Double-check the settings under Properties > Permissions.
3. After you have checked the SQL configuration on the production server, log on to the interface server and run the SQL connectivity test again.
NOTE:
Your interface server must pass this SQL connectivity test before you can use RMC-S.
4. Verify that the SQL Server Browser service is running. Start the service if it is not running.
Error is returned during snapshot or database creation
Symptom
Creating a snapshot of a database instance returns the following error:
RMC5315: ERROR: Not Found: The requested URI was not found on RMC server.
Cause
This issue appears when the Recovery Set is deleted using the RMC GUI or RMC VM is deployed using the same IP address of the deployed RMC VM.
Action
Procedure
• Run the following command on the associated interface server: hprmcli sql policy -s <SQL Server> [-i <SQL instance>] [-d <SQL instance>] resetRS
For example
◦ To reset the SQL instance inst1 on SQL Server sql1 run the following command:hprmcli sql policy –s sql1 –i inst1 –resetRS.
◦ To reset the database db1 for instance inst1 on SQL Server sql1 run the following command:hprmcli sql policy –s sql1 –i inst1 –d db1 -resetRS.
Error is returned during snapshot or database creation
143
◦ To reset the default instance on SQL Server sql1hprmcli sql policy –s sql1 -resetRS.
◦ To reset the database db1 of default instance inst1 on SQL Server sql1 run the following command: hprmcli sql policy –s sql1 –d db1 -resetRS
Local communication port is 9932.
Validating server [RMS-9-237] connection...
WARNING: You are about to reset associated recovery-set data.
Are you sure you want to reset?
Select Y/y=Yes N/n=No:
Enter Y or y to proceed. Retry creating snapshot.
Snapshot creation- Check SQL server
Symptom
Performing snapshot operations of SQL instance or database after using IMC/SSMC to change HPE 3PAR
StoreServ operations, such as:
• Modifying HPE 3PAR LUN name or size.
• Unexported HPE 3PAR LUN from host.
• Exported HPE 3PAR LUN back to host.
• Host name change.
• Host WWN/iSCSI IQN number change.
Returns the following error message: Create Failed with Exception : [ Failed to create snapshot, please check the application and system event logs on the SQL Server for the most recent error. (Server : Server name )
Action
Procedure
1. Go to HPE Recovery Manager Central > Microsoft SQL Server.
2. From the Actions menu, select Analyze enable the check box Synchronize Results with Repository and click Yes. Perform the snapshot operation after Analyze task is complete.
Snapshot mount operation fails due to iSCSI IQN number mismatch
Symptom
Snapshot mount operation fails when iSCSI IQN number for target server is not the same as IQN number listed against it in HPE 3PAR StoreServ.
144 Snapshot creation- Check SQL server
Action
Procedure
• HPE recommends that iSCSI IQN number must be same in the target server and in the HPE 3PAR
StoreServ host.
RMCS Scheduler fails to execute
Symptom
RMCS Scheduler fails to execute
Cause
The following are the causes:
• You may have changed the RMC IP address after creating RMC-S schedules and Post IP Change, all
RMC-S schedules are failing.
• After importing the Catalog to new RMC (new IP), all RMC-S schedules are failing.
RMC GUI timeout error
Symptom
The error message Unable to retrieve microsoft SQL Server appears when RMC-S GUI login session is opened for more than an hour.
Cause
This issue appears when the RMC GUI is timed out.
Action
Procedure
• This issue appears when the RMC GUI is timed out.
Fail to reconnect SQL Server instance
Symptom
Reconnecting to SQL Server instance after restoring Express Protect backup to parent volume may return the following error:
The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database. (Microsoft SQL
Server, Error: 9001)
RMCS Scheduler fails to execute
145
Action
Procedure
• Restart SQL Server services using SQL Server configuration manager tool.
RMC-S 4.0.0 Express Protect backup fails
Symptom
RMC-S 4.0.0 Express Protect backup fails with an error Failed to attach volume to the host if the RMC host entry was created by RMC 1.0.0 / 2.0.0 / 3.0.0 or manually and subsequently upgraded to RMC 4.0.0. The following scenarios are identified as potential reasons for this backup failure:
1. The customer created the RMC host entry manually on the HPE 3PAR StoreServ.
2. The customer deployed RMC 1.0.0 / 2.0.0 / 3.0.0 and taken express protect backup at least once.
Cause
RMC 3.0.0 follows strict compliance standard for supporting multipath feature. Multipath command hangs if correct host entry is not found in HPE 3PAR StoreServ with appropriate host role.
Action
Procedure
• Delete the RMC host entry from HPE 3PAR StoreServ and trigger the Express Protect backup from RMC-
S 4.0.0.
Clonedb with or without the NORECOVERY options fails for multiple files
Symptom
Clonedb with or without the NORECOVERY options fails for multiple ndf,ldf,mdf files.
Action
Procedure
• Use the new default folder option; specify an alternate path and retry the operation.
Clonedb with or without the NORECOVERY fails if ClonedB name is part of parent database path
Symptom
Clonedb with or without the NORECOVERY fails occasionally if Clonedb name is xx which is part of parent database file path. For example, if parent database ndf, ldf or mdf file is under d:\xx\path and you try xx as Clonedb with the NORECOVERY option then the Clonedb operation fails.
Action
Procedure
• Specify a different name that does not consist xx and then retry the operation.
146 RMC-S 4.0.0 Express Protect backup fails
Websites
Website
Contact Hewlett Packard Enterprise Worldwide
Subscription Service/Support Alerts
Software Depot
Customer Self Repair
Documentation
Hewlett Packard Enterprise Information Library
RMC Documentation on Hewlett Packard
Enterprise Information Library
Hewlett Packard Enterprise Support Center
Single Point of Connectivity Knowledge (SPOCK)
Storage Compatibility Matrix
Storage White Papers
Link www.hpe.com/assistance www.hpe.com/support/e-updates www.hpe.com/storage/rmc/swdepot/ www.hpe.com/support/selfrepair www.hpe.com/info/enterprise/docs www.hpe.com/storage/rmc/docs www.hpe.com/support/hpesc www.hpe.com/storage/spock/ www.hpe.com/storage/whitepapers
Websites
147
Support and other resources
Accessing Hewlett Packard Enterprise Support
• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
http://www.hpe.com/assistance
• To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:
http://www.hpe.com/support/hpesc
Information to collect
• Technical support registration number (if applicable)
• Product name, model or version, and serial number
• Operating system name and version
• Firmware version
• Error messages
• Product-specific reports and logs
• Add-on products or components
• Third-party products or components
Accessing updates
• Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method.
• To download product updates:
Hewlett Packard Enterprise Support Center www.hpe.com/support/hpesc
Hewlett Packard Enterprise Support Center: Software downloads www.hpe.com/support/downloads
Software Depot www.hpe.com/support/softwaredepot
• To subscribe to eNewsletters and alerts:
www.hpe.com/support/e-updates
• To view and update your entitlements, and to link your contracts and warranties with your profile, go to the
Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page:
www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett Packard
Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements.
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience.
148 Support and other resources
Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
http://www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product's service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
If your product includes additional remote support details, use search to locate that information.
Remote support and Proactive Care information
HPE Get Connected www.hpe.com/services/getconnected
HPE Proactive Care services www.hpe.com/services/proactivecare
HPE Proactive Care service: Supported products list www.hpe.com/services/proactivecaresupportedproducts
HPE Proactive Care advanced service: Supported products list www.hpe.com/services/proactivecareadvancedsupportedproducts
Proactive Care customer information
Proactive Care central www.hpe.com/services/proactivecarecentral
Proactive Care service activation www.hpe.com/services/proactivecarecentralgetstarted
Warranty information
To view the warranty for your product, see the Safety and Compliance Information for Server, Storage, Power,
Networking, and Rack Products document, available at the Hewlett Packard Enterprise Support Center:
www.hpe.com/support/Safety-Compliance-EnterpriseProducts
Additional warranty information
HPE ProLiant and x86 Servers and Options www.hpe.com/support/ProLiantServers-Warranties
HPE Enterprise Servers www.hpe.com/support/EnterpriseServers-Warranties
HPE Storage Products www.hpe.com/support/Storage-Warranties
HPE Networking Products www.hpe.com/support/Networking-Warranties
Remote support
149
Regulatory information
To view the regulatory information for your product, view the Safety and Compliance Information for Server,
Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center:
www.hpe.com/support/Safety-Compliance-EnterpriseProducts
Additional regulatory information
Hewlett Packard Enterprise is committed to providing our customers with information about the chemical substances in our products as needed to comply with legal requirements such as REACH (Regulation EC No
1907/2006 of the European Parliament and the Council). A chemical information report for this product can be found at:
www.hpe.com/info/reach
For Hewlett Packard Enterprise product environmental and safety information and compliance data, including
RoHS and REACH, see:
www.hpe.com/info/ecodata
For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy efficiency, see:
www.hpe.com/info/environment
Documentation feedback
Hewlett Packard Enterprise 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]). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
150 Regulatory information
RMC registration tool
Procedure
1. When RMC-S interface server is added in RMC, the registration tool automatically displays the registered
RMC host name and IP addresses, in case RmcrRegistration.exe tool displays no RMC host name or
IP address , you can perform manual registration of RMC in RmcRegistratio.exe tool. To register the RMC appliance on the interface and production servers, run the executable RmcRegistration.exe.
The RmcRegistration.exe file is provided with HPE RMC VSS provider.
2. The RmcRegistration.exe file is available under the installation path of HPE RMC VSS provider. For example,C:\Program Files\HPE\RMC\Provider.
3. You can set the default target storage system using the RmcRegistration.exe file.
4. If RMC instance is already registered, click RmcRegistration.exe file. The following dialog appears:
Figure 35: RMC registration tool
1. To set the default target storage system, click Yes. To update RMC details and modify or set the RMC IP address, click No.
The following screen appears:
Figure 36: RMC appliance credentials
2. Enter the following details:
RMC registration tool
151
Name
HPE RMC hostname/IP
HPE RMC username
HPE RMC password
Default Storage System
Description
Enter the RMC hostname or IP address.
Enter the RMC credentials.
If Yes in HPE RMC dialog box, select Fetch from the list to retrieve the configured storage system on HPE RMC.
NOTE:
This field is disabled if you select No in the HPE RMC dialog.
NOTE:
• System running with User access control enabled (UAC) is required to launch the
RmcRegistration.exe tool with Run as administrator option.
• The RMC Registration tool displays HPE 3PAR StoreServ system ID in Default Storage
System . The following example maps the correct HPE 3PAR StoreServ System ID using the
HPE 3PAR StoreServ CLI command.
If HPE 3PAR StoreServ serial number is 1647290, then the last five characters of the serial number are the HPE 3PAR StoreServ System ID. If you do not find this mapping in your configuration, then use the following HPE 3PAR StoreServ CLI command to find the correct mapping of HPE 3PAR StoreServ serial number and HPE 3PAR StoreServ System ID.
For example,
$showsys -d
Output of the command
--------------General--------------
System Name : ndu_3par_01
System Model : HPE_3PAR 7400
Serial Number : 1647290
System ID : 47290
Number of Nodes : 4
Master Node : 0
Nodes Online : 0,1,2,3
Nodes in Cluster : 0,1,2,3
Chunklet Size (MB) : 1024
Description
StoreServ Name is ndu_3par_01
StoreServ System Model: HPE_3PAR_7400
StorServ Serial number : 1647290
StoreServ System ID: 47290
• When you set a new RMC password, update the new password in RMC registration tool.
152 RMC registration tool
Server Virtualization Environments
VMware and Microsoft Hyper-V Environments
VM with iSCSI and direct path I/O
If you are using VMDirectPath I/O or iSCSI for database and log protect, RMC-S provides full features for snapshot, backup, and restore operations. Both VMDirectPath I/O and iSCSI options are supported for RMC-
S virtualized interface server and SQL Servers.
VMware RDM disk
RMC-S does not claim full support for SQL server running on RDM disks. Snapshots and Express Protects are fully supported. However, mount and restore operations require you to perform manual steps.
VMware RDM enables the VM to participate in VSS snapshots using requestors such as RMC-S, SQL writer, and RMC VSS provider. The Snapshots are consistent and can be exported or mounted on a non-VM RMC-S interface server. If a Snapshot or a Backup must be restored to the SQL VM server, then manually copy the data from the RMC-S non-VM interface server to SQL production server to provide a restore image.
NOTE:
If RDM disks are used to host the SQL server database and logs, RMC-S requires the RDM disks to be set in physical compatibility mode.
Microsoft Hyper-V
Microsoft Windows 2012 / 2012 R2 / 2016 with virtual FC and iSCSI are supported on SQL server and
Interface server. Before you perform any mount operations, ensure that the VM that is enabled with virtual FC
HBA and is appropriately zoned with HPE 3PAR StoreServ on the interface server and SQL production server.
The following table lists the various virtualization options and supported functionality in virtualization environments:
Virtualization Option SQL
Server
Interface
Server
Functionality
ISCSI Initiator VM VM
VMDirect path I/O
Raw Device Mapping
(RDM)
VM
VM
Hyper-V virtual FC (vFC) VM
VM
Physical
Interface
Server
VM
You can mount the application consistent snapshot on both interface and SQL production servers. Both
VMware and Hyper-V VMs provide full functionality.
You can mount the application consistent snapshot on both interface and SQL production servers. VM requires a dedicated HBA.
You can mount the application consistent snapshots on the physical backup server. Restore the data to the VM manually. Mounting and restoring from RMC-
S fails.
RMC-S provides complete features support for snapshot, backup, and restore operations.
Server Virtualization Environments
153
Importing/restoring interface server catalog dumps
Perform the following steps after downloading the interface server catalog.zip file from the RMC Import dialog.
Procedure
1. After the Catalog file is download from the interface server, navigate to the interface server installation directory. For example, <installation directory>:\Program Files\HPE\RMC-S\SQL.
2. Copy the .zip file named in the format: RMS-<IP ADDRESS>-MigData.zip. For example,
RMS-15.213.67.225-MigData.zip to the following directory: <installation directory>:
\Program Files\HPE\RMC-S\SQL.
3. Extract the .zip file to a temporary folder on the server.
The following folders and files are extracted:
• Data (folder)
• [Content_Types] (xml file)
4. Copy the contents of the Data folder to the following target directory <installation directory>:
\Program Files\HPE\RMC-S\SQL\Data. If the customer has migrated, then the target directory is
<installation directory>:\Program Files\3par\RM\SQL\Data.
NOTE:
If data exists in the Data folder, make sure to clean up the folder and then copy the data files into this directory.
5. Refer to the Catalog Scenario to make sure that the configurations are appropriate after restore.
6. Restart the interface server.
7. Log in to the RMC appliance to verify the restored data.
Restoring Catalog scenarios
Restore Catalog is classified into the following scenarios.
NOTE:
Auto discovery does not list the reregistered instances.
• Scenarios — 1: Fresh installation of RMC and interface server
• Scenarios — 2: Existing RMC and fresh installation of interface server
• Scenarios — 3: Fresh installation of RMC and existing interface server
• Scenarios — 4: Existing RMC and existing installation of interface server
Fresh installation of RMC and interface server
RMC catalog is restored to a different interface server configured with a fresh installation of RMC.
154 Importing/restoring interface server catalog dumps
Procedure
2. Reregister the production server instances from the RMC GUI with Force RegisterRegistering an
interface server on page 38 even if the instance is in managed state.
Existing RMC and a new interface server setup
RMC catalog is restored to a different interface server configured with the same RMC.
Procedure
1. If the catalog is already restored, you must register RMC on all production servers with the RMC
2. Reregister the production server instances from the RMC GUI with Force RegisterRegistering an
interface server on page 38 even if the instance is in managed state.
Fresh installation of RMC with an existing interface server
RMC catalog is restored to an existing interface server and the protected RMC catalog is restored on a different RMC appliance.
Procedure
1. RMC catalog is restored to a same interface server configured with a different RMC where catalog was protected RMC, Or
in managed state.
Existing RMC and existing installation of interface server
RMC catalog is restored on an existing RMC and the interface server catalog is restored on an existing interface server.
Procedure
1. Verify if all the registered hosts have the same RMC registered, if not you must register RMC using the
2. Reregister the production server instances from the RMC GUI with Force RegisterRegistering an
interface server on page 38 even if the instance is in managed state.
Existing RMC and existing interface server with changed IP
RMC catalog is restored on an existing RMC and the interface server catalog is restored on an existing interface server. In this scenario, the IP addresses of RMC and the interface server are changed.
Procedure
1. Verify if RMC is registered on the interface server and the registered production server. If RMC is not registered, you must register RMC using the RMC registration tool, Or
2. a. Unregister the interface server from RMC GUI with Force Un-Register. Select the force unregistration option if normal unregistration fails before catalog restore.
b. Register the interface server with or without force option.
c. Restore a catalog.
d. Reregister the production server instances from RMC GUI with Force Register even if the instance is in managed state.
Existing RMC and a new interface server setup
155
RMC-S error codes
Each operation failure in RMC-S has a code that is assigned to it. The corresponding error codes will have the reason for the failure.
Table 7: Error codes
SQL Servers registration failure
SQL Servers unregistration failure
SQL Servers RMC credential Update failure
Analyze failure
Create snapshot failure
Create transaction log backup failure
Rescan SQL Server failure
Remove snapshot failure
Mount snapshot failure
Unmount snapshot failure
Edit snapshot policy failure
Policy configuration failure
Snapshot Backup failure
Delete backup failure
Rescan multiple servers failures
Support ticket collection failure
Restore failure
Remote repository update failure
Test mail failure
RMC-S repository configuration failure
Report failure
1301
1318
1319
1323
1325
1311
1312
1313
1314
1321
1322
1326
1322
1306
1307
1308
1310
1302
1303
1304
1305
156 RMC-S error codes
Event Messages
This appendix provides information on the event messages generated by RMC-S.
Table 8: RMC-S Server Event Messages
Event ID Event Message
5312
5313
5319
5321
5325
5326
5327
RMS5312: ERROR: Some of the volumes are either non3PAR volumes or unsupported types of disk drives.
Description/Action
Some target volumes are not HPE 3PAR virtual volumes.
All drives must be HPE 3PAR drives.
• Verify that all database and log destinations belong to an HPE 3PAR StoreServ Storage System.
RMS5313: ERROR: Could not find the Remote Copy group for the specified volume.
RMS5319: ERROR: The snapshot was not found in the repository.
RMS5321: ERROR: The specified mount directory does not exist.
RMS5325: ERROR: The snapshot time stamp does not exist for the snapshotset ID.
The Remote Copy volume group is not configured for the specified SQL database or instance.
• Check the Remote Copy configuration and HPE 3PAR
StoreServ Storage System setup.
• Consult the HPE 3PAR InForm OS CLI
Administrator's Manual or the HPE 3PAR
Management Console Help for details on setting up and checking Remote Copy functionality.
The repository might be out of sync. To list the out-ofsync entries, run HpRmCli Sql analyze.
To use an alternate (nondefault) mount point directory in the HpRmCli Sql mount command, you must first create the mount point directory.
• Verify that the mount point directory exists.
• Alternatively, do not specify a mount directory. If an alternate directory is not specified, RMC-S uses the default mount directory.
When you created the snapshot, RMC-S could not store the snapshot time stamp in the repository for the specified snapshotset ID.
• Wait a few minutes and then retry the operation.
RMS5326: ERROR: Volume Restore failed.
A failure occurred when restoring data using the volume restore feature. The failure might leave the HPE 3PAR
StoreServ Storage System in an inconsistent state. If the
VLUNs are missing, ensure that they are recreated.
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.
Table Continued
Event Messages
157
Event ID Event Message
5328
5329
5332
5333
5335
5336
5337
5347
RMS5328: ERROR: One or more of your databases are on the system volume. You cannot create Virtual
Copies of system volumes.
Description/Action
Some of the database or log files are stored on the system volume.
• Ensure that the database and log files are on HPE
3PAR virtual volumes.
RMS5329: ERROR: The destination file already exists. 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. Verify that the specified restore folder is empty and try the operation again.
RMS5332: ERROR: Could not find the SQL Writer. Either the Writer is not installed or is not running.
RMS5333: ERROR: Remote Copy groups are not configured. A Remote
Copy group must be present to perform this operation.
There are no Remote Copy volume groups configured on the HPE 3PAR StoreServ Storage System. Ensure that the Remote Copy volume group is configured before you create a remote snapshot.
• Check the Remote Copy configuration and HPE 3PAR
StoreServ Storage System setup.
• Consult the HPE 3PAR InForm OS CLI
Administrator's Manual or the HPE 3PAR
Management Console Help for details on setting up and checking Remote Copy functionality.
RMS5335: ERROR: Mount point drive letter is already in use.
SqlServerWriter was not found on the SQL Server.
• Run the vssadmin list writers command and verify that SqlServerWriter is listed.
• Ensure that the SQL Writer service is in the
Running state.
RMS5336: ERROR: Mount point directory is not a valid directory.
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.
The specified mount point is not a directory. Be sure to specify a valid directory as a mount point when you enter the HpRmCli Sql mount command.
RMS5337: ERROR: Mount point directory is not empty.
RMS5347: ERROR: Failed to locate
NetBackup installation. Ensure that the NetBackup is correctly installed.
The mount point directory specified already contains files. Be sure to specify a valid directory as a mount point when you enter the HpRmCli Sql mount command.
Symantec NetBackup installation information could not be retrieved from the registry.
• 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.
Table Continued
158 Event Messages
Event ID Event Message
5348
5349
5351
5354
5356
5364
5367
5370
5371
RMS5348: ERROR: Could not find
NetBackup start and end scripts.
Description/Action
The NetBackup start or end scripts could not be found in the RMC-S installation folder. Ensure that the bpstart_notify.bat and bpend_notify.bat files are present in the RMC-S installation folder.
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.
RMS5351: ERROR: NetBackup restore process has failed.
RMS5354: ERROR: The SQL database was not found in the SQL
Writer database list.
RMS5356: ERROR: The expiration time is out of range (0h - 336h).
The NetBackup restore failed.
• On the NetBackup server, check the application event log and NetBackup logs.
SqlServerWriter could not find the specified database in its list of databases supported for backup.
• Verify that the database is online and attached.
• Ensure that the database is not a snapshot/mirrored database.
The expiration time for a snapshot 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.
RMS5364: ERROR: Failed to back up the snapshot. Consult the backup progress logs for details.
The NetBackup backup process has failed.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
RMS5367: ERROR: Unknown error encountered. See the logs for more information.
RMS5370: ERROR: The specified policy does not exist in the
NetBackup configuration database.
An unexpected error occurred.
• For more details, check the logs in the RMC-S installation folder and the event logs.
The policy was not found in the NetBackup database.
• 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 does not exist in the configuration database.
The schedule was not found in the NetBackup database.
• Verify that the policy is valid.
• For more details, check the application event log and
NetBackup logs on the NetBackup server.
Table Continued
Event Messages
159
Event ID Event Message
5372
5373
5374
5375
5376
5377
5379
5380
RMS5372: ERROR: Failed to connect to the NetBackup master server.
Description/Action
RMC-S 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.
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.
RMS5374: ERROR: The specified policy is not a valid client type.
RMS5375: ERROR: This operation is not allowed at this time.
The NetBackup server is not 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.
RMS5376: ERROR: The specified client does not exist in the specified policy.
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.
RMS5377: ERROR: The specified policy is not active.
RMC-S 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.
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.
RMS5379: ERROR: Failed to mount snapshot. Check the application and system event logs for the most recent error.
RMC-S failed to mount the snapshot.
• Check the application and system event logs for the most recent error messages.
RMS5380: ERROR: Failed to create snapshot. Check the application and system event logs on the SQL Server for the most recent error.
RMC-S failed to create the snapshot.
• Check the application and system event logs on the
SQL Server for the most recent error messages.
Table Continued
160 Event Messages
Event ID Event Message
5381
5382
5383
5384
5385
5386
5387
5388
RMS5381: ERROR: Failed to locate
Data Protector installation. Ensure that the Data Protector is correctly installed.
RMS5382: ERROR: Could not find
Data Protector post script.
Description/Action
The HPE 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.
The Data Protector post script could not be found in the
RMC-S installation folder.
• Ensure that the dpend_notify.bat file is present in the RMC-S installation folder.
RMS5383: ERROR: Datalist not found or SYSTEM account does not permit backup from this client. Select
<Any> while configuring the client system.
The specified datalist could not be found or access was denied.
• Ensure that the correct name is specified for the datalist.
• Ensure that the SYSTEM account has permission to run backup processes from the specified client.
• Use the Data Protector Manager GUI to configure client permissions.
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.
RMS5385: ERROR: The Data
Protector Session ID was not found in the repository for the given time stamp. Ensure that the correct
Vendor Type is specified.
The Data Protector Session ID to restore was not found for the time stamp specified. Ensure that the backup time stamp does not belong to another backup vendor (for instance, Symantec NetBackup).
RMS5386: ERROR The NetBackup policy was not found in the repository for the given time stamp. Ensure that the correct Vendor Type is specified.
The NetBackup policy to restore was not found for the time stamp specified. Ensure that the backup time stamp does not belong to another backup vendor (for instance,
HPE Data Protector).
RMS5387: ERROR: Failed to set the disk in maintenance mode because the disk is offline.
Could not set the disk in maintenance mode because the disk is offline. Ensure that the disk to be restored is online before you run the volume restore operation.
RMS5388: ERROR: Failed to set the disk in maintenance mode.
Could not set the disk in maintenance mode.
• Ensure that the disk is online and can be put in maintenance mode.
• Troubleshoot using the cluster command: cluster res <resource-name> /maint:on
Event Messages
161
Glossary
Terms and technologies
Table 9: Terms and technologies
Term/Technology
RMC
RMC-S
HPE RMC VSS
VSS
CLI
SPOCK
Description
Recovery Manager Central
Recovery Manager Central for MS SQL Server
HPE Recovery Manager Central VSS Provider
Volume Shadow Copy Service
Command Line Interface
Single Point of Connectivity Knowledge
Recovery Manager Agent for SQL Server
Installs the agent component of RMC-S on the production server
Recovery Manager for
Interface Server
To install the server component of RMC-S on the interface server
SSL
OVF
GPT
Availability Group
AlwaysOn
Database
Secure Socket Layer
Open Virtualization Format
GUI Partition Table
A part of the Microsoft SQL Server 2012 and 2014 AlwaysOn feature. It combines both database mirroring and log shipping capabilities to enable:
• Multidatabase failover
• Multiple secondaries
• Application failover using virtual names
• Readable secondary
• Back up from secondary
The databases as a group can move from one node to another node
(failover) within the AlwaysOn set of nodes.
A disaster recovery solution added in Microsoft SQL Server 2012 and 2014.
The solution provides both database level and instance level availability.
A database is a collection of logical objects within a physical structure. The physical structure consists of one or more data files, and one or more transaction log files. A database is either used by the SQL Server itself
(system database) or by an application (user database).
Table Continued
162 Glossary
Term/Technology
Cluster group
Host system
Log shipping
MSCS Microsoft Cluster
Services (MSCS)
Description
A logical group of cluster resources that can be moved from one node to the other while the nodes remain operational. Administrator or a cluster resource failure can move the cluster group.
A computer that accesses storage on a storage system.
A process that takes backed-up transaction logs from a primary SQL Server and applies them sequentially on a scheduled basis to another SQL Server database. If a failure occurs, an application can be redirected to the other server, which will be only slightly behind the primary database. If a logical or physical system failure occurs, Log shipping is a means of protecting organizations.
System services that make it possible to create a virtual system consisting of multiple cluster nodes; each node is an independent physical computer and is a failover resource of other nodes in the cluster. Each node can support one or more virtual SQL Server instances.
SQL Server
SQL Server computer
SQL Server replication
System database
System databases
A Microsoft relational database system based on the client/server database model.
The hardware on which a Microsoft SQL Server database system is running.
SQL Server initiates and controls the replication process.
A type of database that is used internally by SQL Server.
Distribution database
System databases are created either during installation or during feature configuration, such as the distribution database.
A database on the distributor that stores data for replication, including transactions, snapshot jobs, synchronization status, and replication history information. The database is created when replication is activated.
Master database records Master database records the system-level information, SQL Server initialization information, and configuration settings for SQL Server. This database also records all login accounts and the mapping information from the name of a database to its primary file location.
Tempdb database
A database that is used to fulfill all temporary storage needs, including stored procedures and tables. The tempdb database uses SQL Server during query processing and sorting, and for maintaining row versions used in Snapshot isolation. A clean copy of the database is recreated with its default size every time SQL Server is started.
Table Continued
Glossary
163
Term/Technology
Model database
MSDB database
Transaction log
User database
Windows Server Failover
Cluster (WSFC)
Description
A template for all other databases on the system, including the tempdb database. When a database is created, the first part of it is created as a copy of the contents of the model database. The rest of the database is filled with empty pages. The model database must exist on the system because it is used to recreate tempdb every time SQL Server is started.
You can alter the model database to include user-defined data types, tables, and so on. If you alter the model database, every database you create has the modified attributes.
A database that holds tables that SQL Server Agent uses for scheduling jobs and alerts and for recording operators (those assigned responsibilities for jobs and alerts). This database also holds tables used for log shipping and for backup and recovery.
A file that is used as a write-ahead log. All transactional operations are recorded in the transaction log; a transaction is considered committed when the 'commit' transaction record has been written to the transaction log. The main purpose of the transaction log is for crash consistency. If there is a system crash, power failure, or similar disastrous event, then the transaction log has enough information to roll forward all committed transactions and roll back all noncommitted transactions.
A database created for and used by an application is considered to be a user database.
The set of servers (nodes) on which AlwaysOn is configured. The nodes do not share disks and each node must have an SQL Server instance.
164 Glossary
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project