Salta al contenuto principale

Retention rules not working

Thread needs solution
Beginner
Messaggi: 1
Commenti: 2

I have several clients who are using Acronis Backup advanced on their servers. I have noticed lately (for about the last year) the retention rules are not working correctly. I have backup plans that are of the "Custom" scheme with weekly base backups and daily incremental backups. The retention rules are set to delete the oldest backup volumes when the number of backups in the archive exceeds 2. This has worked for years.

At some point, after running updates on the software, this no longer works. now the archive is deleted after the 2nd incremental backup is created. leaving only one archive (with the incrementals). The settings have not changed. The plan was always to have 2 full archives, and delete the oldest one after the third archive has been created. All are currently running build 11.7.50230.

0 Users found this helpful
Support specialist
Messaggi: 0
Commenti: 1295

#1

Hello Dan,

welcome to Acronis forums!

Could you please make a screenshot of your backup archive content (the series of full and incremental files) in File Manager (e.g. Explorer) and how it is presented in Acronis Management Console UI? Please share these pictures so we could compare and analyze the content of your backup archive. Please also export into a .json file your backup plan and share it here.

Beginner
Messaggi: 1
Commenti: 2

#2

Hi Maria,

Please see the attached screen shots you requested. I could not figure out how to export the backup plan as json. The only option was XML, which I have attached as well.

The screen captures show the archive as it looked this morning. Last night, before the 2nd incremental backup ran, I had last weeks baseline backup and 5 incremental backups stored there. They were deleted after last nights incremental backup. They should not have been deleted until the next baseline backup runs this weekend.

This is just one example. I have seen this very same behavior on several servers.

 

Thanks,

Dan

Allegato Dimensione
530876-179901.jpg 205.37 KB
530876-179904.jpg 130.45 KB
530876-179905.txt 21.97 KB
Support specialist
Messaggi: 0
Commenti: 1295

#3

Hello Dan.

I have reviewed your screenshots and a backup plan. There is no inconsistency.

The retention rules are set to delete the oldest backup volumes when the number of backups in the archive exceeds 2. 

This is how it is set now: 

<backup_count_upper_limit>
2
</backup_count_upper_limit>

This means that a new backup will be marked for deletion as soon as the third backup in a row is created: full, incremental1, incremental2 - a full backup is marked for deletion (as it is illustrated on a screenshot from Management Console UI). However, a full backup can't be deleted until a new full is created. That is why your full is now marked for deletion and waits for the next full one. 

I recommend that you change: Retention rules, select Delete backups older than…, and then specify the retention period (e.g. 2 weeks as you wrote in your original post). Otherwise, you can switch to a Grandfather-Father-Son scheme and select different periods for monthly (full), weekly (differentials) and daily (incrementals) backups.

 

Beginner
Messaggi: 1
Commenti: 2

#4

Hi Maria,

These setting have worked for me for several years without a problem. Something definitely changed. It NEVER counted the incremental backups before.

 

Dan

Support specialist
Messaggi: 0
Commenti: 1295

#5

Hello Dan.

According to the information you've shared, the software works as scheduled:

Number of backups in the archive exceeds...2

Where Archive is a set of backups created and managed by a backup plan. An archive can contain multiple full backups as well as incremental and differential backups. 

Perhaps, somebody has changed the scheduler settings if they had worked differently.