top of page

How to Configure High-Availability Clustering in Globalscape EFT 8.3.4: A Step-by-Step Guide

  • Aug 6
  • 4 min read

Ensuring your file transfer infrastructure stays online around the clock is essential for any organisation that depends on secure, reliable data movement. Globalscape EFT High Availability Clustering provides a resilient architecture that minimizes downtime by automatically transferring operations to a secondary node if the primary server becomes unavailable. In this guide, we'll walk you through the step-by-step process of configuring High Availability Clustering in Globalscape EFT 8.3.4, based on a successful implementation completed for our client, Global E-Director.


What Is High Availability Clustering in Globalscape EFT?


Globalscape EFT High Availability is a built-in feature that allows two EFT server nodes to operate in an active-passive cluster. When the active node encounters a failure, the passive node takes over with minimal disruption to running transfers and connected clients.


Key benefits of High Availability Clustering include:


  • Reduced downtime during hardware or software failures

  • Automatic failover without manual intervention

  • Shared configuration across both nodes for consistency

  • Continued processing of in-flight file transfers where possible


Prerequisites Before You Begin


Before configuring Globalscape EFT 8.3.4 High Availability Clustering , confirm that the following requirements are in place:


  • Two Windows Server instances on the same domain or workgroup

  • Globalscape EFT 8.3.4 installed on both nodes

  • A shared storage location accessible by both nodes (such as a UNC path or SAN volume)

  • A valid EFT High Availability licence applied to both nodes

  • Static IP addresses assigned to each node

  • A virtual IP address or DNS alias that clients will connect to

  • Administrator-level access on both servers

  • Firewall rules allowing cluster heartbeat and EFT service traffic between nodes


Meeting every prerequisite before you start will prevent the most common configuration errors.


Step-by-Step Configuration Guide


Step 1: Prepare Shared Storage


Both nodes must read from and write to the same data directory. Configure a shared folder or mount point that both servers can access with full permissions. This location will hold the EFT configuration database, site data, and transfer logs.


  • Verify that both nodes can reach the shared path before proceeding

  • Ensure the service account running EFT has read/write/modify rights to the shared location

  • Test connectivity from each node independently


Step 2: Install and Licence EFT on Both Nodes


Install Globalscape EFT 8.3.4 on each server using the standard installation wizard. After installation, apply the High Availability licence on both nodes through the EFT administration interface.


  • Do not configure any sites or settings on the secondary node at this stage

  • Confirm the HA licence is active and shows the correct node count


Step 3: Configure the Primary Node


On the primary node, open the EFT administration console and complete your full server configuration sites, users, event rules, and security settings. Point the EFT data directory to the shared storage path configured in Step 1.


  • Navigate to Server > High Availability in the administration console

  • Select Enable High Availability 

  • Set the role of this server to Primary (Active) 

  • Enter the virtual IP address or DNS hostname clients will use

  • Set the heartbeat interval and failover timeout to values appropriate for your environment


Step 4: Configure the Secondary Node


On the secondary server, open the EFT administration console and navigate to Server > High Availability.


  • Select Enable High Availability 

  • Set the role of this server to Secondary (Passive) 

  • Enter the IP address of the primary node so the two servers can communicate

  • Point the EFT data directory to the same shared storage path used by the primary

  • Save and apply settings


The secondary node will synchronise its configuration from shared storage. Do not manually configure sites on the secondary node; it inherits everything from the shared path.


Step 5: Test Heartbeat Communication


With both nodes configured, verify that the heartbeat between them is active. In the EFT administration console on the primary node, the High Availability status panel should show the secondary node as Connected.


  • If the secondary shows as unreachable, check firewall rules and node IP settings

  • Review the EFT log files on both servers for any HA-related errors

  • Confirm that both nodes agree on the current active role


Step 6: Perform a Failover Test


Before going live, test that failover works as expected. A controlled failover test is the only reliable way to confirm your Globalscape EFT 8.3.4 High Availability Clustering setup is production-ready.


  1. Initiate a manual failover from the primary node's HA settings panel

  2. Confirm that the secondary node assumes the active role

  3. Connect a test client to the virtual IP address and verify that transfers complete successfully

  4. Fail back to the original primary node and confirm normal operation resumes


Common Configuration Issues and How to Resolve Them


Issue

Likely Cause

Recommended Fix

Secondary node shows as disconnected

Firewall blocking heartbeat port

Open the required port between both node IPs

Failover does not trigger automatically

Timeout value set too high

Reduce the failover timeout in HA settings

Configuration changes not visible on secondary

Shared storage permissions issue

Re-verify service account permissions on the shared path

Licence error after failover

HA licence not applied to secondary

Apply the HA licence key on the secondary node


Best Practices for Maintaining High Availability Clustering


Once your Globalscape EFT High Availability cluster is running, follow these practices to keep it healthy:


  • Schedule regular failover tests at least quarterly to confirm the cluster behaves as expected

  • Monitor the heartbeat status daily through the administration console or an external monitoring tool

  • Apply EFT updates to the secondary node first, then fail over and update the primary

  • Keep shared storage healthy by monitoring disk space and running regular integrity checks

  • Document your HA configuration, including IP addresses and timeout values, for your IT team

  • Review EFT log files regularly for any warnings related to High Availability Clustering


     

Is Your EFT Cluster Ready for Production?


Configuring Globalscape EFT 8.3.4 High Availability Clustering is a straightforward process when each step is followed carefully. A properly configured cluster protects your file transfer operations from unplanned downtime and gives your team confidence that critical data flows will continue even when hardware or software issues arise.


If you are planning to deploy or expand your EFT environment, reviewing your Globalscape EFT High Availability configuration as part of a broader infrastructure audit is a sound investment. A resilient file transfer platform is the foundation of dependable business operations.


Need help reviewing or implementing your High Availability Clustering setup? Reach out to the Global E-Director team for expert guidance tailored to your environment.


 
 
bottom of page