By default, the cmdlet also requires confirmation to continue.
After running the Stop-ClusteredMailboxServer cmdlet, the status shows the state is Offline and
in a Valid state:
[PS] C:\ > Stop-ClusteredMailboxServer -StopReason ???Server Maintenance???
-Identity MB100CCR
Confirm
Are you sure you want to perform this action?
Clustered mailbox server ???MB100CCR??? is stopping with stop reason ???Server
Maintenance???.
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is ???Y???):y
FailedToOffline :
Identity : mb100ccr
State : Offline
IsValid : True
ObjectState : Changed
Replication Status
Another area for measuring cluster health is looking at the replication status. The
Get-StorageGroupCopyStatus cmdlet was covered briefly in the section on seeding. As shown before,
the cmdlet returns a brief snapshot of the current replication state:
Get-StorageGroupCopyStatus
Name SummaryCopySt CopyQueueLeng ReplayQueueL LastInspecte
atus th ength dLogTime
---- ------------- ------------- ------------ -----------
First Storage Group Healthy 5 0 8/17/2007...
Piping the cmdlet to format-list ( fl ) gives more detail about the cluster server health. The key fields
are SummaryCopyStatus , CopyQueueLength , ReplayQueueLength , and LastInspectedLogTime .
Looking at the last log parameters shows the log shipping is current by comparing the log number.
Pages:
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496