• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Which mountpoint is checked for backup space calculation?

Martin.B

Plesk Certified Professional
Plesk Certified Professional
In the backup settings there is the option "Start the backup only if your server has the specified amount of free disk space (in megabytes)", which allows to specify a minimum of free disk space to check before a backup.

For which directory this value is checked in case the system has different mountpoints for specific paths?
 
Code:
# grep DUMP_D /etc/psa/psa.conf
DUMP_D /var/lib/psa/dumps

So, it means that mountpoint where directory /var/lib/psa/dumps is located.
 
Strange. Is there some additional value calculated on top?
We had a system, where we set this value to about 20 GB; the drive in question had about 26 GB free, but the backup manager failed with "not enough space". Only be reducing the value we could start the backup process.

Then there is another thing: According to Hard Drive Partitioning for Plesk the backups are stored in /usr/local/psa/tmp/ and /usr/local/psa/PMM/tmp/ during the creation. Shouldn't the free space of these directories be checked then as well?
 
Hi,

Some clarification on this would be helpful.

What about the path specified for DUMP_TMP_D in psa.conf? Surely that's checked for sufficient disk space?
 
DUMP_TMP_D is set to /tmp. This value wasn't customized;this seems to be the default value.
How does this fit to the above information from the official documentation, that during creation the backups are stored in /usr/local/psa/PMM/tmp/?
Is the documentation out of date?
 
The option "Start the backup only if your server has the specified amount of free disk space (in megabytes)" is described incorrectly. Amount of free disk space for backup creation is calculated automatically. The option means amount of disk space that Backup Manager guarantees to keep free after backup creation. There is the request PPPM-9635 to fix the issue.
 
Back
Top