Skip to main content

Cleaning out old backups

Thread needs solution

Hi.

I have a NAS that I use for backups and I have scheduled ATI to backup once a week on each of 4 PCs. ATI is configured as an incremental backup and a full backup every 3 increments. It is supposed to delete chains that are older than 1 backup.

To indicate one instance, the latest backup is B7 but it has S1, S2, S3, S4. There is no B6, part of B5 (S2 and S3) and B1_S1_V1 and V2 (it's not configured to keep the original).

The questions are, can I delete everything older than B7 manually and why is it doing this?

Cheers

   

0 Users found this helpful

Daylef, it is difficult to guess why your backups are not being cleaned up automatically with just the information provided so far.

I would suggest doing a Validation for your backup task(s) to see if that throws out any error messages?

Screen shots of your Backup Scheme configuration settings would help our understanding here.

Download the MVP Log Viewer tool from the Community Tools link in my signature and check for what messages are being written in the backup task logs, as they may also shed light on what is / is not happening here?

If you do decide to manually delete everything older than your B7 backup version chain, then you should definitely run a Validation after doing so, this will try to reconcile the information stored in the Acronis Database with the status of your remaining .tib files in the backup destination location on your NAS.

In reply to by truwrikodrorow…

Hi Steve

I checked the log and it doesn't throw up any warning or error just the standard process with "Operation has succeeded". I have noted that the log shows "deleting xxx" sometimes. What I think I might do is tick the validation box and invoke a backup manually. I'll report back.

Cheers

 

image

In reply to by truwrikodrorow…

I deleted the old backups manually and it seems ok. The validation didn't do anything other than take up a huge amount of time. I'll keep watching for the same thing over time.

 

Cheers

 

 

Thanks for the update, validation can take a long time depending on the size of the version chain(s) involved.  All the best for 2018.