Propper way to upgrade from 8.6 to 9.5.3?

[Intelehost]

I have seen the upgrade procedure from Parallels and I have seen some people talk about the Atomic yum upgrade to 9.5 in the forums. What is the safest way to upgrade from 8.6 with ASL 2.2.6 to 9.5.3 with ASL?

[Highland]

I'd go the yum route with the plesk repo. You can see what's going on and there's less chance of an arcane failure screwing it up, forcing you to start all over.

[mneese77]

I did it wit the autoinstaller vis the command line and it worked flawless.

[Intelehost]

I have the instructions for the plesk command line way, but where do I find out how to do the yum update method? I cannot find it anywhere listed and doing a yum update doesn't show a plesk 9.5 update. I would assume I need to add a repo in addition to the plesk.repo that atomic installed?

[Highland]

To add the plesk repo run

Code: Select all

wget -q -O - http://www.atomicorp.com/installers/plesk |sh

And then

Code: Select all

yum update psa

[Intelehost]

so doing this will upgrade all of the packages necessary and then migrate all of the databases, usernames, passwords, etc... that are already in plesk? or is this a script that runs only if you run the command line upgrade that plesk has people run?

In past upgrades (6.0-7.5) the script runs, upgrades the packages, then migrate all of the user data.

[Highland]

AFAIK all data is in the database and is kept in the upgrade. I've used this path in the past without data loss issues.

Updating psa should update all dependencies. It's important to note that the autoinstaller for Plesk simply downloads the RPMs from the Parallels server and installs them directly. The differences in the two are negligible.

[Intelehost]

Thank you very much for your assistance!! I am going to be processing this update this weekend during a maintenance window and hopefully I don't have any problems (crosses fingers)

[breun]

One difference is that the autoinstaller checks your Plesk key before upgrading and warns you if your key is not good for the new version. But otherwise both methods should work.

[faris]

And definitely do a backup before you start!

If it goes wrong in the middle, it won't be easy to fix

Faris.

[breun]

Luckily Plesk is smart enough to at least dump the psa database to /var/lib/psa/dumps when doing an upgrade.

But yeah, backups. Always make backups (not just when upgrading Plesk).

[Intelehost]

Well the upgrade went well, everything is working but there is one problem...

There are no clients listed in the clients field any more. When you click on domains you can see the client that owns it, click on their details and edit them, but they do not show up in the clients area. instead it says.

0 Clients found (17 total)

Is this just the way it handles new clients and you have to convert them or something? or did something go wrong during the upgrade?

[faris]

Do you have 17 clients?

Make sure there's nothing in the Search field, like the name of a client that doesn't exist.

That would explain why it is showing 0 out of 17 clients.


Faris.