DESKTOP

Windows Server 2003 : Server Clustering (part 4) - Using the Cluster Application Wizard, Configuring Failover and Failback

8/24/2012 9:16:24 PM

8. Using the Cluster Application Wizard

You can use the Cluster Application Wizard to prepare your cluster for introducing an application. Part of the wizard's job is to create a virtual server for the application: essentially, virtual servers are simple ways to address a combination of resources for easy management. Virtual servers consist of a distinct resource group, a non-DHCP IP address, and a network name, as well as any other resources required by whatever application you want to cluster.

Once the virtual server has been created, you configure the path and directory of the application you want to cluster and then set advanced properties and failover/failback policies for the entire virtual server, automating the failure recovery process.

Let's step through the Cluster Application Wizard and configure our own fault-tolerant application, Notepad:

  1. From within the Cluster Administrator console, select Configure Application from the File menu. The Cluster Application Wizard will appear. Click Next off of the introductory screen.

  2. The Select or Create a Virtual Server page appears next, as shown in Figure 15. You can choose to create a new virtual server or select an existing one from the drop-down list box. Click Next to continue.

    Figure 15. The Select or Create a Virtual Server screen
  3. The Resource Group for the Virtual Server screen appears next, as shown in Figure 16. Identify the resource group by either creating a new one or selecting an existing one that will handle the resources needed by your application. In this example, we'll continue to use an existing one—if you elect to create a new one, the process is much like that described in the previous section. Click Next to continue.

    Figure 16. The Resource Group for the Virtual Server screen
  4. The Resource Group Name screen appears next, as shown in Figure 17. This gives you an opportunity to verify the resource group selection you made on the previous screen. Confirm the information, make any necessary changes, and then click Next to continue.

    Figure 17. The Resource Group Name screen
  5. The Virtual Server Access Information screen appears next, as shown in Figure 18. Here you specify a dedicated, static IP address for communicating with the new virtual server. Enter the name and IP address you like, and then click Next.

    Figure 18. The Virtual Server Access Information screen
  6. The Advanced Properties for the New Virtual Server screen appears next, as shown in Figure 19. On this screen, you can choose any element of the virtual server you've just created and modify its advanced properties. Select the item, and then click the Advanced Properties button to modify the properties. Otherwise, click Next to continue.

    Figure 19. The Advanced Properties for the New Virtual Server screen
  7. The Create Application Cluster Resource screen appears next, as shown in Figure 20. Windows needs to create a cluster resource to manage the fault tolerance of the resources contained in your new virtual server. Go ahead and allow Windows to create a cluster resource now by clicking the first option and then clicking Next.

    Figure 20. The Create Application Cluster Resource screen
  8. The Application Resource Type screen appears next, as shown in Figure 21. Specify the resource type for your new application, and then click Next. For this example, I'll just configure a Generic Application type resource.

    Figure 21. The Application Resource Type screen
  9. The Application Resource Name and Description page appears next, as depicted in Figure 22. Here, name the new resource and enter a friendly description, which is used only for administrative purposes. Click the Advanced Properties button to configure policies on application restart, dependencies on resources, and possible owners of the application. Click Next when you've finished.

  10. The Generic Application Parameters screen appears next, as shown in Figure 23. Enter the command that executes the application and the path in which the application resides. Choose whether the application can be seen at the cluster console using the Allow application to interact with desktop screen, and then click Next.

    Figure 22. The Application Resource Name and Description screen
    Figure 23. The Generic Application Parameters screen
  11. The Registry Replication screen appears next, as shown in Figure 24. Enter any registry keys that are required by the application. These will be moved to the applicable active node automatically by the Cluster Service in Windows. Click Next when you've finished.

  12. The Completing the Cluster Application Wizard appears next. Confirm your choices on this screen, and then click Finish.

Figure 24. The Registry Replication screen

The new virtual server and cluster resource then is created and is shown within the Cluster Administrator console. When you bring the group online, you'll notice that a Notepad window is opened in the background. If you close Notepad, it will automatically relaunch itself. This is the power of the cluster, demonstrated in a simple form, of course.

9. Configuring Failover and Failback

Once you have resources, groups, virtual servers, and applications configured in your cluster, you need to specify failover and failback policies so that upon a failure your cluster behaves as you want it to behave. In this section, I'll detail how to configure each type of policy.

