HP Application Recovery Manager software Integration guide (March 2008)

• All stores in a RSG must originate from the same storage group due to the
Microsoft Exchange Server limitations.
• If you have a CCR environment where the original database resides on a different
EVA disk array than the database copy and you perform backup of the database
copy, note that the restore of this copy to original database will fail, because
restore to a different disk array is not supported. In this case, perform manual
failover of the databases before the restore.
• Restore to a different location is only possible using Microsoft Virtual Disk Service.
With XP hardware provider this means that restore to a different location is
possible only after a backup in VSS compliant mode.
• With the XP VSS provider, if a backup of an LCR or CCR storage group copy is
performed in the resync mode, restore of such backup to the original location
(original database or Exchange Information Store) by default fails.
The reason is that the source volumes, on which the database copy (or Exchange
Replication Service) resides, are in the suspended mirror relationship with the
replicas, which should be restored to the original database.
To perform such restore, the source volumes presented to the database copy are
first unpresented from the database copy and presented to the original database.
This results in the lack of source disks presented to the database copy, so you
should again set up the CCR or LCR environment after restore.
To enable such restore, set the omnirc variable
OB2VSS_FORCE_INSTANT_RECOVERY to 1, perform restore, and after it,
manually set up the LCR or CCR environment.
Instant recovery
For general information on instant recovery, refer to the online Help.
The Application Recovery Manager VSS integration provides instant recovery of
MSDE Writer, SqlServer Writer, Microsoft Exchange Server 2003 Writer, and
Microsoft Exchange Server 2007 Writer.
You can selectively restore separate writer’s components only if they reside on separate
target volumes. Instant recovery of separate components also requires that the target
volumes with components data should not contain any other data. If you do not select
all writer’s components residing on the target volumes to be restored, the restore
fails.
Before starting an instant recovery, Application Recovery Manager checks whether
the data that is required for the components restore is available. If the check fails,
the instant recovery session also fails, ensuring that no data that does not belong to
the components is lost.
Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume
Shadow Copy Service
68