• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Backup creation to remote FTP storage fails due to local disk space check

Blixary

New Pleskian
Title: Backup creation to remote FTP storage fails due to local disk space check

Hello,

I encountered an issue with the Plesk Backup Manager that appears to be incorrect behavior.

Environment​

  • Plesk Obsidian
  • Backup destination: Remote FTP(S) storage
  • Remote connection test: Successful

Problem Description​

I configured a remote FTP(S) server as backup storage in the Backup Manager. The connection test works without any issues.

When I manually start a backup and explicitly select the option to store the backup on the remote FTP(S) server, the backup process starts for a few seconds and then immediately aborts.

The downloaded log file contains the following error message:
"There is not enough disk space at /var/lib/psa/dumps to backup creation. At least 58.00 GB free space is required (57.43 GB is available)"

Expected Behavior​

Since the backup target is the remote FTP(S) storage, the backup process should either:
  • stream the backup directly to the remote storage, or
  • require only minimal temporary local disk space.
The process should not fail because the local /var/lib/psa/dumps directory lacks enough free space when the actual destination is remote storage with sufficient available capacity.

Actual Behavior​

Plesk still performs a local free-space check against /var/lib/psa/dumps and aborts the backup creation, even though the backup is configured to be stored remotely.

​

How can I fix this? Thanks in advance.
 
Backups cannot be written to an external FTP repository directly. Some sort of temporary files are required. They are stored in the path DUMP_TMP_D defined in /etc/psa/psa.conf. Also, a local copy of the data that needs to be packed and uploaded plus a few XML data files on the backup of the server, the subscriptions, clients, domains are stored in the path DUMP_D, also defined in /etc/psa/psa.conf. More information can be found in https://support.plesk.com/hc/en-us/...tion-for-Plesk-backup-files-on-a-Linux-server
 
Back
Top