HP Application Recovery Manager software A.06.10 Administrator's guide (March 2008)

Limitations
• Instant recovery fails in the following situations:
• The source volumes are not presented to the application system.
• If the current configuration of the participating volume groups on UNIX or
partitions on Windows is different from the volume group/partition
configuration during the backup and recorded in the SMISDB.
• After instant recovery, restored filesystems are mounted to the same mount
points or drive letters on the application system as they were at the backup
time. If these mount points or drive letters have other filesystems mounted,
instant recovery fails.
For more information about EVA instant recovery considerations and limitations, see
the HP Application Recovery Manager software product announcements, software
notes, and references and the HP Application Recovery Manager software concepts
guide.
Instant recovery methods
Depending on the instant recovery options you select in the Application Recovery
Manager GUI or CLI, instant recovery can be performed in three ways:
• by switching disks
• by copying replica data and retaining the source volumes
• by copying replica data without retaining the source volumes
Switching disks
With this method, the source volumes are unpresented and the target volumes (replica
from the selected session) are presented in the place of the source volumes. During
this action, information such as the volume names and comments are also exchanged
between the source and target volumes. You can select to retain the old source
volumes. However, you cannot retain the replica and perform another restore from
this backup.
This method may change the physical location of the application production data.
After instant recovery, a replica becomes the source storage volume, therefore, the
performance characteristics of the target storage volumes now become the
characteristics for the application. The application starts running on the physical disks
that were used for backup.
Restore46