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

Issue import backup

dicker

Basic Pleskian
Server operating system version
Ubuntu 22.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.63 Update #4,
Hello, I got a new server because the old server is currently broken.
Now I wanted to restore an external backup.
First of all, I only wanted to restore the backup for one customer.
The server loads a lot of data onto the server. For example, from customers that I didn't want to restore yet.
The /var/lib/psa/dumps alone is currently 700 GB in size.
How can it be that the server does much more than I have configured? I can see all the customers in the /var/lib/psa/dumps/clients even though I haven't wanted to restore them yet.
I tried it last night. This morning a 3 TB disk was full of a backup which was about 1 TB in size.
 
All backup content is packed in a single .tar file. It needs to be downloaded and unpacked to have a separate directory for the one client you want to restore.
 
Okay, so that's normal. The nightly backup was aborted. Nevertheless, more than 1500 GB of storage space was occupied.
I wonder where so much data came from. The defective server only had a total of 1500 GB of disk space. That's strange.
Currently 900 GB have been moved and there is no end to it.
 
Back
Top