• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Disaster recovery planning

W

wsani

Guest
I'm trying to understand what it would take to recover an existing Plesk server in case of an emergency. Are we able to restore the PSA database on a new server and get it running as it were on a new OS?

How are you guys doing this? Suggestions?
 
You need more than just the PSA database. Websites, mail, client databases, etc. are not stored in the PSA database. You could use Plesk's backup and restore utilities. You need to do a fresh OS and Plesk install if you want to restore this backup.

If you want to be able to do quick bare metal restores, then you could maybe use something like mkCDrec. You probably want to combine a bare metal restore tool with a full system backup tool (BackupPC is nice) so you can restore a recent backup after the bare metal restore.
 
Back
Top