It's time to verify that our Exchange 2007 clustered mailbox server is working as expected. Let's first open the
Cluster Administrator and check whether the respective Exchange Resources have been created. If you take a look at Figure 8.88, it looks good; we have both nodes listed in the left pane and all Exchange resources have been created and are currently owned by EDFS09.
If you look closer at Figure 8.88, though, you can see that two cluster groups exist: one containing the cluster IP, name, and the shared disks, and one created by Exchange 2007 setup containing the Exchange Information Store, System Attendant, Storage Groups, and Database instances as well as the Exchange virtual server IP address and network name. We recommend that you move all shared resources from the cluster group to the MailboxServer2 group (or whatever you called it); otherwise, you will have problems mounting the database when moving the clustered mailbox server from one node to the other (which we'll do in just a moment).
In addition, if you have assigned a shared disk specifically for the transaction log files, remember to change the path for these files. You can do so by selecting the respective storage group under Server Configuration -> Mailbox node in the EMC, then click the Move Storage Group link in the Action pane. In the Move Storage Group Wizard, change the path for the log files to the L: drive or whatever drive you assigned them.
Now try to open the EMS by clicking Start -> All Programs -> Microsoft Exchange Server 2007 -> Exchange Management Shell on one of the nodes, then type Get-ClusteredMailboxServerStatus. As you can see in Figure 8.89, the status of the clustered mailbox server is Online, and EDFS09 is currently the active node. This just keeps getting better and better, doesn't it?
Now that we have verified that the clustered mailbox server is online, let's try to move the Exchange resources from node one to node two using the Move-ClusteredMaitboxServer CMDlet. In the test environment we're using, we do so by issuing the command Move-ClusteredMailbox Server -Identity:Mailbox Server2 -TargetMachine:EDFS10 -MoveComment:"Testing the Move Clustered Mailbox functionality!"
You're then asked to confirm this action. Type Yes, then press Enter (see Figure 8.90). After a while the clustered mailbox resources will be moved to the second node.
|Warning: Although it's possible to move the cluster resource group between the nodes using the Cluster Administrator console, you should always do so (just as is the case with CCR-based clusters) using the Move-ClusteredMailboxServer CMDlet because the Move Group task in the Cluster Administrator console isn't Exchange 2007 aware.|
Let's also take a look at the clustered mailbox server in the EMC. To do so, click Start -> All Programs -> Microsoft Exchange Server 2007 -> Exchange Management Console, then drill down to Server Configuration -> Mailbox. Notice that the clustered mailbox server we named MailboxServer is listed in the Results pane and that it's recognized as a cluster server (see Figure 8.91).Also notice that the Mailbox Database for this server points to the S: drive, exactly as we specified during the installation of the Active Clustered Mailbox role.
Managing an Exchange 2007 Single Copy Cluster-based setup
Part 1: A basic Single Copy Cluster setup in Exchange 2007
Part 2: Configuring Single Copy Cluster (SCC) nodes and shared cluster disks
Part 3: Creating a Windows Server 2003 cluster for an Exchange SCC setup
Part 4: Installing Exchange Server 2007 clustered mailbox roles on SCC nodes
Part 5: Verify Exchange 2007 clustered mailbox server functionality
Part 6: Exchange 2007 Single Copy Cluster-based setup review
|This chapter excerpt from How to Cheat at Configuring Exchange Server 2007: Including Outlook Web, Mobile, and Voice Access, by Henrik Walther, is printed with permission from Syngress, a division of Elsevier, Copyright 2007.
Click here for the chapter download.