• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Best Upgrade path?

H

Helter

Guest
Ok, here's the situation that I've let myself get into.

I'm running Plesk 7.5 Reloaded, on a Redhat 7.3 box... I know, bad Helter.
I'd like to upgrade Plesk, and I'd like to upgrade my OS, but I'm in a bit of a bind as far as how to accomplish it. My first intent was to upgrade Plesk to a new version, then back it up, install a fresh os, and reinstall/reload plesk.
Then I found that you had discontinued support for RH7.3.
So my question is, what is the best upgrade path to get from RH7.3 with Plesk 7.5 reloaded, to say, CentOS5, with Plesk 8.4.
Should I backup Plesk, Install 7.5 on my CentOS install, then upgrade plesk? Is there a way to go directly from a 7.5 backup to an 8.4 install?
 
Can you get a second server? Id set up a C5 plesk box and then use the migration manager to copy the data from the old system in parallel.
 
Can you get a second server? Id set up a C5 plesk box and then use the migration manager to copy the data from the old system in parallel.

I absolutely can. Will the migration manager copy across different versions? Or will I still need to go 7.5 to 7.5 then upgrade? Is the migration manager stable/reliable?
 
Just looked it up. Thanks for the tip! this is going to save me *tons* of time.
 
Back
Top