White Papers

BP1013 Best Practices for Enhancing Microsoft Exchange Server 2010 Data Protection and Availability 36
Figure 13 DAG seeding (1 database) over the replication network: source host CPU impact
Figure 14 DAG seeding (1 database) over the replication network: target host CPU impact
In order to further understand the load on local host resources, we analyzed the disk access to both
the source and target volumes, focusing on disk read access on the source and disk writes access on
the target.
Figure 15 and Figure 16 show the disk access patterns of the two volumes used by the mailbox
database copy process.
Note: The counter values for I/O operations (reads or writes) for processes reported by Performance
Monitor include all the operations executed by the process against the entire disk sub-system, not
only on the volume we are analyzing. Still, we reported them here because the monitored process
matched the pattern of the volume access.
As illustrated previously in this section we found confirmation that during the operations all the source
volume reads were handled by the Information Store during the timeframe of the pure database copy
and when the mailbox database was mounted and then handled directly by the Replication service
during the transfer of the Content Index. This would also explain the Replication service processor
utilization increase during the last phase of the copy (when transferring the Content Index). This is