Issue Backup cycle wrong since 18.0.65 (too much full backups)

[King555]

Server operating system version

Ubuntu 18.04.6 LTS x64 (ELS)

Plesk version and microupdate number

Plesk Obsidian 18.0.65 Web Admin Edition

I automatically backup my domains every day via incremental backups and do a full backup every week. The backups are stored for 2 weeks. So every domain has 2 full backups at all times and several incremental backups.

Yesterday I updated Plesk to 18.0.65 (from the version which was the current before) and now there seems to be something wrong with the backup routine.

The full backups were done on 18th and 25th of October, so the next full backup would be on the 1st of November. But a full backup of all domains was created today (30th of October) and without deleting the full backup from the 18th.

I was pointed to that because my backup storage is full. Usually all backups take up no more space than 70 GB, now they take up 100 GB.

Is this a new bug? I checked the settings, they are as before.

 

[Sebahat.hadzhi]

Hello, @King555. We have no reports of a similar issue since the last update. Could you please double-check if there's a mismatch between the database and the server time by executing the following commands:

1.

date

2.

mysql psa
SELECT now();

 

[King555]

I just checked the two commands. Both show the same date and time and both are identical to my local time, which is definitely correct. So that's not the error.

On the 1st of November I deleted everything which has been created before the 25th of October to free up the storage space, although this leads to inconsistency within the incremental backups. On the 2nd of November a new full backup was created, although it should have been created on the 1st.

I will now wait about a week and check again whether the problem occurs again or solved itself.

 

[King555]

Between my last post and today I deleted some files again, because there was still some (new) chaos, but meanwhile everything seems to be OK again. I don't know why this happened, but now it's resolved.

Thank God these backups were not super-important, otherwise I would have big problems due to this behaviour of the Plesk backup manager.