When the Exchange 2007 Mailbox Server role is installed, setup adds two LCR-related performance objects to the...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Windows 2003 Performance Monitor. To open the Performance Monitor, either click Start --> Run and type Perfmon or click Start --> Administrative Tools and select Performance. This will bring up the Performance Monitor, shown in Figure 8.27.
The first object is the MSExchange Replica Seeder performance object, which, as you can see in Figure 8.28, contains only one counter, called Seeding Finished %. This counter is used to show the progress of database seeding in percent. When you add this counter, you can choose which instance (in this case, the particular storage group) you want to view the database seeding for.
The MSExchange Replication performance object contains at least 14 different counters (see Table 8.2).
Table 8.2: Continuous Replication performance counters.
|Copy Queue Exceeds Mount Threshold (CCR only)||Copy Queue Exceeds Mount Threshold (CCR Only) is 1 if the copy queue length is larger than the Mount Threshold specified by the Auto Database Mount Dial. This counter is used only with CCR. It will always be 0 with LCR.|
|CopyGenerationNumber||Copy Generation Number is the generation of the last log file that has been copied.|
|CopyNotificationGeneration Number||Copy Notification Generation Number is the generation of the last log file the copier knows about.|
|CopyQueueLength||Copy Queue Length is the number of log generations waiting to be both copied and inspected successfully.|
|Failed||Failed is 1 if the replica instance is set to failed, otherwise O.|
|InspectorGenerationNumber||Inspector Generation Number is the generation of the last log file that has been inspected.|
|ReplayBatchSize||Replay Batch Size is the number of log generations replayed together.|
|ReplayGenerationNumber||Replay Generation Number is the generation of the last log file that has been replayed successfully.|
|ReplayGenerationsComplete||Replay Generations Complete is the number of log generations already played in the current replay batch.|
|ReplayGenerationsPerMinute||Replay Generations Per Minute is the rate of replay in log generations per minute in the current replay batch.|
|ReplayGenerationsRemaining||Replay Generations Remaining is the number of log generations remaining to be played in the current replay batch.|
|ReplayNotificationGeneration Number||The generation of the last log file that replay knows about.|
|ReplayQueueLength||Replay Queue Length is the number of log generations waiting to be replayed.|
|Suspended||Suspended is 1 if the continuous replication is suspended. When the continuous replication is suspended, logs are not copied and replayed into the passive copy.|
As you can see, all these counters can be used to determine how replication for an LCR-enabled storage group have progressed, but a high-availability feature such as LCR should really be monitored using a proactive and automated monitoring solution such as Microsoft Operation Manager (MOM) with the Exchange Server 2007 Management Pack installed.
Managing Local Continuous Replication in Exchange 2007
Part 1: Exchange 2007 Local Continuous Replication overview
Part 2: Enabling Local Continuous Replication on a storage group
Part 3: Viewing the status for a Local Continuous Replication copy
Part 4: Switching to the LCR copy for database disaster recovery
Part 5: Suspending and resuming LCR for an Exchange 2007 storage group
Part 6: Manually adding an Exchange 2007 database to a storage group copy
Part 7: Use Exchange Eseutil for a passive storage group copy integrity check
Part 8: Disabling LCR on an Exchange 2007 storage group
Part 9: Adding LCR performance objects and counters
Part 10: Exchange 2007 LCR administration summarized
|This chapter excerpt from How to Cheat at Configuring Exchange Server 2007: Including Outlook Web, Mobile, and Voice Access, by Henrik Walther, is printed with permission from Syngress, a division of Elsevier, Copyright 2007.
Click here for the chapter download.
Dig Deeper on Microsoft Exchange Server Sync and Replication Issues