• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Backup repository

muskratt

New Pleskian
I noticed the difference between downloading a file via HTTP panel versus what is actually stored in the repository (one tar file versus a number of gz, tgz, and xml several folders deep).

My idea was to use aws-cli to sync this folder to S3 every day but that leads me to wonder how can I restore files back? Keeping the backups synchronized offsite seems a lot easier than other tutorials that include a local FTP repository.

If I put the old backup files into the repository after they're deleted by Plesk, will is automatically show that the backup is available to be restored from in the Backup Manager?
 
Back
Top