HP StorageWorks Application Recovery Manager Administrator's Guide (T4395-96004, February 2008)

Appendix B
Known Non-Application Recovery Manager Issues and Workarounds
Appendix BB-10
password are stored in registry as a plain text.
• During a VSS Transportable Backup the following error is reported
by the VSSBAR on the backup server: Import failed.
If the backup server is inspected after the failed session, the
snapshots are actually visible as new disks in the Device Manager, as
well as in the Disk Manager. In the Disk Manager window the
volumes may even be visible (together with the volume labels), but
the Windows "volmount" CLI tool does not detect and show them. All
subsequent backup sessions fail.
Workaround: Delete the VSS Snapshot Database on the backup
server and reboot the server. To locate the VSS Snapshot Database
files, use the registry editor to find the value of the following registry
keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Backu
pRestore\FilesNotToBackup\VSS Service DB
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Backu
pRestore\FilesNotToBackup\VSS Service Alternate DB
• A backup session can fail if there are more than 4 source volumes
(original virtual disks) in a snapshot set. (QXCR1000101055)
Workaround: None. Make sure that the number of source volumes in
a backup specification does not exceed 4 and that the next snapshot
starts no earlier than 30 minutes after the last snapshot was deleted.
Volume Shadow Copy Service
• The following MSDE writer components cannot be restored while the
SQL server is online: master, model and msdb.
• When restoring the MSDE writer while the SQL server is offline, the
restore completes with error messages similar to the following:
Major] From: [e-mail] "MSVSSW" Time:
8/7/2003 1:49:49 PM
Component 'master' reported:
'CSqlRestor::PrepareToRestore failed with HRESULT =
0x8000ffff'.
Workaround: None. The problem may be resolved in a future
Microsoft Windows Server 2003 Service Pack release.