Upgrade and migration

9.1 Upgrade

Check your license first whether you are eligible to upgrade to the desired version.

Pro edition license allows you to download and use any version released up to 1 or more years after the initial purchase, depending on the support contract you purchased. The exact date can be found in the original license file. If your support contract expired, you can renew it here.

9.1.1 Upgrading using the .exe installer (recommended)

Download the current version or an older version for your platform (64-bit or 32-bit Windows) from the archive.
Backup your configuration folder for extra safety.
Run the installer, use the existing directory for installation path. The installer will update the files and services. When upgrading from v1.x, the services will be reinstalled and you will need to re-enter service user credentials.

9.1.2 Upgrading from version 2.x using the .zip package

Download the current version or an older version for your platform (64-bit or 32-bit Windows) from the archive.
Stop the services - (“Rebex Buru SFTP Server” and “Rebex Buru SFTP Server Web Administration”).
Backup your configuration folder for extra safety.
Unzip over the existing installation
Run burusftp init to check the configuration files
Start the services again.

9.1.3 Upgrading from version 1.x using the .zip package

Full reinstall is recommended: unregister the services (buru uninstall), then install the new version to a different location. You can reuse the old configuration files as they are (with few exceptions) backwards compatible.

9.2 Server migration

Migrating Buru SFTP Server to another machine is a straightforward process.

Perform new installation of the software on the new machine. Do not start the services yet.
Copy all configuration files (except the private keys - more on that below) in the configuration directory from the previous installation to the new one, replacing existing files.

We strongly discourage from copying SSH private keys unless the new machine is a replacement of the old one, with the same IP address and host name, or when it is part of a load balancing cluster.

When using custom SSH private key location, new keys can be generated using burusftp keygen command.
Start the services on the new machine.

9.2.1 Licensing notice

When migrating to a new server, you are allowed to temporarily exceed the number of purchased licenses for a period strictly necessary to perform the migration.

See more on the topic in our licensing FAQ.

9.3 Configuration backup

All configuration files and user database are located in the configuration directory. This directory also contains server’s SSH private keys, unless specified otherwise in the configuration file.

Feedback

Was this page helpful?

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.