Export (0) Print
Expand All

Add a Mailbox Database Copy

Applies to: Exchange Server 2010

Topic Last Modified: 2011-03-19

When you add a copy of a mailbox database, continuous replication is automatically enabled between the existing database and the database copy. Database copies are automatically assigned an identity in the format of <DatabaseName>\<HostMailboxServerName>. For example, a copy of a database named DB1 that is hosted on a server named MBX3 would be named DB1\MBX3.

Looking for other management tasks related to mailbox database copies? Check out Managing Mailbox Database Copies.

  • The active copy of the mailbox database must be mounted.
  • The specified database must be a mailbox database. You can't use continuous replication for public folder databases. For public folder database availability, we recommend deploying multiple public folder databases and using public folder replication. For more information, see Understanding Public Folder Replication.
  • The specified Mailbox server must not already host a copy of the specified mailbox database.
  • The path for the specified mailbox database and its log files must be available on the specified Mailbox server.
  • The server hosting the specified database and the server that will host the database copy must both be in the same database availability group (DAG). The DAG must also have quorum and be healthy.
  • Circular logging must not be enabled for the specified mailbox database. If circular logging is enabled, you must first disable it. After the mailbox database copy has been added, circular logging can be enabled. For information about how to enable and disable circular logging, see Configure Mailbox Database Properties.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Mailbox database copy" entry in the High Availability Permissions topic.

  1. In the console tree, navigate to Organization Configuration > Mailbox.
  2. In the result pane, on the Database Management tab, right-click the mailbox database that you want to copy, and then click Add Mailbox Database Copy.
  3. On the Add Mailbox Database Copy page, complete the following fields.
    • Mailbox database name   This read-only box displays the name of the database for which you are going to make a copy.
    • Server name   Click Browse to open the Select Mailbox Server dialog box. Use this dialog box to select the Mailbox server that will host the copy of the mailbox database, and then click OK.
      Dd298080.note(en-us,EXCHG.140).gifNote:
      The Select Mailbox Server dialog displays all Mailbox servers. You must select a Mailbox server that it is in the same DAG as the Mailbox server hosting the active copy.
    • Activation preference number   Use this box to specify the preference value for the database copy. The activation preference number is used to break ties during database activation when multiple database copies meet the same criteria for activating.
  4. Click Add to add the copy of the mailbox database.
  5. On the Completion page, review the following, and then click Finish to close the wizard:
    • A status of Completed indicates that the wizard completed the task successfully.
    • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
  6. Click Finish to close the wizard.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Mailbox database copy" entry in the High Availability Permissions topic.

In this example, a copy of mailbox database DB1 is being added to a Mailbox server named MBX3. Replay lag time and truncation lag time are left at the default values of zero, and the activation preference is configured with a value of 2.

Add-MailboxDatabaseCopy -Identity DB1 -MailboxServer MBX3 -ActivationPreference 2

In this example, a copy of mailbox database DB2 is being added to a Mailbox server named MBX4. Replay lag time and truncation lag time are left at the default values of zero, and the activation preference is configured with a value of 5. In addition, seeding is being postponed for this copy so that it can be seeded using a local source server instead of the current active database copy, which is geographically distant from MBX4.

Add-MailboxDatabaseCopy -Identity DB2 -MailboxServer MBX4 -ActivationPreference 5 -SeedingPostponed

In this example, a copy of mailbox database DB3 is being added to a Mailbox server named MBX5. Replay lag time is set to 3 days, and truncation lag time is left at the default value of zero, and the activation preference is configured with a value of 4.

Add-MailboxDatabaseCopy -Identity DB3 -MailboxServer MBX5 -ReplayLagTime 3.00:00:00 -ActivationPreference 4
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft