This appendix is designed to be used like a Frequently Asked Questions section. It will help you find solutions to some of the common issues that might arise when running HP 3PAR Recovery Manager Software for Microsoft SQL Server.
Problem:
Recovery Manager displays error message “VSS_E_PROVIDER_VETO.”
Suggestion:
Check the application event log and VSS provider log from the production server. If you see “Maximum of 28 writable virtual copies per volume is allowed,” your virtual copy capacity might be full.
This error usually occurs when you mount a virtual copy. Unmount several virtual copies and continue the mount procedure.
Problem:
Even though Recovery Manager validated the configuration during operation, Recovery Manager exits without any messages during the check of the HP 3PAR StoreServ Storage System.
Suggestion:
Validation might fail without proper notification. Restart the HpRmCli Sql agent service on the backup and production servers.
Problem:
A restore of a backup, which was created using Symantec NetBackup via the Recovery Manager GUI, fails.
Suggestion:
When you use the Recovery Manager GUI to back up a virtual copy using Symantec NetBackup and a directory is specified for backup, you must enter the directory name and path precisely, including the upper- and lower casing (for example, MuTenFF). If the names do not match exactly, a restore of this backup will fail as Symantec NetBackup is case-sensitive.
When backing up a directory, specify the directory in exactly the same case as it exists on the file system.
Problem:
When you create a virtual copy on a SAN boot disk, the virtual copy creation fails with error “Error-VSS_E_HOLD_WRITES_TIMEOUT.” The in-box system writer that enumerates all operating system and driver binaries is included as well. The error usually occurs because the I/O cannot hold the system writer.
Suggestion:
HP does not recommend placing a database on the SAN boot disk. Place all important databases on separate SAN disks.
Problem:
As data blocks are copied per the copy-on-write technology, the space for virtual copies on the virtual volume might become 100% full either if virtual copy space was statistically allocated as a percentage of the virtual volume, or if there is no additional space available for the CPG to auto-grow. If the space for virtual copies on a virtual volume becomes 100% full, the virtual copies on the virtual volume may become invalid and subject to the Recovery Manager policy.
Suggestion:
Allocate more virtual copy space when creating virtual volumes during base volume creation, or use CPGs to manage the data generated by copy-on-write technology.
Problem:
You just installed Recovery Manager, but all GUI and CLI commands fail.
Suggestion:
If you install Recovery Manager via a remote desktop session, the newly added environment variables do not go into effect until you log out of the session. (If Recovery Manager is installed directly from the system console, these variables should be available immediately.)
Problem:
Symantec NetBackup takes a substantial amount of time to complete a backup process.
Suggestion:
Make sure you have the latest maintenance package installed for your NetBackup application.
Problem:
Recovery Manager is running in a Windows cluster environment and the application event log displays the Volume Shadow Copy Service error: “Unexpected error querying for the
IVssWriterCallback interface. Access is denied.”
Suggestion:
Reconfigure the security settings for the cluster environment as follows:
1. Ensure that Failover Cluster MS DTC is installed. Failover Cluster MS DTC is required for the following procedure.
2. ClickStart→Run→dcomcnfg orStart→Administrative Tools→Component Services. 3. ExpandComponent Services and clickComputers.
4. Right-clickMy Computerand selectProperties. 5. Select theCOM Securitytab.
6. UnderAccess Permissions, clickEdit Default.
7. Add aCluster Serviceaccount and selectLocal AccessandRemote Access. 8. Reboot the machine.
9. Perform these steps on the second node.
Problem:
You attempt to perform a media restore using the Recovery Manager CLI-tscommand and the attempt fails.
Suggestion:
If the restore log contains the error message: “client<client> peer name<peer name>is invalid for restore request,” the restore client is different from the backup client. Configure Symantec NetBackup to perform a redirected media restore as follows:
1. Create analtnamesdirectory on the NetBackup master server in the directory containing the backup policy for other clients:
Install_path\NetBackup\db\
2. Place an empty file namedNo.Restrictionsin thealtnames directory: Install_path\NetBackup\db\altnames\No.Restrictions Do not add a suffix to the files in thealtnamesdirectory.
3. Ensure that the NetBackup client name on the requesting client matches the name of the client for which the backup was created. (The peer name of the requesting client need not match the NetBackup client name.)
Problem:
When using Symantec NetBackup, you see this message: 0x1: ERROR: Cannot connect to [NBU server name]; socket error.
Suggestion:
Check whether you are using a different version of the NBU master server and the NBU client. If so, upgrade the NBU client to the same version as the NBU master server.
Problem:
Error in communication between Production Server and Backup Server and the vcdbasqlRMSQLAgent_1.logshows the following exception -
System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted.
Suggestion:
By default, HP 3PAR Recovery Manager for Microsoft SQL Server uses port 9932. This port might be used by other application, leading to a communication issue between backup server and production servers.
If you continuously notice this issue, follow either of the following steps:
• Change the default port used by Recovery Manager in the registry and restart HP 3PAR Recovery manager for SQL service from services.msc.
NOTE: The port used should be the same on both, backup server and production servers. • Find out the application using the default port and stop that application.
To find out the application using the default port:
◦
Open the command prompt◦
Runnetstat -ano | find "<port number>" Example:c:\>netstat -ano | find "9965" UDP 10.10.5.32: 9932 *:* 1252 UDP 16.154.142.171: 9932 *:* 1252 UDP 127.0.0.1: 9932 *:* 1252
This will list the process id of the application that is using the default port. (The process id of the application is 1252 in the example.).
To find out the application name for the process id which is using the port:
◦
Runtasklist | find "<port number>"Example:
c:\ >tasklist | find "9932"
application.exe 1252 Services 0 23,228 K
If it is possible, stop this application to free up the port<port number>and Restart HP 3PAR Recovery manager for SQL service from services.msc.
Problem:
While installing HP 3PAR Recovery Manager Software for SQL, the setup.exe prompts to uninstall 3PAR CLI though it is a supported version as per Single Point of Connectivity Knowledge for HP Storage Products (SPOCK) document. The installer does not provide an option to install HP 3PAR Recovery Manager Software for SQL .
Suggestion:
If you want to install only HP 3PAR Recovery Manager Software for SQL without its required components, then runRMS_2k8_x64.msi/RMS_2k8_x86.msidirectly from the folder \HP3PAR\RecoveryManagerSQL.
Ensure that you have the supported configuration as per Single Point of Connectivity Knowledge for HP Storage Products (SPOCK) document
Problem:
Backup Exec does not invoke post job command in the following cases: • Media configured for backup is offline
• Media configured for backup is running with low space • Network issue
In such cases, The impact on HP 3PAR Recovery Manager for SQL is as follows: 1. GUI will show backup status in progress
2. Backup time stamp will be empty
3. In case of one click backup, though the virtual copy is marked for deletion, the virtual copy does not get removed
4. Virtual copy will not be unmounted
Suggestion:
To overcome the above use case user have to manually run the postbackup commands
hprmcli sql postbackup –s <servername>[ -i <instancename> ] -t <timestamp> [ -d <database>] -r <Backup status>
–s <servername> The SQL server associated with the database.
-i <instancename> Optional. The SQL server instance associated with the database. If not specified, MSSQLSERVER (local) is used as the default value. -t <timestamp> The timestamp of the virtual copy to back up.
-d <database> Optional. The database for the virtual copy. If not specified, the instance for the virtual copy is used as the default value.
–r <Backup status> Backup completion status in NBU, DP or BE. If backup completed successfully then backup status will be 1 else it will be 0.
Problem:
After volume promote, on few occasions, the volume involved in the restore operation might not come online.
Suggestion:
to the same host again through HP 3PAR Management Console (MC) using a LUN ID different from the original LUN ID.
Problem:
After Repository location change, previously scheduled tasks do not work and they do not appear in Task Manager List.
Suggestion:
Delete those old tasks from Windows Task Scheduler. Clean up the Recovery ManagerTasks folder and create those tasks again from the Recovery Manager.
Problem:
Point of failure (using Auto restore) fails if, earlier the virtual copy is recovered manually using Point in time and No recovery option.
Suggestion:
Do not use any third party software or SQL management studio for backing up the transaction logs. Doing so would result in Recovery Manager not having the Transaction log backup sequence and this results in the failure of point-of-failure restore operation.
Problem:
If you are trying to uninstall HP 3PAR Recovery Manager for SQL , sometimes a window pops up prompting for server reboot.
Suggestion:
It is recommended that you clickCancel button, stop the HP 3PAR Recovery Manager for SQL service and HP 3PAR VSS Provider service and then try the uninstallation of the product again.
Problem:
If Recovery Manager for SQL server is in the workgroup and is managed by Recovery Manager for Exchange backup server, then one click backup fails.
Suggestion:
Symantec NetBackup must be installed using custom installation option and registration of the Symantec Netbackup service during the time of installation must be done explicitly using work group privilege.
Problem:
You might encounter the following error in HP 3PAR Recovery Manager Software for SQL CLI or GUI output or in the log files.
Suggestion:
Use the provcfg.exeutility provided with HP 3PAR VSS Provider to recreate an expired, an invalid, or a new certificate.
Problem:
If you have configured StoreServ during HP 3PAR VSS Provider installation or using HP 3PAR VSS Providerprovcfgutility, and later changed the TPDCERTDIRenvironmental variable or moved certificate from one location to another location, then you might encounter the following error:
Suggestion:
Use the provcfg.exeutility provided with HP 3PAR VSS Provider to recreate an expired, an invalid, or a new certificate.
Problem:
If the certificate is not saved using theprovcfgcommand provided by HP 3PAR VSS Provider, but by using some other command (for example, using HP 3PAR CLI command), then HP 3PAR Recovery Manager Software for SQL is dependent on the%USERPROFILE%or theTPDCERTDIR environment variables. If a user modifies these two variables to an invalid value, then HP 3PAR Recovery Manager Software for SQL does not work for that HP 3PAR CLI user.
Suggestion:
Use the provcfg.exeutility provided with HP 3PAR VSS Provider to recreate an expired, an invalid, or a new certificate.
Problem:
Mounting of Recovery Manager for SQL snapshot fails with the following error: Import snapshot information to backup server.
RME5189: ERROR: Fail to mount to specified mount point, in iSCSI environment of RMS Configuration
Currently unmounted. UnMount Successful
Suggestion:
Check if the iSCSI hostname of the Recovery Manager for SQL Production server or Backup servers created on HP 3PAR StoreServ is same as the name mentioned in the iSCSI initiator's configuration tab.
NOTE: The name is case sensitive. When checking iSCSI hostname, exclude the iqn number from the name mentioned in the iSCSI initiator's configuration tab.
For example:
If host side iqn number isiqn.1991-05.com.microsoft:rmsbackupsvr.2k10vfc.com Then hostname created on HP 3PAR Storeserv side should bermsbackupsvr.2k10vfc.com