• 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.

What to backup when upgrading to 8.2?

C

Chris-TT

Guest
After using the backup command /plesk_installation_directory/bin/pleskbackup --all <backup file name>
Will this backup be sufficient to restore Plesk to its original state if an update from 8.0 to 8.2 fails?
 
That's a pretty good question.

I've always run a full backup including everything before attempting to upgrade in place.

If the server is remote and you have the available bandwidth you might want to look into rsync over ssh to grab a copy of the server.

It would be a good idea to make sure the server is at run level 1 to that all services are stopped and no users are logged in to the system.

In the event something doesn't work right you will have a copy of the entire system sitting right beside you that you can restore from including Plesk.
 
Back
Top