This example suspends all of the storage groups on server MB100:
Get-StorageGroup -Server mb100 | Suspend-StorageGroupCopy
To check the status, run Get-StorageGroupCopyStatus :
Get-StorageGroupCopyStatus [-Identity < StorageGroupIdParameter > ]
[-DomainController < Fqdn > ] [-DumpsterStatistics < SwitchParameter > ]
[-StandbyMachine < String > ]
Get-StorageGroupCopyStatus -Server < ServerIdParameter > [-DomainController < Fqdn > ]
[-DumpsterStatistics < SwitchParameter > ] [-StandbyMachine < String > ]
The Identity and Server parameters allow the results to be scoped to a particular server or storage
group. This cmdlet is detailed in the next section on monitoring continuous replication.
This example shows the status of the storage group on the mailbox server mb100 that was suspended in
the previous example:
[PS] C:\ > Get-StorageGroupCopyStatus
Name SummaryCopySt CopyQueueLeng ReplayQueueL LastInspecte
atus th ength dLogTime
---- ------------- ------------- ------------ ------------
First Storage Group Suspended 0 0 8/17/2007...
Part III: Working with PowerShell in a Production Environment
348
Once replication has been suspended, the Update-StorageGroupCopy cmdlet does the seeding:
Update-StorageGroupCopy -Identity < StorageGroupIdParameter > [-Confirm
[ < SwitchParameter > ]] [-DataHostNames < String[] > ] [-DeleteExistingFiles
< SwitchParameter > ] [-DomainController < Fqdn > ] [-Force < SwitchParameter > ]
[-ManualResume < SwitchParameter > ] [-StandbyMachine < String > ] [-TargetPath
< LocalLongFullPath > ] [-WhatIf [ < SwitchParameter > ]]
The new string parameter StandbyMachine is used to seed an SCR target.
Pages:
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493