HP Application Recovery Manager software Integration guide (March 2008)

Configuration steps
1. Configure disk arrays needed for the backup.
2. Create an Application Recovery Manager VSS backup specification specifying
the VSS components to back up, as well as the Application Recovery Manager
backup options that define the behavior of your backup or restore session.
The Microsoft SQL Server or Microsoft Exchange Server has to be running on the
application system for a backup to start.
Replica types
The two basic families of replicas available with Application Recovery Manager are
split mirror and snapshot.
Split mirror replica
This type of replica is produced using mirroring technology, provided by HP
StorageWorks Disk Array XP. Mirroring technology allows a duplicate (a mirror) of
the filesystem or application data to be created during normal application use. When
a replica is required, a disk from the S-VOL host group is first synchronized with the
(P-VOL) and after that the pair is split leaving a fixed copy, or an independent split
mirror replica of the source volume. Depending on the configuration mode set in the
VSS hardware provider, two types of mirror replicas are possible after the pair is
split:
• If the provider is in the VSS compliant mode, the replica is independent copy or
clone of the source volume with no pair relationship between the replica and its
source volume.
• If the provider is in the resync mode, the replica and its source volume are in the
suspended mirror relationship enabling restore of such replica only by
re-synchronization the replica with its source volume.
Snapshot replica
This type of replica is produced using snapshot technology, provided by HP
StorageWorks Enterprise Virtual Array.
In the case of a snapshot replica, no synchronization is required before creating the
fixed point-in-time copies because a snapshot is a logical copy of the pointers to the
data rather than the data itself. Snapshot replicas are considered to be created almost
instantaneously and are immediately available for use. However, in some
implementations, background processes may continue for some time afterwards.
Integration guide 45