Skip to main content

Continuing Incremental backups when full backup image is changed

Thread needs solution

I currently run  full disk image backup once per week.

I have also setup to reun incremental backups on a once per day basis at system shutdown.

This appears to work fine. However, whne I create my new weekly backup I have to edit my incremental seting to point to my new weekly disk image.

Does any one know of a way of automating this process? I would like to be able to just point & click to link my incremental schedule to my new disk image.

0 Users found this helpful

Are you using the exact same backup file name for both FULL and INC? I run a FULL on Mondays and INCs on the other weekdays and this works fine week after week with no intervention on my part. IOW - if you’re using the same name, it should work.

Related to using the same names, do the existing files get wiped out before the new backups are completed? In other words, are you OK if some failure occurred while the new backups were being made? 

Jim

Peter Barker wrote:

I currently run  full disk image backup once per week.

I have also setup to reun incremental backups on a once per day basis at system shutdown.

This appears to work fine. However, whne I create my new weekly backup I have to edit my incremental seting to point to my new weekly disk image.

Does any one know of a way of automating this process? I would like to be able to just point & click to link my incremental schedule to my new disk image.

- I am using a different file name for the Full, since I don't want to loose the last full backup before the next one is completed.

You just given me an idea - what if i rename the old backup before the new one is run ? This would mean that I can continue to use the same name for the full back up - which should work if I understand your comments correctly.

If you create a FULL named “MyBackup”, any INC you want to create based on that backup must point to “MyBackup”.
If you later create another FULL named “AnotherBackup”, the INC task you had earlier created will still base itself on “MyBackup”. They work in tandem – both FULL and INC tasks must reference the same .tib name.
“what if i rename the old backup before the new one is run ?”
Once you create a string of a FULL and any number of INCs, I think you’re asking for trouble by renaming any of them since they were created using the .tib name as a link. I think you’re asking for even more trouble by renaming the FULL and then creating another with the original name leaving a string of files that are not connected but whose names would make it appear as if they were.