Failover is configured automatically on a cluster with two or more nodes. Failback is not.


9.1. Failover

You can configure a failover policy by right-clicking any group within the Cluster Administrator console and selecting Properties from the pop-up context menu. Once the properties sheet appears, navigate to the Failover tab. A sample Failover tab for a group is shown in Figure 25.

Figure 25. Configuring a failover policy

On this tab, specify the threshold, which is the maximum number of times this particular group is allowed to fail over during a specific timeframe, as specified by the period option. If there are more failovers than specified in the threshold value, the group enters a failed state and the clustering service won't attempt to bring it back to life.

Click OK when you've entered an appropriate value.

9.2. Failback

You also can configure a failback policy by right-clicking any group within the Cluster Administrator console and selecting Properties from the menu. Navigate to the Failback tab, a sample of which is shown in Figure 26.

Figure 26. Configuring a failback policy

You can set the option to prevent failback, meaning that when a failed node that originally hosted the group returns to normal functionality, the migrated group will not return and will remain on its new host. If you decide to allow failback, you can choose how quickly the group will return to its original host—either immediately, or between a certain period of time.

Other  
  •  Windows XP : Participating in Internet Newsgroups - Downloading Messages
  •  Windows XP : Participating in Internet Newsgroups - Working with Newsgroups in Outlook Express
  •  Analysis Ultrabooks
  •  Farewell To Pixels : Retina MacBook Pro brings the new age of dot-free displays to OS X
  •  Computing – OS
  •  Windows Server 2003 : Protecting Network Communications with Internet Protocol Security - IPSec Basics (part 2) - Differences Between AH and ESP, Process and Procedure
  •  Windows Server 2003 : Protecting Network Communications with Internet Protocol Security - IPSec Basics (part 1) - Security Advantages of IPSec
  •  Windows Vista : Communicating with Windows Mail - Handling Incoming Messages (part 2) - Customizing the Message Columns, Setting Read Options
  •  Windows Vista : Communicating with Windows Mail - Handling Incoming Messages (part 1) - Processing Messages
  •  Windows Vista : Communicating with Windows Mail - Setting Up Mail Accounts
  •  Ultra-X P.H.D PCI2 - Solve PC Problems Easily (Part 2)
  •  Ultra-X P.H.D PCI2 - Solve PC Problems Easily (Part 1)
  •  Confessions Of An Internet Troll (Part 2)
  •  Confessions Of An Internet Troll (Part 1)
  •  Windows Vista or Windows Server 2008 : Architecture of Group Policy - Domain Controller Selection During GPO Management
  •  Windows Vista or Windows Server 2008 : Architecture of Group Policy - Group Policy Dependencies
  •  Retina MacBook Pro
  •  Suitcase Fusion 4
  •  Canon PIXMA MX895
  •  Samsung Series 5 Ultra
  •  
    Top 10
    Canon PowerShot G15 12MP Digital Camera With 3-Inch LCD
    3D Printed Guns
    Dual-channel DDR3 RAM (Part 4)
    Dual-channel DDR3 RAM (Part 3)
    Dual-channel DDR3 RAM (Part 2)
    Dual-channel DDR3 RAM (Part 1)
    In-Win G7 Black Windowed Mid-Tower Case
    Starcraft II Gaming Mouse & Marauder Starcarft II Gaming Keyboard
    The Computers That Came In From The Cold (Part 2)
    Joystick Junkies - The Sim Hardware Roundup (Part 3) : Thrustmaster HOTAS Warthog, Thrustemaster TH8 RS Gear Shifter, ButtKicker Gamer 2
    Most View
    AV & CI: App You Like It (Part 1)
    Speaker Packages Awards – Q1 2013 (Part 2)
    Sony STR-DN1030 – Home Cinema Amplifier
    Kobo Aura HD – E-Reader For The Most Eager Readers And Books Lovers (Part 2)
    TaskPaper - Completely Rethinks Lists
    Cooler Master CM Storm Scout 2 Ghost White
    Evercool Silent Shark CPU Cooler Review (Part 1)
    The Latest Gadgets, Gizmos And Geek Toys
    SQL Server : Reusing T-SQL Code - The Dangers of Copy-and-Paste
    10 Essential Hardware Accessories (Part 1)