HP Data Protector A.06.00 additional writers and HP StorageWorks Disk Array XP support for Microsoft Volume Shadow Copy Service integration

Set the variable OB2VSS_FORCE_INSTANT_RECOVERY in the omnirc
file and enable the restore option Retain source for forensics in the GUI.
When this option is selected, Data Protector preserves the pair relationship
between the S-VOL and its P-VOL created in the backup with 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 session is aborted. This may happen after at least two
backup sessions are run using the same backup specification in different modes
and you run a "switch of disks" restore before a "copy of replica data" restore.
Under such circumstances, perform one of the following prior to restore:
On the application system, manually present the P-VOL.
Set the variable OB2VSS_FORCE_INSTANT_RECOVERY in the omnirc
file.
The following restore considerations apply to restore using Disk Array XP Agent only:
You cannot start another instant recovery session using the same disk on the
application system at the same time. A session can be started only after the
preceding session completes synchronization.
After instant recovery, the restored filesystems are mounted to the drive letters as
were used at the time when backup was run. If these drive letters have other
filesystems mounted, these filesystems are automatically dismounted before instant
recovery, and the restored filesystems are mounted afterwards.
Microsoft Exchange Server writer instant recovery specifics
This section provides specific information on the point-in-time and roll-forward recovery
of Microsoft Exchange Server data.
With Microsoft Exchange Server 2003, you can restore a whole storage group or
individual stores only to the original location. With Microsoft Exchange Server 2007,
you can restore a whole storage group or individual stores to the original location
or to a different location. For details, see Microsoft Exchange Server 2007 writer
restore specifics on page 114.
Note that restore to the original location will fail if not all objects residing on the
target volume are selected for restore. Fore example, if you have four stores and
transaction logs on the target volume, and you select only one store for restore, restore
session will fail. Thus, the following configuration scenarios are possible when
restoring Microsoft Exchange Serve data:
Transaction logs and database stores are on the same target volume.
Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service120