how to test upgrading Plesk using a VPS snapshot?

[Maarten]

Because upgrading Plesk servers in the past often caused problems, I want to try it this time in a different way because I want to upgrade from 12.0.18 to 12.5

This is the plan: I want to make a snapshot from a production VPS and and install that snapshot on test VPS. If the upgrade goes without problems, I want to upgrade the production VPS. The problem is, when I start the test VPS with the snapshot, there will be two virtual servers with the same license active. I expect issues with the Odin license servers. Is there a way to prevent this?

 

[bulent]

I think it will be easier to make snapshot of the production VPS, upgrade the production VPS and if something goes wrong, just restore the snapshot.

 

[trialotto]

Because upgrading Plesk servers in the past often caused problems, I want to try it this time in a different way because I want to upgrade from 12.0.18 to 12.5

This is the plan: I want to make a snapshot from a production VPS and and install that snapshot on test VPS. If the upgrade goes without problems, I want to upgrade the production VPS. The problem is, when I start the test VPS with the snapshot, there will be two virtual servers with the same license active. I expect issues with the Odin license servers. Is there a way to prevent this?

@Maartenv

In the cloning options, there is this option to "get rid of the license settings".

The command

plesk bin cloning -u -prepare-public-image true -reset-license true

will reset

the IP Pool, the GUIDs, the password for the admin, the default ssl certificates (other certificates are kept) and the license key.

That is, the command resets all settings that have to be reset when going to a new server.

In the new server, you can then use a new license key, consider for instance the trial license key, that Plesk provides on their download page: http://plesk.com/plesk/download/

It should be as easy as that.

However, if you want to keep the production server intact and online, you should not consider cloning, but perform a simple migration.

I would strongly recommend that you use the "migration based approach", this is less error-prone and more safe for your production environment.

Regards.....

PS The cloning procedure and associated steps are discussed in this part of the official documentation: http://docs.plesk.com/en-US/12.5/de...d-cloning-plesk-in-virtual-environment.70621/