This section describes the installation tasks.
The following figure shows the flow of tasks to install and Exchange Server and backup server.
Refer to the ETERNUS SF Installation and Setup Guide for details of installing AdvancedCopy Manager. In order to use this function, the AdvancedCopy Manager's agent must be installed in a Windows Server 2008 or later 64bit environment at both the Exchange Server and the backup server.
Installation must be to a LUN that is not subject to backup.
Refer to "Transportable Copy Configuration Installation" in the ETERNUS VSS Hardware Provider Copy Set Operation Technical Guide when performing these tasks.
VSSHP must be installed in a LUN that is not subject to backup.
The VSSHP installer is stored on the DVD-ROM "Agent Programs & Manuals".
<DVD-ROM drive>:\Agent_windows\AdvancedCopy_Manager\VSSHP\win2008_x64\install\setup.exe
Note
If the firewall is enabled, the port (TCP/IP) used by VSSHP must be registered as an exception. Refer to the manual for the relevant firewall for information concerning changing firewall settings.
Install the Exchange management tools.
If the Exchange Server has a cluster configuration, customize the Managed Server transactions at the Exchange Server.
Refer to the following manuals for transaction details:
ETERNUS SF Cluster Environment Setup Guide
13.1.7 Notes on replication in a clustered system
This section describes the environment settings to be performed before backup operations are started.
Use swsrpsetvol (Replication volume information setting command) to register the replication source volume (transaction volume) and replication destination volume (backup volume) in the replication function.
swsrpvolinfo (Replication volume information display command) can be used to check the registered replications source and replication destination volume information.
Note
Register all the transaction volumes (those to which files with *.edb, *.log, and *.chk extensions are allocated) and their backup volumes as replica volumes.
Set the transaction volumes as source volumes and the backup volumes as replica volumes. (Do not reverse the source and replica volumes.)
Set the Exchange server (the source volume server) as an operation server (by specifying "ORG" or "BOTH" as an argument of the -o option in the replication volume information configuration command (swsrpsetvol)).
Do not specify the -u option because the restoration needs to be performed.
Use the partition unit (gXdYpZ) as the volume registration unit. Do not register using the LUN unit (gXdY).
The drive letter map file defines the drive letters (or mount points) to be assigned to the shadow copies (ie, backup volumes).
If there are multiple copies (LUN unit copies) from the same copy source on a backup server, the drive letter (or mount point) may be removed after copying ends.
If you want to maintain the backup volume drive letter in the backup server, create a drive letter map file and define the drive letter (or mount point) assigned to the shadow copy (backup volume).
Create a drive letter map file with the following file name on the backup server:
<Environment directory>\etc\repl\data\EXDMAP.INI |
An example of the settings in the drive letter map file is shown below.
[DRVMAP] g1d1p1=F: g1d2p1=C:\mnt |
During backup processing, a drive letter is assigned to a backup volume based on the settings in the drive letter map file.
The drive letter assignment is not performed if there is no drive letter defined in the drive letter map file, or if the file contains a setting error (e.g., the relevant drive letter is in use, or an invalid directory is specified for a mount point, etc).
Set up the Exchange server or either of storage groups or databases based on the results of the operations design.
Allocating EDB, CHK, and LOG files
Allocate the Exchange server EDB, CHK, and LOG files.
Refer to "8.2.2.2 Designing storage groups or databases" for details.
Installing Exchange management tools
Be sure to install the Exchange server management tools on the backup server. The service pack level on the backup server must be the same as the Exchange Server.
Register Exchange server database information in the management file using swsrpdbinfo_ex2k3/swsrpdbinfo_exchange (Exchange database information registration command). Before backing up or restoring the Exchange server databases, execute this command on the Exchange server to perform an initialization. Additionally, execute this command after any change has been made to the Exchange server configuration.
Example: This example stores the database information of the storage group FirstStorageGroup (if the command is executed from the business server with Exchange Server 2007).
C:\>set SWSTGNODE=nodeAGT C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpdbinfo_exchange -evs VSVR -sgname FirstStorageGroup swsrpdbinfo_exchange successfully completed C:\> |
Example: This example registers the database MailBox1. (if the command is executed from the business server with Exchange Server 2010 or Exchange Server 2013).
C:\>C:\Win32App\AdvancedCopyManager\bin\swsrpdbinfo_exchange -dbname MailBox1 swsrpdbinfo_exchange successfully completed C:\> |
Set the information about the disks included in the copy source and copy destination volumes set as described in "8.2.3.2.2 Setting up the source and replica volumes", and enter this information in a copy set file to be used as VSSHP copy set information.
Use stxvgetolu (ETERNUS disk OLU/BOXID display command) from the VSSHP group of commands to check the physical disk number and OLU number of the copy source and copy destination disks. Use this information to enter the copy set information in a text file in the format below. Store the created file in a specific folder recognized by VSSHP under a filename recognized by VSSHP. Alternatively, use commands to specify the filename (path name).
Refer to "Creating a Copy Set File" in the ETERNUS VSS Hardware Provider Copy Set Operation Technical Guide for details.
Format (enter one copy set in one line)
Copy type ("OPC" or "QOPC"),
Copy options (cannot be specified),
Copy source physical disk number,
Copy destination OLU,
Copy destination BOXID
[Example of a copy set file entry]
OPC,,5,0x00c0,00E8000M9#####XXXXXXXX####YYYYYYYYYYYY## QOPC,,6,0x00c1,00E8000M9#####XXXXXXXX####YYYYYYYYYYYY## |
Execute stxvcopyset (Copy set file registration command) from the VSSHP group of commands at the transaction server to perform batch registration of the copy set information that has been entered in the copy set file. Refer to "Registering Copy Set Information" in the ETERNUS VSS Hardware Provider Copy Set Operation Technical Guide for details.
[Copy set file registration command specification method]
stxvcopyset [-c|-r] [-file copy_set_file] * Option contents: "-c: Check only", "-r: Check then register", "-file: Copy set file specified using full path" |
Note
The copy set file registration command overwrites all the contents that have already been registered in the specified file.
Check and save the copy set registration contents as a precaution. The VSSHP stxvcopyprt (Copy set registration information display command) can be executed at the Exchange Server to check the registration contents. Refer to "Copy Set Registration Information Display Command (stxvcopyprt)" in the ETERNUS VSS Hardware Provider Copy Set Operation Technical Guide for details.
[Copy set registration contents save method]
stxvcopyprt > [save file name (full path)] |