When backing up a Replication Service instance, backup may fail due to any of the
following reasons:
• The selected node is not available.
• The status of the storage group to be backed up is not "Healthy".
• Data Protector is not running on the selected node.
• Vssbar.exe cannot not be started on the selected node.
To avoid the session failing, select the option Revert to active node on failure in the
same dialog box. The backup will be restarted on the original server (active cluster
node) and the original storage group will be backed up. This option is ignored during
backup of an Information Store instance.
Prerequisites
• Before creating a backup specification and before running a backup, ensure that
the Exchange Server 2007 copy status is “Healthy”. Otherwise, you cannot
browse the objects to be backed up during creating backup specification, or the
backup will fail. Note that the status “Initializing” is not acceptable.
Limitations
• In CCR environments, if a replicated storage group (Replication Service instance)
is selected for backup, no other VSS writer (for example, filesystem writer or SQL
Server writer) can be selected to be backed up in the same backup session.
Because in this case, two writers would be located on different systems, but Data
Protector limits VSS backup sessions to involve only one system.
• In LCR and CCR environments, each storage group can have only one store.
• CCR clusters can have only two nodes.
Considerations
• Transaction log files are truncated after each full or incremental Microsoft Exchange
Server backup. The LCR and CCR clustering technologies, however, guarantee
that logs that have not been replicated are not deleted. Thus, running backups
in a mode that truncates logs may not actually free space. This may happen if
replication of logs has not completed yet.
• Before using XP VSS hardware provider in the resync mode, consider all
applicable limitations of this mode. The limitations are listed in “HP StorageWorks
Disk Array XP specifics” on page 362 and “Limitations” on page 398. Due to these
limitations, it is recommended to rather use XP provider in VSS compliant mode,
or EVA VSS provider, or VSS software provider.
Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service374
To Next Page
Loading...
Need help?
General