White Papers

BP1013 Best Practices for Enhancing Microsoft Exchange Server 2010 Data Protection and Availability 34
We configured a dedicated 1Gbps network (see Appendix A3.2) between the two nodes of the DAG to
handle the Replication traffic required for regular and exceptional DAG seeding procedures. First we
used this network to measure the load of the seeding and reseeding procedures on the DAG hosts.
Test Details for one database, seeding process using the Replication network:
Details Initial seeding or reseeding of the database using Exchange Replication
service
Workload No user workload applied
Key indicators Host resources impact
The seeding activity can be started by the Exchange Management console or the PowerShell
command line. We used the command line shown below (server and database names are reported
with wildcards as the commands were reused differently during multiple instances of the same test).
Additional command line options were not included because they were not essential to the tests.
While running, both of these command lines immediately started the file transfer copy.
The commands for initial mailbox database seeding (including the content index), create the database
copy object, and replicate the data:
[PS]>Add-MailboxDatabaseCopy -Identity DBn -MailboxServer MBXn
-ActivationPreference 2
The commands for full update of a mailbox database (including the content index) and replicating the
data of a pre-existing database copy:
[PS]>Update-MailboxDatabaseCopy -Identity DBn\ MBXn
Figure 12 shows the data flow for a DAG seeding activity over the network.