Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Serv-U - Knowledgebase Articles > Serv-U High Availability

Serv-U High Availability

Updated March 11th, 2016

High Availability and Serv-U

  1. Here are some essential documents on high availability:
  2. Document on Linux and Serv-U.
  3. Architecture Admin Guide.

Here is information on High Availability regarding importing users and general setup good practice.

Stop Serv-U

  1. Export local users on your existing production to CSV file,
    • This can take a few minutes if you have MANY user accounts.
  2. Edit users in CSV for changes to network paths,
    1. Home directory.
    2. Dir access rules.
    3. Anything else they're customizing that involves a path to a local file that is no longer local?
    4. Pay special attention to formatting of these paths as they use double backslashes.
      • ** For example, the value "D:\\MM\\files" would be become "\\\\\\share\\files".
  3. Import CSV users into ODBC users on new Serv-U,
    • This can take a few minutes if you have MANY user accounts.
  4. Add limit under Server Limits & Settings | Limits | Connection,
    • Allow X-Forwarded-For to change HTTP connection IP addresses ==> Yes
    • If this isn't done, log files for Serv-U will always show the load balancer as the connecting IP
  5. Adjust logging settings for domain if you want log files on network location as well,
    • Ensure different Serv-U's use unique file names - the info is not collated into one file.
  6. Change system service to use an account other than LocalService that will have full access to the network paths desired.
  7. Enable sticky sessions in load balancer,
    • If this isn't done, clients may connect to the other Serv-U when establishing a data connection.
  8. Copy over Archive file from production server to new ones to copy all settings over.

Start Serv-U


High Availability Things to Know:

  • Settings changes made on one Serv-U instance must be manually performed on others as well
  • Changes do not propagate between servers automatically.
Last modified