Figure 13-16
Part III: Working with PowerShell in a Production Environment
382
SCC cluster resources have undergone resource model dependency changes that require a manual
dependency be created and assigned. The physical disk resources are now dependencies of the mailbox
database. These dependencies are not automatically created when the mailbox cluster is installed.
Within our current configuration, it would be best practice to move the physical disk resources out of
Group 0, place them into MB002, and then delete Group 0. This can be accomplished with the
following script:
$Cluster_MBX_Name (reused from Exchange install)
cluster resource ???Disk S:??? /move:$Cluster_MBX_Name
cluster resource ???Disk T:??? /move:$Cluster_MBX_Name
cluster group ???Group 0??? /delete
Once the physical disk resources are in the same group as the Exchange resources, the dependency can
be created. Note: having the physical disk resource in the same resource group is not required, but is a
best practice for managing Exchange cluster resources. The mailbox database needs to be offline for the
next step. Creating the dependencies can be done by using PowerShell to set the Microsoft Exchange
Database Instance dependent upon the disks like this:
$Cluster_MBX_Name (reused from Exchange install)
cluster resource ???First Storage Group/Mailbox Database ($Cluster_MBX_Name)???
/offline
cluster resource ???First Storage Group/Mailbox Database ($Cluster_MBX_Name)???
/adddep: ???Disk $Disk2_Drive??? /adddep: ???Disk $Disk3_Drive???
cluster resource ???First Storage Group/Mailbox Database ($Cluster_MBX_Name)??? /online
In this example the $Cluster_MBX_Name is reused from the install steps, and $Disk2_Drive and
$Disk3_Drive are variables that are created during the drive formatting steps.
Pages:
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529