Keep in mind, this only covers items that flow through the
Hub transport servers. Other items, such as updating personal contacts, tasks, and appointments, or
flagging a message will not be redelivered and are lost. The transport dumpster feature was only
available to CCR clusters in the release version of Exchange Server 2007. Service Pack 1 extends the
feature for LCR clusters as well.
Failover in Local Cluster Replication
LCR provides a quick recovery method when there is trouble with the active database and log files. It is
a manual process to bring the database back online. The actual recovery steps may differ depending on
what the cause of the failure is and what state the production database and log files are in.
The actual steps may change based upon the cause of the failure, and the condition of the active database
and log files. The general recovery process starts with dismounting the active database. The dismount is
performed using the Dismount-Database cmdlet. For example:
Dismount-Database -Identity ???MB100ccr\first storage group\mailbox database???
Part III: Working with PowerShell in a Production Environment
354
Once the database has dismounted, the LCR passive copy needs to be activated, and the LCR copy
stopped. The Restore-StorageGroupCopy cmdlet does both, and leaves the storage group and
database paths unchanged.
Pages:
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501