User's Manual

B.2
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide
3PAR Confidential
Suggestion:
Restart the RMSql agent service on the backup and production servers.
Problem:
When backing up a virtual copy using NetBackup through the Recovery Manager GUI, if a
directory is specified for backup, the directory must be entered in exactly the same case as it
resides on the file system. If this is not done then a restore of this backup will fail. This is a
limitation of Veritas NetBackup.
Suggestion:
When backing up a directory, specify the directory in exactly the same case as it exists on the
file system.
Problem:
A virtual copy creation fails with error “Error-VSS_E_HOLD_ WRITES_
TIMEOUT” when creating a virtual copy on a SAN boot disk, the in-box system writer which
enumerates all operating system and driver binaries will be included as well. The error mostly
occurs because of the I/O cannot hold on the system writer.
Suggestion:
Database located on the san boot disk is not recommended. All the important databases
should be located on the separate san disks instead.
Problem:
As data blocks are copied per the copy-on-write technology, the snapshot space of a virtual
volume may become 100% full if it has been statistically allocated as a percentage of the
virtual volume, or if there is no additional available space for the CPG to auto-grow. In the
event that the snapshot space of a virtual volume becomes 100% full, the snapshots for the
virtual volume may become invalid and subject to the configured Snapshot Policy.
Suggestion:
Allocate more snapshot space when creating virtual volumes during base volume creation or
use CPGs to manage data generated by copy-on-write technology.