HP Application Recovery Manager software Integration guide (March 2008)

Actions

1. Stop the Virtual Disk Service (VDS):

• Check that Virtual Disk Service is started, stop it using the command net

stop vds or via the Control Panel.

• If the above step does not help, stop the Virtual Disk Service by terminating

the process vds.exe using the Task Manager. VDS will be started

automatically as needed.

• Alternatively, you could also log in to the system again and check if the

system requests your confirmation to stop a crashed VDS. If it does,

reconfigure the debugger to launch automatically to avoid similar problems

in the future. This can be done by setting the

HKLM\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\AeDebug value Auto to 1.

2. Check your configuration.

Successful Application Recovery Manager backup or restore completion is

influenced by a number of factors imposed by non-Application Recovery Manager

components, including Microsoft Exchange Server and VSS. One of the factors

is timing, which in turn is impacted by environmental conditions such as I/O

loads, storage device activity and concurrent Application Recovery Manager

actions.

To inhibit potential issues, it is recommended that you balance Application

Recovery Manager activity across the available activity or maintenance window.

If you encounter issues, review and possibly reduce concurrent Application

Recovery Manager activities such as concurrent backups or restores.

Backup problems

Problem

Microsoft Exchange Server writer backup failed.

When you start a backup of a Microsoft Exchange Server 2003 Writer, the following

error is displayed:

[MAJOR]: Writer ‘Microsoft Exchange Writer’ failed to prepare files

for backup.

Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume

Shadow Copy Service