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

Question Full Server Backup on Unbuntu 16.04 LTS

Määxx

New Pleskian
Hi friends of Plesk,

i got a few questions, about the full server backup process in Plesk.

First of all, here is my setup and what i have done so far:

1. I scheduled a full server backup job in the plesk webinterface at 3am. So the system wrote many files to /var/lib/psa/dumps.

After i read a lot of documentations from plesk, i realised that this files are only in the "local repository". So if my Server crashs and i want to restore this files on a new server (with new installed plesk), i cant use them cause of the encrypted passwords.

Is this right?

2. So i must do a Fileexport (i try the fullbackup.php script (Plesk Server Backup Script).

If i create a BackupFile with this Syntax:
./fullbackup.php -b -o /var/plesk_fb/test/ -p test1234

The Script writes a small fullbackup_171026, and a big file called server_171026 without a filetype at the end.
So, is this a Backupexport File, and when yes, which one of this 2 files can i upload at the new Server?

The other Methode is, do create an export for the local repository files:
./fullbackup.php -e /var/lib/psa/dumps/backup_info_{ymd}{time}.xml <output_file>

Which one is the right way? Maybe iam doing it to complicated.

Would be awsome if someone got a few tips for me!

Thank you,
Maximilian
 
Back
Top