Microsoft Exchange Server Writer Specific Configuration; Prerequisites - HP Data Protector A.06.11 Integration Manual

• Non-strict
If any folder on the volume does not belong to the component, the ZDB to disk
or instant recovery fails.
• Disabled
A check detects whether there is more than one component on the volume and
whether there is any other data besides the component's data on the volume, but
the session will not fail.
IMPORTANT:
If the configuration check is disabled for an instant recovery, you will lose the data that
does not belong to a component, but resides on the same volume as the component.
Disable configuration check only if instant recovery cannot be performed with an enabled
configuration check and only if you are sure that this will not result in a loss of data
during the instant recovery.
The configuration check should not be disabled except for the cases when instant
recovery cannot be performed with an enabled configuration check. Due to the
specific behavior, some writers (not applicable to the MSDE Writer and Microsoft
Exchange Server writers) may create temporary files on components volumes during
backup and instant recovery causing the check failure. In such cases, instant recovery
is not possible without disabling the check.

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
354 Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service