• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Best practice for updates

Pippa

New Pleskian
Complete newbie. I have inherited a website to maintain that is hosted on plesk cloud server. There are a lot of updates due on Plesk and I'm not sure of the best way to go ahead. Should I be doing these in a particular order? Ionos offer the option of taking a snapshop of the server before, would this be sufficient to roll back if anything goes wrong

Upgrade to plesk Obsidian 18.0.30 is available
Updates for 291 packages are available


any advice would be appreciated and hoping I've posted in the right place!
 
Snapshot: Normally this stores a full copy of a server including everything. But you need to ask Ionos if that is the case with their snapshots. If so, then the whole system can be restored safely if something goes wrong.

Updates for 291 packages: This sounds like the operating system subversion updates. If the initial installation of the OS was correctly done and Plesk is compatible with it, there should not be an issue when upgrading the packages. However, many users here still experienced issues with all kinds of operating system package updates for several reasons. You never know before you have actually tried it.

Upgrade to Plesk Obisidan 18.0.30: If you already have a Plesk Obsidian you can normally do the upgrade without any issues. If you are still on Plesk Onyx I'd make sure to have a fully functioning snapshot of the system before you try that and that you have updated all the os system packages before you try he upgrade to Obsidian.
 
Hi Peter,
Thank you for taking the time to reply, I've just checked and it is still on Onyx. So I will contact Ionos to confirm that the snapshot will save everything before I begin.
Update packages first, then do the upgrade to O‬bsidian.
Should the package updates be done one at a time or should I just run them?
I've been very much chucked in at the deep end here!

CentOS Linux 7.4.1708 (Core)
Plesk Onyx
Version 17.8.11 Update #91, last updated on Sept 28, 2020 06:35 PM
 
Normally on CentOS it should not be a problem to run the whole bunch of updates all at the same time. Problems can come up when you are not using the original EPEL repositories, but have a mixture of different sources for different software, because then dependency issues might occur that cannot easily be fixed. If you have a snapshot, give it a try. If you have a cloud instance, you might as well open a second instance and try to restore the snapshot to the other instance to make sure that the backup really works before you proceed with the upgrades.

In case you feel unsure about the upgrade to Obisidan, Plesk offers a paid service (i think it's about 150 Euros) to do the Plesk upgrade for you. But I don't think they do the OS updates.
 
Back
Top