Article ID: 118514, created on Nov 8, 2013, last review on Jan 15, 2015

  • Applies to:
  • Plesk

Before the upgrade

1) My system fits all the requirements

2) My panel and all services are up and running, I see no errors on Home page before upgrade

3) My sites are up before upgrade

4) I know that upgrade does not fix existing issues – I ask to fix them before updating

5) I create full system backup before upgrade

6) I have sufficient disk space to start upgrade

7) All my antiviruses are off before upgrade

8) On Linux I disable 3rd-party repositories before upgrade

9) I download the latest Autoinstaller of the latest Plesk version available on Parallels site to start upgrade

10) My user in the system has administrative privileges

Planning the upgrade

11) I have a license for new version of my panel

12) I schedule maintenance window for my users before upgrade planning it out of business time (if possible)

13) I watch YouTube upgrade video tutorials before update:

Doing the upgrade

14) I do believe pre-upgrade checker does not lie

15) I do not blindly “say” yes to all OS/installer requests during upgrade

16) I do not cancel upgrade (even if I think it hanged)

17) I do not try to launch second upgrade simultaneously (even if I really want to)

18) I do not run upgrade again if it initially failed

19) I do not fix upgrade issues on my own, but contact ISV or Parallels support

20) I upgrade my panel from the latest update within a major version installing all available micro updates

Search Words

update to plesk 12

MSI: Error! An installation for Parallels Panel Service Node is currently suspended. You must undo the changes made by that installation to continue. Do you want to undo those changes? upgrading Perl modules...


plesk upgrades

upgrade to plesk 12

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF