Large diffs all of a sudden
I got a message that my target disk was running out of room, and usually it doesn't run out of room before deleting older versions. I look on my drive, and my diff files since my previous full are much larger than usual, in fact, they're larger than my last full. What could possibly be going on here?
Or, did you tweak the backup task in anyway and/or rename the Acronis backup database folder and let it rebuild again? If the backup task was changed, differentials will start the version chain over. With incrementals, this can mean that the next incremental will be as large as a full then, with the rest being smaller after that. With Diffs though, each diff could be as large as the original full (or larger considering any changes that have occured since the first full was taken) since diffs are all changes since the last full was created.
Steve, I thought about that, and I definitely haven' t done any intentional defrags, and I checked to make sure I'm not doing any scheduled.
I'm going to keep an eye on it and follow-up if it continues.
Bobbo, I've always done a full followed by two diffs each week. This allows me to restore even if the one of the pieces of the chains gets corrupted. Usually, the diffs aren't this large.
I think I'm going to restart these from scratch.
Les,
Curious. Would you post a picture of your storage folder showing the full names and sizes of the tib files.
Does the service logs provide any information?
Was the computer involved in any Windows upgrade which Window 10 did recently to a new build?
Grover, it's attached to my original post. See the screen shot.
Yes, I recently upgraded to Windows 10, but that was a while back. I think there were a number of updates it installed earlier this week, but Windows 10 isn't as polite about letting me know about updates, so I have trouble telling when, if, and how many updates it installed. Maybe that is it.
I noticed that my T-Th-Sat routine did two fulls in a row for some reason, but they're clearly labelled as such.
I am thinking it might just make sense to start over, as I said in my earlier post. I've often found that when things start to go south in Acronis, it just makes sense sometimes to just clear out the cobwebs and start from scratch.
The B51 series could well be Windows updating. The B52 Full is only one full with two pieces (V1 and V2).
The anomoloy could be updates or bad sectors. Let the B52 diff S2 run and check the sizes.
After B52, diff S3 runs but before the next full runs, you might want to check your disk for disk errors--just as a safety precaution.
Are you validating as the backup runs. If not, you might want to validate.
While starting over is an option, why not wait until the next full runs, or if you have the space, run a new task in tandem with the old and compare, but either way, I would check the disk for errors.
The Windows downloads could have interfered with the backups and there was an interruption which mght account for two pieces to the last full.