Failback
Failback is the process of returning servers to their original state after a failure. It is equally important to
understand and practice as failing over. Each type of replication has its own methods of failback. This
section introduces the following cmdlets that relate to failback:
??‘ Move-ClusteredMailboxServer
??‘ Set-MailboxServer
??‘ Restore-StorageGroupCopy
??‘ Mount-Database
??‘ Dismount-Database
Failback in Local Continuous Replication
The method you use to return to the original configuration for LCR depends on how the LCR failover
was performed. In the scenario where the original paths were kept and the underlying storage was
switched, recovery consists of fixing passive storage and re - enabling LCR.
Part III: Working with PowerShell in a Production Environment
360
If the paths were reconfigured during passive node activation, then the same process can be used to
revert back to the original storage. The original storage is brought back online and is LCR enabled. From
this point, the process is the same as in the original failover.
The steps previously discussed are:
1. Run Dismount-Database on the active database
2. Run Restore-StorageGroupCopy to allow the passive node to mount the database
3. Mount the database on the passive copy
Failback in Cluster Continuous Replication
Failing back from a failure in a CCR is simply performing an administrative failover.
Pages:
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510