Exchange mailbox database copies in ESI enable continuous replication of active databases for local- and remote-site replication. You can create multiple database copies in ESI on one or more servers in the same DAG. If a failure occurs, ESI supports automatic database-level recovery.
When you create one or more Exchange mailbox database copies in ESI, the first copy in the list is the original active database and the passive copies are listed next by activation preference number. When multiple database copies meet the same activation criteria, the preference number breaks the tie during database activation.
For DAGs with built-in replication, you can add mailbox databases copies with existing drive letters or create new drive letters to associate with the copies.
For DAGs in third-party replication mode, you can add copies to the primary mailbox database only if ESI can detect the corresponding host disk and storage information:
If ESI can present the associated storage for the primary mailbox database to the Exchange server, the Add Mailbox Database Copy wizard provides local-site replication options.
If ESI cannot present the associated storage to the selected server, the Add Mailbox Database Copy wizard provides remote-site replication options.
For DAGs in third-party replication mode, only synchronous replication is supported by ESI for the Exchange integration with EMC RecoverPoint. Because Microsoft does not currently support asynchronous replication for Exchange DAGs in third-party replication mode, the Asynchronous Replica Link Mode setting in ESI is available for experimental testing purposes only and is not currently supported for production replication.
You can use the Test-EmcSystemConnectedToBlockStorageSystem cmdlet in the ESI PowerShell Toolkit to determine if the host initiators are logged in to the storage system LUN.
After adding one or more mailbox database copies, you can view the status of the copies in the ESI GUI or with the Get-EmcMailboxDatabaseCopyStatus cmdlet in the ESI PowerShell Toolkit.
To add a mailbox database copy for local site replication:
In the left pane of the ESI window, select Applications > Exchange > Applicable Mailbox Server and the applicable mailbox forest.
Click Mailbox Databases, expand the database, and select the active database that you want to copy in a in a DAG with third-party replication mode.
In the Actions pane, click Add Mailbox Database Copy.
The Add Mailbox Database Copy wizard appears.
In the Mailbox Server page, set the following field values, and then click Next.
|
Field |
Description |
|
Database name |
A read-only field that displays the name of the original active database for the copy. |
|
Activation Preference Number |
Preference number for the database copy. Two is the lowest number for the first passive copy available for database activation, because the first copy is the original mailbox database. |
|
Servers |
Host mailbox server from the list of all available mailbox servers. You must select a mailbox server that is in the same DAG as the mailbox server hosting the active copy. |
|
Servers that already have a copy of this database |
Lists the other servers that also host a copy of the specified database. |
In the Storage System page, select the storage system that will host the database copy, and then click Next.
In the Storage Pool page, select the applicable storage pool, and then click Next.
In the Review Input Parameters page, confirm the parameters, and then click Next to add the copy.
In the Progress page, click Next.
Note: Click More Information for more progress details. If a problem occurs, an error message appears with options to resume or roll back the process. After the error is resolved, click Resume to resume the process. Click Rollback to revert to the previously executed step.
In the Summary page, click Finish.
To add a mailbox database copy for remote-site replication in a DAG in third-party replication mode:
In the left pane of the ESI window, select Applications > Exchange.
Click Mailbox Databases and expand and select the active database that you want to copy in a DAG with third-party replication mode.
In the Actions pane, click Add Mailbox Database Copy.
The Add Mailbox Database Copy wizard appears.
In the Mailbox Server page, set the following fields, and then click Next.
|
Field |
Description |
|
Database Name |
A read-only field that displays the name of the original active database for the copy. |
|
Activation Preference Number |
Preference number for the database copy. Two is the lowest number for the first passive copy available for database activation, because the first copy is the original mailbox database. |
|
Servers |
Host mailbox server from the list of available mailbox servers. You must select a server that it is in the same DAG as the mailbox server with the active copy. |
In the Replication Settings page, set the following field values and then click Next.
|
Field |
Description |
|
Production Journal Size |
Accept or change the default disk size. |
|
Remote Journal Size |
Accept or change the default disk size. |
|
Replication Cluster |
Select a replication cluster for the database copy. |
In the Production Journal Storage Pool page, select the storage pool for the production copy journal, and then click Next.
In the Remote Copy Storage System page, select the storage system connected to the replication site with the remote database copy and then click Next.
In the Remote Replica Storage Pool page, select the storage pool for the remote replica copy of the mailbox database, and then click Next.
In the Remote Journal Storage Pool page, select the storage pool for the remote replica journal, and then click Next.
In the Review Input Parameters page, verify the parameters, and then click Next.
In the Progress page, click Next.
Note: Click More Information for more progress details. If a problem occurs, an error message appears with options to resume or rollback the process. After the error is resolved, click Resume to resume the process. Click Rollback to revert to the previously executed step.
In the Summary page, click Finish.
