• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Big upgrade path suggestions

G

Gorgon@

Guest
Hi folks,

Just looking for a little advice. We currently have a RHEL3 server running Plesk 7.5.4. We want to get this to a RHEL4 (or maybe RHEL5 now?) and Plesk 8.1.1. We're debating 1 or 2 paths:

1) Upgrade the OS and the Plesk on current hardware. The pro here would be no moving of client data around. The con is that it would be difficult for us to test this first and thus would have to have a fallback plan along each step in case it doesn't work.

2) Build out new server with RHEL4/5 and Plesk 8.1.1 and migrate the customer data from the old 7.5.4 server using the migration tool.

I'm curious on what experience others have had with either method. Any input is appreciated.

Thanks,
mikeS
 
We recently migrated from Plesk 5.0 to Plesk 8.0 (and then upgraded to 8.1) so I will give you my input.

The path with the least amount of headaches is going to be the new server with Plesk 8.1 installed, and then migrating the accounts over all at once.

The migration process works well, and you can make sure the new server is sorted out before you move anything over to it.

In place upgrades are troublesome and can lead to potential headaches that are hard to track down.

The only downside to this process is that there is inevitably something you have missed (perl modules got us). So just make sure you identify any problem sites/clients that need special attention and test them thoroughly once you have migrated the accounts over.

Good luck.
 
Thank you folks. I tend to lean towards the clean rebuilds myself. :) I also discovered the RHEL5 is not supported yet too. Oh well, guess that upgrade will have to come later.

Good call on checking that all necessary perl modules and stuff like that are installed. :)

Thanks again for the input.

mikeS
 
Back
Top