Grandfather-Father-Son (GFS) Differential, Not Incremental Backups . . .

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 1
Kommentare: 0

We are currently using Backup & Recovery 10 (Update 4, v.10.0.13544) in a Business Environment.

We are currently running a Nightly Differential Backup because the GFS backup scheme built into B&R relies upon INCREMENTAL daily backups, which we feel is dangerous, as 1 failed backup could break the whole set.

This being said, we are looking for a solution WITHIN Acronis (yes, we could use scripts, but would rather not) that will run a G-F-S style backups scheme based on DIFFERENTIALS, rather than INCREMENTALS.

Does anyone have a similar solution?

Within Acronis B&R, what can be done?

Currently, I can only think about MOVING FILES OUT of the folder to accomplish this solution, but then the "clean up" routines and retention rules go completely out the window.

What we are looking for:

>> Keep every monthly FULL BACKUP.

>> Keep every weekly differential backup within the current month, then delete at end of current month all but latest.

>> Keep every daily differential backup for the whole week, and delete at end of current week, but the most recent.

Thanks for all your help, Acronis Team & Community

Sa, 10/01/2011 - 00:34
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Beiträge: 159
Kommentare: 518

Hi Tech..

Might be good to wait a little longer for someone else’s reply on this as it’s not something I have done myself yet and I don’t believe it’s possible to change the GFS scheme as such

What I did what to mention however is that performing an daily incremental will not cause any issues if a backup job fails the next backup that runs will still be valid and you will be able to recover from any point in the chain of backup files. You can also setup your backups jobs to retry if error’s occur or even re-start the job if it fails for whatever reason which is a good option to have enabled if you start to see failed jobs occurring every now and then. Another option to look into would be to limit the network bandwidth (if backing up over the network) as at times we’ve found this to increase backup reliability on some networks.

On a side note I’ve had customers ‘loose’ incremental backups before or delete them by mistake and they were still able to recover files from within the archive as the files they required were not included in that ‘missing’ incremental backup. It’s obviously not something I would recommend but was a good outcome from a bad situation I thought would be worth mentioning.

All the best with it.

Mo, 10/03/2011 - 06:31
  • Anmelden, um Kommentare verfassen zu können