HP XP P9000 Replication Manager Software 7.6.0-00 Application Agent CLI User Guide

Requirements and precautions for backing up Exchange
databases
The following table describes the types of data subject to backup in the Exchange database.
Table 3 Types of data subject to backup in the Exchange database
ExtensionFiles subject to backupDatabase subject to backup
*.edb
*.stm
#
Data files (Exchange Server Information Store)
Exchange Server storage group
*.logTransaction log files
*.chkCheckpoint files
*.edb
Data files
Exchange Server Information Store
*.log
Transaction log files
*.chk
Checkpoint files
#
Files with the .stm extension exist only in Exchange Server 2003.
In Application Agent, data is backed up and restored in physical volumes units so the object
configuration of an Exchange database requires the following:
• The files to be backed up must all be placed on a RAID volume defined as a pair.
• Deploy the storage group or Information Store by taking into consideration that the unit for backup
is physical volumes.
In Exchange Server 2003 or Exchange Server 2007:
• If you deploy multiple storage groups in the same physical volume, you need to back up or
restore these storage groups as one group. When backing up or restoring a storage group
separately, deploy the storage group on a separate physical volume.
In Exchange Server 2010 or Exchange Server 2013:
• If you deploy multiple Information Stores on the same physical volume, you need to back up
or restore these Information Stores as one group. When backing up or restoring an Information
Store separately, deploy the Information Store on a separate physical volume.
• When you place an Exchange database that is subject to backup on the volume, note the following:
In Exchange Server 2003 or Exchange Server 2007:
• You cannot put the transaction log file (*.log) on a volume where a data file is placed.
• For online backup and VSS backup, data files (*.edb, *.stm) and checkpoint files (*.chk)
cannot be allocated to the same volume.
In Exchange Server 2010 or Exchange Server 2013:
• When you back up a database, you cannot put the transaction log file (*.log) on the same
volume that holds a data file (*.edb). Data is restored in physical volumes units so you will
not be able to perform a roll-forward restore operation if you put both the transaction log file
and the database file on the same physical volume. You must therefore put the transaction log
file and the database file on different physical volumes.
• When you set a name for a storage group or Information Store, note the following:
Application Agent CLI User Guide 69