Forwarded to devs Creating "too many" manual full backups results in removal of older backups although not expired

[Bitpalast]

TITLE:

Creating "too many" manual full backups results in removal of older backups although not expired​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Onyx 17.07, 17.5
CentOS 7.2, 7.3
64-Bit​

PROBLEM DESCRIPTION:

Backup are set to:
28 backups max.
full backup every week
incremental backups in between
3 weeks retension time

When manual full backups are created and the number of full backups defined by thhe number of weeks retension time is exceeded, Plesk removes all old backups, leaving only the latest, new backup and the ones that reach back to the previous full backup. If that backup was, e.g. 1 day ago, all previous backups are lost.​

STEPS TO REPRODUCE:

Create backups by the backup plan described above. You should have three full backups and the incremental backups after them in storage.

Then create manual full backups.​

ACTUAL RESULT:

When the number of full backups is exceeded that matches the retension time in weeks, Plesk removes all older backups. It does not look at the weeks, it looks at the number of full backups.​

EXPECTED RESULT:

Plesk should not count the number of full backups that exist in the storage space to determine the "number of weeks" but the actual age a backup file has.

It is not doing so at the moment. It does not check the age of the file but only counts the number of "full backup" files, then subtracts them from the "number of weeks" that full backups ought to be retained and removes all excess backup files.​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

Thank you for report.
Root cause - we cannot divide manual and scheduled backups. Issue PPPM-7082 was submitted.