This switch causes the cmdlet to accept data loss
caused by missing committed log files.
Putting the steps together, this is an example of making the passive node viable for mounting with the
Restore-StorageGroupCopy cmdlet. To make the passive node active, the database is then mounted
with Mount-Database . If there is data loss or the SCR source is unavailable, the Force parameter is
required to override the warnings.
Restore-StorageGroupCopy -Identity ???First Storage Group???
Mount-Database -Identity ???MB101\First Storage Group\Mailbox Database???
Chapter 12: Working with Continuous Replication
357
One shortcut is the addition of a new script located by default at C:\program files\Microsoft\
Exchange Server\Scripts . The script ??™ s name is GetSCRSources.ps1 . Given an SCR target,
the script will output all of the SCR sources it is a target for. For example, instead of running multiple
Restore-StorageGroupCopy cmdlets:
Restore-StorageGroupCopy -Identity ???mb100CCR\First Storage Group???
-StandbyMachine ca100 -force
Restore-StorageGroupCopy -Identity ???mb100CCR\Second Storage Group???
-StandbyMachine ca100 -force
Restore-StorageGroupCopy -Identity ???mb100CCR\Third Storage Group???
-StandbyMachine ca100 -force
you can use the following:
GetSCRSources | Restore-StorageGroupCopy -StandbyMachine $env:ComputerName
-Force
The steps are the same for a single target SCR or a clustered target SCR.
Pages:
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505