HP Application Recovery Manager software Integration guide (March 2008)

• HP Application Recovery Manager software installation and licensing guide

on how to install Application Recovery Manager on various architectures and

how to install the Application Recovery Manager Microsoft Volume Shadow

Copy Service integration and ZDB agents.

• Writers and shadow copy providers documentation for instructions on how

to install and configure writers and providers on your system.

• To be able to perform a backup and instant recovery, ensure that the source

volumes do not reside on GPT (GUID Partition Table) disks. If the system where

you want to install an application database has GPT disks, convert them to MBR

(Master Boot Record) disks using the Windows Management Console. For

instructions on how to perform the conversion, see the Microsoft Windows Help.

VSS transportable snapshot prerequisites

For VSS transportable snapshots there are additional prerequisites:

• The backup system must be configured to accept connections from the application

system.

• The VSS and VDS hardware providers must be installed and configured on the

application and backup system. Refer to the provider documentation for details.

Limitations

For a list of general Application Recovery Manager limitations, see the HP Application

Recovery Manager software product announcements, software notes, and references.

Common integration-specific limitations

• To run a VSS integration backup, the writer’s data must be on an NTFS filesystem.

• The VSS integration backup of writers which store their data on network shared

volumes is not supported.

• Preview is not possible for VSS backup sessions.

• With Microsoft Exchange Server 2007 which is running in a CCR environment

and whose database copy resides on the backup system, there are three particular

situations where you need to consider additional steps for performing instant

recovery:

• When Disk Array XP VSS hardware provider is used, and the application

system, where the production database resides, and the backup system, where

the database copy resides, are connected to two different disks arrays that

are not configured in the same SAN. In such configuration, the application

system does not see LUNs on the backup system and vice versa.

Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume

Shadow Copy Service