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

NOTE:
Changing the modes between backup sessions may have an impact on restore. For
details, see HP StorageWorks Disk Array XP considerations on page 119.
Microsoft Exchange Server writer specific configuration
A backup of the Microsoft Exchange database is considered successful only when
consistency check of the replicated data files succeeds.
For instant recovery–enabled backups, it is recommended that the stores and
transaction logs reside on different source volumes. Such an Exchange Server
configuration enables you to restore individual stores and perform roll-forward
recovery. Otherwise, if all data resides on the same source volume, all the data
residing on this volume must be restored, thus only point-in-time recovery is possible.
Prerequisites
When configuring an Exchange Server 2007 LCR environment, ensure that the
original database and the database copy of the Exchange Server have the same
directory and file structure. Failing to do so will result in unsuccessful attempts to
mount the database after restore of an LCR copy to the location where original
database resides.
Microsoft Exchange Server 2007 configuration in CCR environments
In CCR environments where a production database resides on a different EVA disk
array from the database copy, and the backup system and the application system
are not the same physical system, ensure that:
The backup system is connected to the same disk array where the replicas (volume
shadow copies) of backup objects (either production database or database copy)
will be created. If you back up the production database, the backup system must
be connected to the disk array on which the production database resides. If you
back up the database copy, the backup system must be connected to the disk
array on which the database copy resides.
The VSS/VDS hardware provider is configured for the same Command View on
both EVA disk arrays.
If the above prerequisites are not met, failed presentation of replicas to the backup
system causes entire backup session to fail.
Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service80