This section explains the following procedures for designing the backup of the Exchange database:
Designing server configurations
Designing storage groups
Designing circular logs
Determining the backup method
Preparing backup disks (LUNs) and backup volumes (partitions)
Designing copy sets
Storage Management Server
The Storage Management Server centrally manages and operates multiple Storage Servers.
Install the AdvancedCopy Manager function on this server. The Storage Management Server cannot also work as the Storage Server (Exchange server or backup server) that performs Exchange database backup.
Storage Server (Exchange server)
This Storage Server is used for the Exchange server operation.
In a Windows Server 2008 (x64) environment, install the AdvancedCopy Agent function on this sever. During installation, select the [Use Exchange Server 2007 linkage online backup function] checkbox.
Execute database backup or restoration from this server.
Storage groups subject to a backup and the disks (i.e., the transaction volumes) to which the storage groups are allocated must be connected to this server.
The Exchange server supports operations using Windows Server Failover Clustering (hereafter referred to as WSFC) or single nodes.
Storage Server (Backup server)
This Storage Server is used for the backup server operation.
In a Windows Server 2008 (x64) environment, install the AdvancedCopy Manager Agent function on this sever. During installation, select the [Use Exchange Server 2007 linkage online backup function] checkbox.
In addition, install the Exchange server system management tool to check the backup data.
The disks (ie, the backup volumes) to which the database volumes are backed up must be connected to the backup server.
Note
The backup server cannot be used in cluster operation mode.
Only one backup server is supported from one (one cluster service) Exchange Server.
The Exchange server and backup server cannot be used in combination.
An Exchange Server 2003 and an Exchange Server 2007 backup server cannot both be on the one backup server machine.
If an environment contains both Exchange Server 2003 and Exchange Server 2007, a separate Exchange Server 2003 backup server and a separate Exchange Server 2007 backup server must be provided.
The following figure shows a server configuration example. The minimum configuration contains three machines, a Storage Management Server, an Exchange Server, and a backup server, as well as one ETERNUS disk storage systems.
Figure 9.33 System configuration example
Advanced Copy for backup is performed in units of disks (i.e., LUNs), not in units of partitions. For this reason, when multiple partitions are created on a disk, the individual partitions must contain files belonging to a specific storage group (refer to Example A below). An operation cannot be performed with a configuration in which one disk contains files belonging to different storage groups (refer to Example B below), or which contains files used by other applications (refer to Example C below). Configure a copy target disk such that it contains only partitions for Exchange Server log files or database files.
Figure 9.34 Partition configuration
The operation can be performed in the configuration shown in Example A.
However, it is recommended that a configuration consisting of multiple disks (such as the one as shown below) is used for improved performance and easy management.
Figure 9.35 Recommended partition configuration (multiple disk configuration)
Point
Assign drive letters (or mount points) to the volume (partition) that configures the storage group. AdvancedCopy Manager supports both drive letters and mount points.
Note
Use copy source and copy destination disks in their initial state, in which Exchange Server linkage function backup has not been performed. Refer to "9.2.6.4 Initializing a disk" for details of disk initialization.
Database file allocation
The Exchange server linkage function provides the backup and restore function that backs up or restores the Exchange server databases in units of storage groups. AdvancedCopy Manager copies data in units of volumes (partitions). For this reason, if two or more storage groups exist in the same volume, the backup and restore function cannot be used.
With these restrictions in mind, the following instructions must be followed when designing the physical layout of storage groups:
Only store Exchange server database files that are to be backed up in the volume in which the database files are to be allocated. If a file other than an Exchange server database is created in the same volume, it is also backed up. Accordingly, when it is restored, the latest data in the non-database file will be damaged.
Only one storage group can be stored in the same volume. Say, for example, that storage groups 1 and 2 are stored in the same volume. When storage group 1 is backed up, the files in storage group 2 are also backed up. When only storage group 1 is subsequently intended to be restored, storage group 2 is also restored. As a result, when the database of storage group 2 has been updated, the storage group 2 database is corrupted by the data from the time of the backup (refer to the figure below).
Figure 9.36 Data destruction example
Note
When a backup is performed from a volume that contains a database that is subject to a backup and a database that is not subject to a backup, the data integrity of the database that is not subject to a backup is not guaranteed.
A database can not be allocated to the volume that contains the Exchange server and AdvancedCopy Manager executable and control files.
Point
To copy an already allocated database file, use the Exchange system manager to move the file.
Transaction log file allocation
Figure 9.37 Relationship between log file allocation and feasible restoration modes
| Restoration mode | ||
|---|---|---|---|
Point-in-time | Roll-forward | ||
Log file allocation | Database files and log files are allocated to the same volume. | Enabled | Disabled |
Database files and log files are allocated to separate volumes. | Enabled | Enabled | |
When a log file is stored on the volume containing a database, roll-forward restoration cannot be performed. This is because Advanced Copy performs copying in units of volumes. If a log file is stored in the volume containing a database and copy is performed (virtual copy is performed), the log file at the time of backup overwrites the latest log file. When the roll-forward restoration is specified, AdvancedCopy Manager checks whether the database file and log file are stored on the same drive.
The roll-forward restoration can only be performed when a transaction log file and database file are stored on separate drives.
The point-in-time restoration can be performed regardless of the log file allocation.
CHK file allocation is not related to the available restoration modes.
Therefore, allocate the database files and log files to different volumes when roll-forward restoration is required. Although Exchange normally creates database files and transaction log files in the same volume, the Exchange system manager can be used to move the transaction log files to another volume.
Distributed allocation of an EDB file
As shown in the figure below, a database file can be distributed and stored in multiple volumes. When a storage group is distributed and stored in multiple volumes, AdvancedCopy Manager backs up all the volumes.
Figure 9.38 Distributing a database file to multiple volumes
Circular logging must be disabled to implement AdvancedCopy Manager backup of Exchange databases. A backup cannot be performed if circular logging is enabled.
With circular logging disabled, the log files are sequentially created as the amount of logged data increases and they reduce the free volume space accordingly. When a backup is successful, however, backed-up data that is no longer needed in the volume can be deleted.
The Exchange database online backup function supports the replication function.
Different copy methods cannot be mixed in the one storage group. Select one of the following copy methods for each storage group unit.
Snapshot backup
This backup method uses the ETERNUS disk array OPC function. A backup is taken by starting OPC.
Differential snapshot backup
This backup method uses the ETERNUS disk array QuickOPC function. A backup is taken by starting or restarting QuickOPC.
Note
Exchange Server 2007 database backup using SnapOPC, SnapOPC+, or EC/REC is not supported.
Placement of the backup disk
The backup disks and the disks used by transactions must be placed on the same ETERNUS disk array.
Creating backup disks and volumes (partitions)
A backup volume must be prepared (refer to 9.1.3 Preparation) before the operation that is explained in 4.4.5 Fetching device information on a Storage Server is performed.
A backup volume must be created so that the partition size and start offset match those of the transaction volume (because Advanced Copy is executed in units of disks when the backup is performed). In a "1 LUN = 1 partition" configuration, it is enough to match the partition size - the start offset need not be recognized.
Figure 9.39 Creating a backup volume
Note that a backup disk LUN and a transaction disk LUN of the same size must be prepared.
Supported disk partition formats are MBR and GPT. However, the transaction disk and backup disk partitions must have the same format.
Design copy sets so that there is a 1:1 relationship between backup disks and all the transaction disks related to the storage group being backed up.
Figure 9.40 Copy set registration
Copy sets with the same transaction disk but different backup disks cannot be registered at the same time.
Figure 9.41 When registration to a copy set is not possible
Exchange linkage commands (swsrpXXX_exchange) perform processing on particular copy sets based on the storage group name.
Figure 9.42 When multiple storage groups are registered
For one Exchange Server machine (one cluster environment), there must be one backup server machine and a non-cluster environment.
Figure 9.43 Exchange Server and backup server example
