• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Plesk uses local storage for backup (instead of FTP server)

Joopjr

New Pleskian
My server makes full backups every week (and incremental backups daily) to an external FTP server. This FTP server has 12.16 TB free space (the last full backup was 327 GB) and there are no restriction for the FTP user or specific folder. I've tested the FTP username and password and verified that these are correct. There weren't any problem before.


tmp.JPG

The last time that an full backup was required the server used all available (local) disk space and filled the local disk. After some investigation I found that the backup process has filled up the disk space in the /var/log/plesk/PMM/ folder.

The Plesk settings doesn't allow the backup to be stored locally. I've tried enabling "Start the backup only if your server has the sufficient amount of free disk space (this option may significantly increase the backup time) " but this would not prevent the backup (300+ GB) from filling up the /var/log/plesk/PMM/ folder (with 220 GB free space). I've also disable "Save backups in the server storage if the upload to FTP fails".
tmp.JPG

Yesterday 219G was available on my server (more than enough for normal daily operations). If the backup process (more than 300G) tries to store the backup in the /var/log/plesk/PMM/ folder it will fill the disk and prevent functions like Databases, Sessions or Plesk from working. I than have to manually intervene by remove the created files in the /var/log/plesk/PMM/ folder. To prevent the backup proces from bricking my system I've created a cronjob that removes all backup files from /var/log/plesk/PMM/ hourly.
Filesystem Size Used Avail Use% Mounted on
/dev/ploop14118p1 591G 342G 219G 61% /

Why is the backup process trying to use the local storage instead of the FTP server? Due to this behavior I don't have any recent backups available.
 

Attachments

  • backuplog.zip
    4.1 KB · Views: 0
I can't edit my original post anymore.

I of course ment to say "/var/lib/psa/dumps" instead of "/var/log/plesk/PMM/"
 
I didn't know that it is intended behavore to first store the backup locally before uploading it. I've removed a lot of files from my webserver to decrease the full backup from 327 GB to 152 GB. My server now has more than enough space to first store it locally and the daily backup is back up and running.

I still think its weird that the option "Start the backup only if your server has the sufficient amount of free disk space (this option may significantly increase the backup time)" didn't prevent the system from aborting the backup process when the local disk didn't have enough free disk space.
 
@Bitpalast is this also the case for Google Drive ? Because my server went 100% of disk space because it was locally saved. Or is it me that did something wrong ?
 
Back
Top