Updating a cluster member (Windows only)

Periodically you will need to update software or content that resides on your cluster members. Software updates include new versions or patches of operating system software, web server software, new web applications, ClusterCATS software, or other third-party products.

ClusterCATS lets you put an active cluster member in maintenance mode and then bring it online slowly so you can verify that your changes do not introduce new problems. This section describes how to do this.

To update an existing cluster member with new software or content:

  1. Put the server in maintenance mode using the instructions in "Using maintenance mode (Windows only)".
  2. Make your updates to the inactive server.
  3. Open a web browser on the cluster member and enter the server name associated with the maintenance address defined for the server. For example, serv1.mycompany.com.

    If you configured the maintenance address correctly as described in "ClusterCATS Dynamic IP Addressing (Windows only)", your site appears in the browser.

  4. When you have verified your changes, exit the browser.
  5. Open the ClusterCATS Server Administrator utility on the server by selecting Start > Programs > Macromedia > ClusterCATS Server Administrator.
  6. Click the BT Service Status button.

    The Manage ClusterCATS Services dialog box appears:

    ClusterCATS Service dialog box

  7. Select Running.

    ClusterCATS adds the cluster member back into the cluster.

  8. To initially limit the amount of HTTP traffic sent to the server, return to ClusterCATS Explorer and reconfigure the cluster member's peak load threshold to a low value such as 10%.

    ClusterCATS Explorer

  9. Click OK.
  10. In ClusterCATS Explorer, right-click a cluster member and select Monitor > Load.

    The Server Load monitor appears:

    Server Load dialog box

  11. Observe your cluster member at low usage levels until you are satisfied that your new changes are working properly.
  12. When you are certain that the updates you made have not adversely affected the server's operation, set the peak and gradual redirection load thresholds back to their original values.

Comments