HP XP Command View Advanced Edition Software User Manual
Page 71
•
P9000 RMXP Shadow Copy Provider must be installed in advance, on both the database server
and the backup server. If P9000 RMXP Shadow Copy Provider has not been installed on those
servers when Application Agent is installed, P9000 RMXP Shadow Copy Provider will be installed
together with Application Agent.
•
The backup server is required even if data is not backed up to tape. This is because the backup
server imports VS snapshots and verifies the Exchange database.
•
If Veritas Snapshot Provider is installed on the database server or backup server where a VSS
backup will be performed, make sure you use version Veritas Snapshot Provider 1.04 or later.
If a VSS backup is executed using version Veritas Snapshot Provider 1.03 or earlier, the volume
to be backed up might be left with
Read-Only
and
Hidden
attributes. If this happens, the drive
will not be allocated at system startup and Exchange Server will not operate normally. If this occurs,
release these attributes as described in Microsoft Knowledge Base Article 840781.
•
If a system failure or other problem causes a VSS backup to be interrupted, the volume that is the
target of the backup might be left with the
Read-Only
and
Hidden
attributes. If these attributes
remain, the drive will not be allocated at system startup, and Exchange Server will not operate
normally. If this occurs, release the attributes as per Microsoft Knowledge Base Article 840781.
•
You can acquire backup or delete transaction logs while Exchange Server is operating. However,
you cannot back up data while Exchange Information Store service is shut down.
•
During backup, the database write processing of Exchange Server shuts down for a certain period
(up to 10 seconds). During that period, the database write processing of Exchange Server (such
as sending mail) is suspended. After backup finishes, the database write processing of Exchange
Server is resumed.
•
Since the number of log files might increase during backup operations by VSS, when you perform
backup by using VSS, the backup results might contain a log file that has not been recorded in
the catalog.
•
Set the environment of Application Agent to use VSS. For details on environment settings required
to use VSS, see “
Specifying settings for using VSS
•
The Information Stores of the storage group that are to be backed up must all be mounted in ad-
vance.
•
When Protection Manager version 4.4 or earlier is used to back up storage groups, the Information
Stores of storage groups to be restored must all be mounted in advance. When Protection Manager
version 5.5 is used, the Information Stores do not need to be mounted in advance in order to be
restored.
•
If the name of the Exchange database has been changed, you must perform the following opera-
tions:
• For Exchange Server 2003 or Exchange Server 2007, unmount all of the Information Stores
in the relevant storage group and then remount them.
• For Exchange Server 2010, unmount the Information Stores and then remount them.
•
Do not use LUN#0 as a secondary volume for the backup destination. If the LUN#0 disk is used
as a secondary volume for the backup destination, other disks might not be recognized.
•
When data is backed up, a folder named
DRMVSSMETADATA_
backup-ID is created in the root
directory of the secondary volume. Do not delete this folder, as a backup metadata file necessary
for restoration is stored in it. This folder is automatically deleted after data has been restored.
•
Do not mount another volume in a directory on the volume to be backed up. If another volume is
mounted, mounting and restoration for the secondary volume might fail.
•
It might take a long time to execute the backup command for VSS backup, because the VSS import
server verifies the backup result database. The time required to verify the database depends on
factors such as the database capacity, the backup server's machine performance, and disk per-
formance. Also, an option can be specified in the
drmexgbackup
or
EX_DRM_EXG_BACKUP
command used for completing the backup operation without verifying the database. If you omit
Application Agent CLI User Guide
71