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

This problem may occur in CCR environments, due to a Microsoft Exchange Server
2007 issue with incorrect display of database copy states in Exchange Management
Console. In such a case, a database copy in a "Failed" state may be displayed as
"Healthy".
Action
To make the Exchange Management Console show the real status of a database
copy, perform either of the following actions:
• Update Microsoft Exchange Server 2007 with Service Pack 1.
• Perform re-seeding procedure as follows:
1. On the passive node, suspend the replication by using
Suspend-StorageGroupCopy cmdlet.
2. Delete all log files from the Logs directory of the database copy.
3. Seed the database copy or re-synchronize the original database and its copy
by using the Update-StorageGroupCopy cmdlet.
4. Resume the database copy by using the Resume-StorageGroupCopy
cmdlet.
5. On the passive node, check the status of the Exchange Replication Service
by using vssadmin list writers command. If the status is not stable,
restart Microsoft Exchange Replication Service.
Problem
Exchange Replication Service writer instance in LCR environment is not displayed in
the Data Protector GUI
In the Data Protector GUI, while creating a backup specification, the Microsoft
Exchange Writer(Exchange Replication Service) object is not displayed
on the pane for selection of backup objects.
This problem may occur in LCR environments, due to a Microsoft Exchange Server
2007 issue with incorrect display of database copy states in Exchange Management
Console. In such a case, a database copy in a "Failed" state may be displayed as
"Healthy".
Action
To make the Exchange Management Console show the real status of a database
copy and to enable selection of the backup object, restart Microsoft Exchange
Replication Service.
Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service134