Failover Option: Reliability, Continuity, Customer Satisfaction
Achieving high availability is critical when it comes to file transfer systems and processes. When your company relies on file transfer to exchange mission-critical files and data, unscheduled downtime is not an option, as it can cause missed service level agreements (SLAs), lost revenue, customer turnover, and limited profitability.
The failover option of WS_FTP Server minimizes the risk of file transfer failure and ensures business continuity related to your file transfers, giving you the ability to:
Provide continuous service to file transfer users
Increase application uptime, reliability, and performance
Align with Microsoft best practices on high availability
Enhance customer satisfaction with systems that are “always on”
Reduce costs and eliminate lost revenue from system downtime
The risk of application failure is higher than you think. Power losses, network outages, data corruption, human error, disk crashes, scheduled server downtime, and many other interruptions put your applications and your whole file based operation at risk.
How Does the Failover Option Work?
WS FTP Server Failover is easy to set up: simply provision a two-node Microsoft cluster or web farm, install and activate your WS FTP Server licenses on each node and then deploy. One node will act as the primary (active) node and the other will act as the secondary (passive) node. All inbound connections, whether FTP/S, SFTP or HTTP/S, will use a shared IP address. In the event the first node fails, the secondary node will automatically assume the failed node’s traffic, authentication duties and logging, thereby ensuring continuous service to file transfer users.
High Availability File Transfer: WS FTP Server with Failover can now be configured to support automatic, unattended failover, enabling your organization to achieve high availability for your file transfer processes. WS FTP Server 7.6.1 and later releases use cluster technology so file servers, databases, and applications perform clean and automated failovers – in fact, it’s the same technology that Microsoft uses in its operating systems for years.
When you deploy WS FTP Server with Microsoft Clustering, you benefit from the failover capabilities of two nodes to run both public and private file sharing services. Microsoft Clustering with WS FTP Server acts as a traffic cop to manage the shared IP address and ensure that external connections are arriving at one node at a time. Store the WS FTP Server configuration in a Microsoft SQL Server database and store the files uploaded to WS FTP Server to a NAS or file share. You may enhance your setup with external authentication using an LDAP server, Active Directory, or another ODBC database.
Another option is to run WS FTP Server using the Web Farm deployment which uses two nodes to run both public-facing and internal WS FTP Server services at all times. Then use Microsoft Network Load Balancing services to ensure that traffic is only directed to one node at a time. Store the WS FTP Server configuration in a Microsoft SQL Server database and store the files uploaded to WS FTP Server to a NAS or file share. You may enhance your setup with external authentication using an LDAP server, Active Directory, or another ODBC database.
My need for quick, secure ﬁle transfer has been instantly met by Ipswitch’s solutions
Kevin Davis, Studio Manager, Positive Images UK
Whitepaper: The Evolution from FTP to Secure File Transfer
Contact a File Transfer Specialist
Discuss how businesses like yours have solved their file transfer challenges with WS_FTP Server.