Forced full backups after a successful restore

Every single time I have to restore my installation for whatever reason, the backup/restore utility always creates a new, full data files/image backup. As one can imagine, this gets very large after a while and I would prefer it to continue backing up incrementally. Is there any way of informing or resetting Windows that the backup is still there, intact, and that there is no need for another full backup? I did find a bit of a workaround using the "make incremental backup" tutorial/download here on the forums, but I was wondering if there was possibly another way without doing any more backups (until scheduled, of course). Let me know if any more info is needed. Thanks in advance. Edit: Upon checking the backup files, the above workaround does not work, unfortunately. It still thinks it must perform another full backup.

Hi there
note however in addition to the tutorial that if you do a FULL restore using incremental backups you need to do the following

1) FULL restore from the last FULL backup you have taken.
2) Restore ALL the incremental backups in the order they were taken up to an including the last one.

on a NON FULL restore

you need to restore ALL the incremental backups from the earliest known COMPLETE file GOOD date to the latest good date.

for example you need to restore file X. You know it was good on wed, and thur but not sure about Fri.
so you restore full file from wed and thur version. (You need both since the thur version will only have the CHANGES from wed).


@kado897 -- I'm 100% positive that image copies (partition copies for example) can only be restored in their entirety -- not a problem when restoring an OS. Data however can be restored via incremental backups as you've stated.

Cheers
jimbo

jimbo45 said:

Hi there
note however in addition to the tutorial that if you do a FULL restore using incremental backups you need to do the following

1) FULL restore from the last FULL backup you have taken.
2) Restore ALL the incremental backups in the order they were taken up to an including the last one.

on a NON FULL restore

you need to restore ALL the incremental backups from the earliest known COMPLETE file GOOD date to the latest good date.

for example you need to restore file X. You know it was good on wed, and thur but not sure about Fri.
so you restore full file from wed and thur version. (You need both since the thur version will only have the CHANGES from wed).


@kado897 -- I'm 100% positive that image copies (partition copies for example) can only be restored in their entirety -- not a problem when restoring an OS. Data however can be restored via incremental backups as you've stated.

Cheers
jimbo

That seems like a fair amount of restoration to get the desired effect, especially considering the amount of data I have. So I would have to restore, incrementally, each file to the date of the last backup in order for the utility to behave as if the files were unchanged from the image restore? Also, how do I differentiate files in the backups as incremental vs. full?

@Kado
That was the tutorial I used before. At first, I thought it was incremental, but it actually did not change its behavior. It made a completely new full backup from the one made prior to re-imaging.

You might do better by making system and data imaging separate processes.
I haven't done all the various backup permutations the Win 7 utility allows, but fairly quickly found some disadvantages it has compared to other imaging software, and decided not to use it. But that was just due to my preferences.
Since you like incrementals for your data, you might find that doing them without the system image ticked will allow those to be restored without a needless extra image being taken.
Do the system images separately, either with Win 7 or other imaging software.
I don't know if that would resolve your issue, but it's easy enough to test.
I don't want to dismiss the Win 7 incremental and scheduling capabilities, since that can be valuable to some people. So the object is to get it doing what you want, by adjusting to its capabilities.
Sometimes I wish I had stayed with the Win 7 backup, so I could play guru here.
But I didn't. Still, as a long time computer guy, I can confidently say that fully automated processes often add more complexity than is good, and that divide and conquer is the best tool for solving problems.

kado897 said:

In normal circumstances Windows backup uses it's own nearly indecipherable rules to determine whether this should be full or incremental. This shortcut forces an incremental, provided of course that there is already a full backup to be the base.

I am beginning to believe the indecipherable part. There was a preexisting full file backup prior to the image restore, but even with the shortcut mentioned above, it still made another full file backup.

Victor S said:

You might do better by making system and data imaging separate processes.
I haven't done all the various backup permutations the Win 7 utility allows, but fairly quickly found some disadvantages it has compared to other imaging software, and decided not to use it. But that was just due to my preferences.
Since you like incrementals for your data, you might find that doing them without the system image ticked will allow those to be restored without a needless extra image being taken.
Do the system images separately, either with Win 7 or other imaging software.
I don't know if that would resolve your issue, but it's easy enough to test.
I don't want to dismiss the Win 7 incremental and scheduling capabilities, since that can be valuable to some people. So the object is to get it doing what you want, by adjusting to its capabilities.
Sometimes I wish I had stayed with the Win 7 backup, so I could play guru here.
But I didn't. Still, as a long time computer guy, I can confidently say that fully automated processes often add more complexity than is good, and that divide and conquer is the best tool for solving problems.

It's not the most feature-rich utility, granted, but it is native and doesn't require more installations. I've also had a bad taste left behind by several of the more popular utilities, both free and shareware. They usually either caused a BSOD, corrupted the MBR, or something along those lines. Surprisingly or not, I've never encountered any weird issues stemming from the native backup.

As far as doing them separately, the imaging isn't the only problem, since the data file backup also makes another full backup. That is what makes the whole thing so large and it is only after a restore that this happens.


If it comes down to it, is there a particular backup utility, preferably freeware, that would be recommended? Either that or I can just learn to live with the annoyance and delete older data as needed, I suppose.

amrobx said:

If it comes down to it, is there a particular backup utility, preferably freeware, that would be recommended? Either that or I can just learn to live with the annoyance and delete older data as needed, I suppose.

Macrium Reflect Free Edition is the most common recommendation to backup your C partition (Windows and whatever else is on C)

Synctoy and Karen's Replicator are among the most common recommendations to back up your personal files, not Windows.

All of them free. All of them are about as easily understood as possible for such applications.