HP Application Recovery Manager software Integration guide (March 2008)

P-VOL will be detected from the other backup performed in the resync mode.
This pair relationship should not be removed during restore and thus a switch
of the source volume with the replica cannot be performed.
To restore such a backup, perform one of the following prior to restore:
Manually remove the S-VOLs that were created during backups made in
resync mode using the omnidbvss command.
Set the variable OB2VSS_FORCE_INSTANT_RECOVERY in the omnirc
file and enable the restore option Retain source for forensics in the GUI.
This option must be selected to preserve the pair relationship between the
S-VOL and its P-VOL created in the backup performed in the resync mode.
If you perform restore using re-synchronization (the "copy of replica data"
restore) and the production source volume (P-VOL) is not presented on the
system, the restore is aborted. This can happen if you have at least two backups
created in different mode and you performed the "switch of disks" restore
before "the copy of replica data" restore.
To restore such a backup, perform one of the following prior to restore:
Manually present the P-VOL on the application system.
Set the variable OB2VSS_FORCE_INSTANT_RECOVERY in the omnirc
file.
The following considerations apply to restore using HP StorageWorks Disk Array XP
only:
Only three first-level mirrors can be used for instant recovery. Six additional
(cascading) copies are not supported.
You cannot start another instant recovery using the same disk on the application
system at the same time. A session can be started only after the preceding session
using the same disk on the application system finishes synchronization.
IMPORTANT:
After instant recovery, restored filesystems are mounted to the same drive letters as they
were at the backup time. If these drive letters have other filesystems mounted, these
filesystems are automatically dismounted before instant recovery, and the restored
filesystems are mounted afterwards.
Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume
Shadow Copy Service
64