• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Backups Plesk Onyx 17.8.11

Hi,

quick question:
I want to backup my server (453G total, 266G used, 164G free) to an FTP Space.
The backup fails with the message "Not enough free disk space to backup selected objects. At least 236539.92 MBytes free disk space is required.".
I thought as of Plesk Onyx 17.5 and above the Backup does not store all created archives on the local disk prior uploading them to ftp.

Is there a way to use the PLESK backup feature and let it backup to remote FTP Space without double the amount of space required on local disk?
I am using duplicity right now, which just needs the space of one archive (in my case 100 MB) at a time, then upload it and continues with the next archive...

Is something similar possible with PLESK Onyx? Is it possible with Plesk Obsidian?

Thank you for your help.
 
Thanks. I already knew this page.
My problem is that i don‘t know what will happen...
I set Plesk to split backup archives to 2048 MB each. Does it create at first ALL chunks and uploads them then to FTP? Then my server will crash as it has not enought space...
OR does it upload the chunks simultaneously and deletes already uploaded chunks asap? This way the space will not be occupied and it does not crash my server due to less free space...

Please clarify how PLESK FTP Backup process is working in depth. I dont want to crash my production server due to „experiments“.

Thank you
 
It will create the backup files in /var/lib/psa/dumps/ first, and then will create from those an (uncompressed) tar container on the fly while uploading.
You can see them lying around in there when plesk fails to upload the files to ftp, e.g. due to insufficient space on the ftp server. (There is still nothing that would clean those files up automatically.)
Note that plesk calculates the required space without taking compression into account, so if you have e.g. a lot of huge log files (*cough* magento), the backup will really only take up a fraction of that space.
 
Back
Top