Aller au contenu principal

Proposal for improved automatic cleanup of differential backups

Thread needs solution

While the existing automatic cleanup rules make sense for incremental backups, I think there could be some improvement in the rules for differential backups.

I suggest these new rules be added to the choices for differentials:

[] Cleanup differentials in a version chain (a check box, if checked the next two options appear)

       O Delete differentials older than X days

       O Store no more than X recent differentials on a version chain

Since for recovery only one differential is needed with the Full backup, this allows a greater number of differentials to be written before running a new Full backup, without all the space being taken or the performance hit by not having to do so many full backups. Because differentials always get bigger, a lot of space can be wasted.

As an example, one can do a Full backup once a month, but only a week's worth of differentials need be saved.

Additionaly, I could envision an option to create a new version chain when the size of a differential reaches X percent of the Full version (X being something close to 100% makes sense).

The idea here is to better balance space, performance and reliability.

Thoughts?

 

 

1 Users found this helpful

I like both ideas. 

I believe there is room for improvement in the scheduling and cleanup and types of backups too.  For starters, it would be nice if there was more flexibility in the scheduling so that you could run a full on set days (not days of the week, but let's say I want a full on every 1st day of the month and every 15 day of the month and whatever comes between them is fine).

I would also still like to see a backup chain that incorporates Full, inc and diff (grandfather, father, son) too.  Essentially this would cater to a set-and-forget monthly backup plan with maximum flexibility, minimal storage requirements and greater reliability of backups (since you'd have at least a differential to fall back on if any incrementals ever got corrupted).  This would be something like:  

#1 would be an initial full, followed by backups #2-6 as incrementals and #7 as a differential (week 1). 

Followed by 6 more incrementals and another 1 diff (week 2)

Followed by 6 more incrementals and another 1 diff (week 3)

Followed by 6 more incrementals and another 1 diff (week 4)

Followed by incrementals for any remaining days in the month

Then start the backup with a new full on the 1st day of the month, which would be the beginning of next monthly chain and repeat.

This would minimize the need for monthly fulls, reduce backup size by using incrementals for the majority of backups, and improve reliability, by having differentials spaced out, just in case an incremental did have an issue at some point. 

I also believe it would allow for a more informative manual "cleanup versions" menu where users could manually cleanup backups to free up space, and still retain at least certain differentials  (if needed).  

@Bobbo_3C0X1 my recollection is that the combination incremental/differential is available in some form in Backup 12.5. So it presumably would be relatively easy to import the code into ATI. As a set-and-forget solution it looks like a reasonable approach. Not sure how Acronis see the demarcation between features in ATI and features in Backup 12.5; they are directed at different markets.

Ian

Agreed.  I'd hope they also consider competitor features though too.  Macrium has been offering this setup for quite some time now as well and it is a solid backup scheme.  Of course, both products have their positives and negatives, but when certain features are available in one and not another, the scales may tip in favor of the other for some.  Macrium is also offering ransomeware protection for the Macrium backup image files (not whole PC... yet?).  

I'd also just like to see a "run full backup now" button at some point.

Bobbo_3C0X1 wrote:

I'd also just like to see a "run full backup now" button at some point.

+1 to that!

Ian 

Bobbo_3C0X1 wrote:

I'd also just like to see a "run full backup now" button at some point.

+1 here too.

I'd call it "Start new chain" though. To me that's clearer but I realize it may not be to others.

Good point Bruno. It is important that users will find it easy to understand what the button does.

Ian

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Guys, thank you for bringing up these ideas! The following feature requests have been opened\updated

TI-176473 Add new auto-cleanup options for differential backups

TI-95638 Add GFS (Grandfather-Father-Son) backup scheme

Great. Thanks, Ekaterina.

Regular Poster
Contributions: 198
Commentaires: 120

Bruno, Bob, Ian... Brilliant Ideas !

Steve F.

Great news Ekaterina! Hopefully they consider them! These would be awesome feature updates in my book.