HP 3PAR Recovery Manager Software for Microsoft SQL Server Licenses - Manual (Page 80)

B Troubleshooting
This appendix is designed to be used like a Frequently Asked Questions section. It will help you
find solutions to some of the common issues that might arise when running HP 3PAR Recovery
Manager Software for Microsoft SQL Server.
Problem:
Recovery Manager displays error message “VSS_E_PROVIDER_VETO.”
Suggestion:
Check the application event log and VSS provider log from the production server. If you see
“Maximum of 28 writable virtual copies per volume is allowed,” your virtual copy capacity might
be full.
This error usually occurs when you mount a virtual copy. Unmount several virtual copies and
continue the mount procedure.
Problem:
Even though Recovery Manager validated the configuration during operation, Recovery Manager
exits without any messages during the check of the HP 3PAR Storage System.
Suggestion:
Validation might fail without proper notification. Restart the RMSql 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 lowercasing (e.g., 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:
80 Troubleshooting