HP Data Protector A.06.11 Integration Manual page 207

If an Exchange Server 2003 Writer is being backed up, the session can fail with
VSSBAR reporting:
Snapshot could not be created.
In the application event log on the application system, the following event is recorded:
Event Type: Error
Event Source: ESE Event
Category: (16)
Event ID: 2004
Information Store (4916) Shadow copy 3 time-out (20000 ms).
Action
The following can help to solve the problem:
• Limit the number of users that are accessing the management system.
• Reduce the number of volumes in a snapshot set. Create a backup specification
dedicated to each storage group instead of one specification for the whole server.
See "Microsoft Exchange Server writer backup
Problem
Backup of a Microsoft Exchange Server 2007 CCR database copy fails
During a backup session of a database copy in a Microsoft Exchange Server CCR
environment, Data Protector reports a major error notifying that the backup session
has failed.
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.
specifics" on page 175.
Integration guide for Microsoft applications 207