HP P9000 Replication Manager Software 7.3.1-00 User Guide

• The files to be backed up must all be placed on a RAID volume defined as a pair.
• For Exchange 2003/2007 servers, deploy the storage group taking into consideration that backups
are conducted in units of volumes. If you deploy multiple storage groups in the same 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 volume.
• When you place an Exchange database that is subject to backup on a volume, note the following:
• You cannot put the transaction log file (*.log) on a volume where data files are stored.
• Data files (*.edb, *.stm) and checkpoint files (*.chk) cannot be allocated to the same
volume.
• Do not use the following characters when setting a name for a storage group: = ; \ / “ ,
• Do not register the instances of multiple Exchange resources into a cluster group.
• If a mounted storage group or information store is renamed in Exchange Server 2003 or 2007,
all of the information stores under the corresponding storage group must be unmounted and then
remounted.
• If an information store is renamed in Exchange Server 2010, the information store must be unmoun-
ted and then remounted.
• Exchange Server 2010 recovery information stores cannot be backed up. Recovery information
store files and folders must be on a different file system from the information stores.
• To back up a storage group in Exchange Server 2003 or 2007, all of the information stores in
the storage group must be mounted.
SQL Server data and requirements
The following are the types of SQL Server data subject to backup using Replication Manager. Backed-up
databases differ depending on the option specified in the Create Replica Wizard.
Table 20 Types of data subject to backup (SQL Server)
Storage destination for
backup files
Backup file name
Files subject to
backup
Database subject to backup
Secondary volume
Same as the backup
source file name
Data file
master
model
msdb
User database
Distribution database
Secondary volume
Same as the backup
source file name
Transaction log file
Varies depending on the VDI metafile storage directory
specified.*
Metafile
Legend:
*: When a VDI metafile storage directory is registered in the SQL Options tab of the Setup Application
Agent dialog box, the metafile is stored in the registered directory. The file name is
backup-ID_database-ID.dmp. When default is selected for the VDI metafile storage directory,
the metafile is stored in the directory that contains the file whose management number (file_id) for
SQL Server in the database file is a minimum value. The file name is META_xxx.dmp.
Databases are backed up and restored in units of volumes, so the object configuration of an SQL
Server database requires the following:
• Configure each instance so that its data files are on one volume. In addition, do not place data
files of multiple instances on a single volume.
• The following should not be placed in the same directory as the database configuration files
(*.mdf, *.ndf, and *.ldf):
Managing application replicas380