Before the failover,
the passive node may need to be reseeded to bring the node to current state.
In the event that a server needs to be rebuilt, there are some additional steps to follow. On the new
server, install the mailbox server role on. Next run setup.com in recovery mode:
Setup.com /recoverCMS /CMSName mb100ccr /CMSIPaddress:192.168.1.80
For CCR, reseed the node to bring the node to current state. Once replication is healthy, an
administrative failover will return the original node back as it was before failure.
Failback in Standby Continuous Replication
Once the SCR source is brought back online, the Clustered Mailbox Server can return to the original
cluster. At this point, the two original nodes are clustered without a CMS, and they have the mailbox
role installed.
1. The first step is to dismount the database on the SCR target cluster:
Dismount-Database -Identity ???ca100\SG1Temp\Mailbox Database???
2. Next, use Restore-StorageGroupCopy to prepare the storage group for mounting on the SCR
source cluster. The force parameter is not used because the SCR source is available.
Restore-StorageGroupCopy -Identity ca100\SG1Temp -StandbyMachine mb100
3. The CMS on ca100 should be stopped using Stop-ClusteredMailboxServer :
Stop-ClusteredMailboxServer -Identity mb100ccr -StopReason ???Server Failback???
4.
Pages:
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511