Backing Up or Moving Serv-U Settings - KB Article #1047Related Articles -- 2104
Backing Up Serv-U Settings
In accordance with the new requirements of Windows 7, 8, Server 2008 R2, and Server 2012, Serv-U now stores critical settings files in the "ProgramData" folder. This means Serv-U settings may be in one of two different locations depending on the version of Windows you have installed. The files that must be backed up are the following:
- Serv-U.Archive file
- Users folder
- Serv-UID.txt file
These files are either stored in:
- Windows Vista/7/8, Server 2008/2012 - C:\ProgramData\RhinoSoft\Serv-U (Folder is Hidden in Windows by default)
- Windows 2000/XP, Server 2000/2003 - C:\Program Files\RhinoSoft\Serv-U
- Linux - /usr/local/Serv-U
If you are using FTPS or SFTP you will need to back up additional key and cert files along with the above basic configuration files.
- Any file ending with .crt
- Any file ending with .pem
- Any file ending with .key
The Serv-UID.txt file contains your license key information. This file is created at the time when you enter your license ID in the Serv-U Management Console, and it will be stored in your installation directory, but the other files may be located elsewhere on your system. The best way to verify whether you are using these files is to check the Domain Limits & Settings | Encryption (for each domain) and Server Limits & Settings | Encryption tab to see where those files are stored. (It's a best practice to store these all either in one directory for the server, or one directory per domain so they are easy to back up.)
Backing Up Serv-U Gateway Files
Before upgrading your Serv-U Gateway, certain data must be backed up. The data you must back up is stored in either of the following default data directories:
- Windows Vista/7/8, Server 2008/2012 - C:\ProgramData\RhinoSoft\Serv-U Gateway
- Windows 2000/XP, Server 2000/2003 - C:\Program Files\RhinoSoft\Serv-U Gateway
- Linux - /usr/local/Serv-U Gateway
The following files must be backed up:
Accept-Public-IP-CIDRs.txt file is in the Serv-U Gateway installation directory, which may or may not be the same as the data directory. In the case of Windows Vista/7/8 and Windows Server 2008/2012, the installation directory is different from the data directory.
Backing Up the File Share Database
To migrate the file share database to a new or upgraded Serv-U instance, copy one the following folders from the old server to the new server (depending on your operating system version).
Note: Before copying the folder, stop your Serv-U instance.
- C:\Program Files\RhinoSoft\Serv-U\Shares
Backing Up the Contents of the File Share Repository
To migrate the contents of file sharing repository to a new or upgraded Serv-U instance, perform the following steps:
- In the Serv-U Management Console, click Domain > Limits & Settings > File Sharing.
- Note the location of the File Sharing Repository, and back up the contents of that folder.
- After the migration of Serv-U is complete, create the new file sharing repository at the same location on the new system.
Backing Up and Restoring Serv-U Configuration Files
Serv-U configurations can be backed up or restored by copying the Serv-U.Archive file, Users folder, and any auxiliary files as listed above either to a folder (for backup) or to a new Serv-U installation (for a server restoration or migration). Copying the files from the source server can be done while the Serv-U server is live with no data integrity issues. However, when restoring the configuration files to a new server (or rebuilding an existing server) the Serv-U service must be stopped while the files are imported. To stop the Serv-U service, right click on the Serv-U Tray and choose "Stop Serv-U".
This RhinoSoft utility will back up most of Serv-U's settings and can be configured to back up SSH keys, SSL certificates and other important elements as well.
Migrating Serv-U Configuration
Migrating Serv-U from an old server to a new server at a basic level requires only the steps in the "Backing Up and Restoring Serv-U Configuration Files" section - copying the files from the old server to the new server, and restoring the files to a Serv-U instance that is stopped so that the configuration files are then used by Serv-U when it starts up.
Note: The same steps apply if you are migrating Serv-U from one operating system to another.
There are also some additional considerations when migrating from an old server to a new one.
In regards to versioning, configuration files from Serv-U 188.8.131.52 can be migrated directly to servers running Serv-U 12, which can load the new files directly and will update them automatically with any additional fields used to accomodate new features - in this case, no further work is needed. Administrators migrating from Serv-U 6 or older to Serv-U 184.108.40.206 or newer will need to reference KB Article 1154 for their users and settings to be updated for use with the new Serv-U release (no settings or users will be lost).
Many administrators will need to perform stage testing with the new Serv-U server before deploying it to production. Serv-U's installer comes with a 30-day trial that will be sufficient for most stage-to-production tests. RhinoSoft can provide a further 30-day trial extension if needed for further testing. To obtain a trial extension, contact RhinoSoft Technical Support.