Open the Exchange Management Shell using the
Get-ClusteredMailboxServerStatus . The output of this shows the Clustered Mailbox Server
name, the operational state, the nodes present in the cluster, and a list of any failed resources.
From there, you can take the clustered mailbox offline to perform maintenance by using
Stop-ClusteredMailboxServer . The cmdlet only requires two parameters: the name of the
clustered mailbox (Identity) and the reason that it is being taken offline (StopReason) .
To take your scc2mbx cluster offline you would issue the following:
Stop-ClusteredMailboxServer -Identity MB002 -StopReason ???Firmware patching on SAN???
??‘
??‘
??‘
??‘
Part III: Working with PowerShell in a Production Environment
384
Figure 13 - 17 shows stopping the clustered resource for maintenance on the SAN.
Figure 13-17
This cmdlet takes all of the resources in the MB002 resource group offline. When the Clustered
Mailbox Server is ready to come online, Start-ClusteredMailboxServer would be issued, as shown
in Figure 13 - 18 .
Figure 13-18
Chapter 13: Single Copy Clusters
385
If a manual failover of resources needs to occur, this too can be accomplished through the Exchange
Management Shell by using the Move-ClusteredMailboxServer cmdlet. This cmdlet has three
necessary parameters: the name of the Clustered Mailbox Server (Identity) , the node that will receive
the Exchange resources (TargetMachine) , and the reason for the resource movement
(MoveComment) .
Pages:
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532