Previous Topic

Next Topic

Book Contents

Book Index

Configuring a Failover Solution Using Microsoft Cluster Services

This guide describes how to implement a failover solution for WS_FTP Server using Microsoft Cluster Services (MSCS) software. This solution is designed to provide continuous service to your file transfer users in the event of a service or node failure.

Microsoft Cluster Services can only provide failover with WS_FTP Server Professional or WS_FTP Server Premium. It cannot be used with WS_FTP Server Basic, the Web Transfer Module, or the Ad Hoc Transfer module.

This failover solution provides one active and one passive node, each running identical configurations of WS_FTP Server. If a server (FTP or SSH) is unavailable on the primary node, or the primary node itself is unavailable, processing switches over to the secondary node. This two-node configuration uses shared resources for the user database, configuration data, and the file system for user directories and log data.

Carefully follow all directions in this document for configuring a failover cluster. Failure to do so maybe result in a nonfunctional or malfunctioning high availability environment. Progress cannot support alternate MSCS configurations.

If you are upgrading from a non-failover WS_FTP Server installation to a failover solution, we recommend that you configure your failover environment with fresh WS_FTP Server installations, then migrate your user and configuration data and file system over to the failover configuration.

In This Section

Architecture

Requirements

Step 1: Configure the MSCS Failover Solution

Step 2: Install WS_FTP on Both Nodes

Step 3: Edit Progress Registry Settings on Both Nodes

Step 4: Configure Progress Services in Microsoft Cluster Services

Step 5: Test the Failover Cluster

See Also

Failover Configuration

Configuring a Failover Solution Using Microsoft Network Load Balancing

Configuring Windows Share Permissions for Failover Clusters

Migrating WS_FTP Server to a Failover Cluster

Replacing a Failed Node in a Failover Cluster