- Plesk Onyx for Linux
Scheduled server backup to FTP storage is configured in Plesk in Tools & Settings > Backup Manager > Schedule.
The option Use incremental backup is enabled with keeping the backup files for several weeks.
When the number of full backups exceeds the number set in the field Keep backup files for, the oldest full backup along with its increments is not removed (in other words, the backup rotation does not work properly).
The following line can be found in the file
CONFIG_TEXT: INFO: Dump object guid 'XXX' does not match object guid 'YYY', skip.
Mismatch of the current GUID of the Plesk
admin user (it is stored in the Plesk configuration database) and the GUID in the oldest backup.
The current GUID of the Plesk
admin user is written to each server backup made by Plesk. GUID can be changed due to, for example, the restoration of a backup or a migration.
Backups are rotated by comparing the current GUID and the GUID in the backup. If they do not match, the old backup is excluded from the rotation and not removed.
Connect to the server using SSH.
Find all old backups that are linked to old GUID using the command below:
# grep -r -B11 "does not match object guid" /var/log/plesk/PMM/ | grep BINA | cut -d"'" -f2 | sort -u
Log into Plesk and go to Tools & Settings > Backup Manager.
Delete old backups with timestamps matching with ones found on step 2 (full backups should be deleted with all their increments).