Tranquil IT Forum

Hello everyone,

I'm planning to replace my current server (see signature) with a Debian system to better meet Tranquil-it's requirements.
Is there a procedure for this?
If not, how do I migrate all the data, packages, configurations, and certificates so I don't lose anything from the current server? In what order?

Thanks in advance,
Thomas

Hello Thomas,

TomTom wrote: ↑Dec 11, 2019 - 2:39 PM I'm considering replacing my current server (see signature) with a Debian system to better meet Tranquil-it's requirements.
Is there a procedure for this?
If not, how do I migrate all the data, packages, configurations, and certificates so as not to lose anything from the current system? In what order?

We are currently testing on Debian 9, Debian 10 and CentOS 7. We have added builders for Ubuntu 18.04 and 19.04 for the Community version which should be perfectly adequate, but for the Enterprise version we prefer to stick with the versions we test more thoroughly.

In practice, we're not too dependent on the OS because the installer includes a virtual environment with most non-standard Python libraries. However, there can also be details such as the Nginx version, which changes regularly (the Spnego Nginx module for Kerberos authentication must be compiled with the exact same headers and build parameters as the installed version), details about the number of allowed file scriptors, the integrated PostgreSQL version, the OpenSSL ABI, which changes and requires updating the virtual environment, etc. Furthermore, we haven't had many requests for WAPT Enterprise installations on Ubuntu, and the Debian option has always been acceptable.

It is for these reasons that only the three versions mentioned above are officially supported for the Enterprise version.

Simon created some documentation https://www.wapt.fr/fr/doc/waptserver-backup.html To migrate from one server to another, it's best to reuse the same DNS name (or the same IP address if the agent is configured with an IP address). If you have a valid certificate on the server, you'll also need to retrieve it. This should be seamless for client machines.

Sincerely,

Denis

Hello Denis, and thank you for your very detailed reply.

I will therefore proceed with creating a new server based on Debian 10 (might as well start with the most recent version) following the documentation written by Simon.
I will keep the topic open in case I need further assistance and will mark it as resolved as soon as I have successfully migrated to the replacement server.

Thanks again for your help.

Best regards,
Thomas

Hello Thomas,

TomTom wrote: ↑Dec 12, 2019 - 9:02 AM So I'm going to start creating a new server based on Debian 10 (might as well go with the latest version) following the documentation written by Simon.
I'll keep the thread open in case I need to and will mark it as resolved as soon as I've successfully migrated to the replacement server.

Thanks again for your help.

Feel free to note any details that might be implied but could be made clearer. We can add to the documentation if needed.

THANKS,

Denis

Hi Denis,

I just finished my migration.
The steps I followed were:

- Backing up the data from the old server as described in Simon's documentation, namely the WAPT, WAPT-HOST, and WAPTWUA folders, as well as the configuration and certificates
- Backing up the PostgreSQL database
- Shutting down the server
- Configuring Debian 10 with WAPT installed, including the postconf folder (same server name and IP address)
- Restoring the data
- Re-establishing the database (exactly as described in the documentation)
- Restarting the services and testing access, deployment, and adding packages
- Configuring Syncthing for my remote repositories

The feedback is more than positive. No issues to report regarding differences between theory and practice. The documentation is clear and 100% functional.

Congratulations on this software, which continues to impress, and for your flawless support.

Thanks again,
Thomas