Question Plesk Backup Manager uploads first and deletes afterwards – how to switch this?

[King555]

Server operating system version

Ubuntu 24.04.5 LTS

Plesk version and microupdate number

Plesk Obsidian 18.0.82 Update #2 Web Admin Edition

My websites are backed up daily with incremental backups automatically by Plesk. My storage has 100 GB, the backups are 75 GB in size. One of the backup files (when starting a new incremental cycle) is a little bit over 25 GB. It seems that Plesk uploads the new file first and then deletes the old file. This leads to an error, because the space is not enough (a little bit over 100 GB is needed). So the incremental cycle stops at this point (old file is never deleted, because the new file is never uploaded).

What can I do in this case?

 

[Kaspar]

This is expected behavior and cannot be changed. It's fail safe logic; if the new backup fails (for whatever reason), there the previous backup is still available. Having the previous backup deleted first would leave administrators with no (recent) backup if the new backup fails.

As a workaround however, you can create a custom script to the delete the previous back and run that's script with a cron job just before the the daily backup is scheduled. Below is an example Shell script to get you started. I assumed you store the backup locally on the same server. The script simply deleted yesterday's locally stored backup. If haven't tested this thoroughly, so use with cation.

#!/bin/bash
# Delete yesterday's Plesk server-wide backup via pmm-ras

PMM=/usr/local/psa/admin/bin/pmm-ras
DUMPS=/var/lib/psa/dumps
YESTERDAY=$(date -d "yesterday" +%y%m%d)

for f in "$DUMPS"/backup_info_${YESTERDAY}*.xml; do
    [ -e "$f" ] || continue
    "$PMM" --delete-dump --dump-specification="$(basename "$f")"
done