[Resolved] WAPT 1.5.21 to 1.7 but hypervisor change...

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
User avatar
Jonattend
Messages: 43
Registration: March 26, 2018 - 2:45 PM

March 25, 2019 - 3:08 PM

Hello,

To resolve some issues and keep my WAPT system up to date, I'd like to migrate from version 1.5.21 to 1.7.

Theproblemis that version 1.5.21 was installed on our old hypervisor (Proxmox).

Version 1.7 will therefore need to be installed on the new hypervisor (Open Nebula).

Here's how I plan the migration:
- I install WAPT 1.7 on Open Nebula independently of the existing WAPT 1.5 installation
- I import my 70 packages from the 1.5 server to the 1.7 server
- I shut down WAPT 1.5
- I uninstall the WAPT 1.5 clients from the workstations
- I install the WAPT 1.7 client on the workstations (push installation)
- I'm happy.

Given that the packages are signed, copying the packages (via scp) and then scanning them (wapt-scanpackages) from the new server won't work? Could I import certificates and keys from a WAPT 1.5 server?

Thanks ;)
Last edited by Jonattend on 02 Apr 2019 - 11:06, edited 1 time.
WAPT Server version: 1.8.1 on Debian 10
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
High
skoizer
Messages: 54
Registration: June 19, 2018 - 4:45 PM

March 28, 2019 - 10:45

Don't you have a tool in Nebula to extract a VM?
For example, VMware has the converter, which can handle physical to virtual, but also virtual to virtual.

Regards
High
User avatar
Jonattend
Messages: 43
Registration: March 26, 2018 - 2:45 PM

April 2, 2019 - 11:06 AM

Hello,

Apparently, it's possible to export the VM from Proxmox 3 and import it into Open Nebula.

So I've updated my current server to 1.7.x and I'll import it into Open Nebula when the time comes.

Thanks everyone ;)

! Resolved!
WAPT Server version: 1.8.1 on Debian 10
WAPT Agent version: 1.8.1.6756
WAPT Setup version: 1.8.1.6756 on Windows10 v1909
WAPT Deploy version: 1.8.1.6756
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

April 15, 2019 - 8:59 PM

To migrate or back up a WAPT server, you'll find the complete procedure in the documentation:
https://www.wapt.fr/fr/doc/waptserver-b ... r-on-linux
High
Locked

Return to "WAPT Server"


  • To go further with WAPT