Aller au contenu principal

Confused about the size of the backups

Thread needs solution

I have five full OS backups on an external drive. The backups were all made of the same OS, W7. Two of the backups were made as reserve backups when I made two backups in the ASZ using the True Image software on the operating system. I removed the ASZ because I was having problems with it. The other three were made as full back ups using True Image on the boot disc and their creation was directed to be placed in a backup folder on the external hard drive. The first two backups were 21,769,141 KB and 25.010.332 KB. Which made sense to me because one of the backups had more software on it.
The three backups that were made when I started True Image from the boot disc were 11,800,348 KB, 26,251,656 KB, 13,069,512 KB. All three were full backups. This makes no sense to me at all because each backup had more or less the same amount of software it. I did test all the back ups and they all are functional. Would someone please tell me why two of the backups indicate have of the file size? Would I jeopardize any of the backups if I deleted one of the three backups?

0 Users found this helpful

pastafazoul,

First off, let me say that ATI is very reliable with copying data, so there is a rational explanation about the differences in size.
Differences in the size of the TIB file of full disk and partition backups can be due to (if we eliminate obvious user errors like not selecting the same partitions):
- different settings in image compression,
- selecting or not selecting the sector-by-sector option (default is off),
- file exclusions differences,
- variation in the size of the page file (when it is automatically managed by windows). Although the content is not copied into the backup archive, a placeholder file is created of the same size as the original file,
- turning on or off hibernation, which creates the hiberfil.sys page, handled by ATI just like the pagefile.sys
- variations in Windows indexes,
- differences in temp files in the Windows/Temp folders and or the Users/appdata/local/temp folders,
- variations in NTFS file system information (in the System Volume Information folder)
- volume shadow copies created by the Windows System Protection mechanism (same folder as above)
- actual file system errors (fixed by chkdsk /r typically).

I am not sure that explains your case, but this is a good list to review and evaluate.

Also, there have been cases where a backup .TIB file gets saved to the Windows partition and then gets included in later backups. This causes a dramatic increase in size (usually double or more).

In addition to what was said before, it looks like it detected file system errors three times of five and silently used sector-by-sector mode.

Thank all you for the help.

I recovered the back up images that were the largest and ran check disk on the operating system after it was recovered. I then backed up the operating system and the tib file was reduced by half. I am wondering if the new back up that I ran check disk on is still valid.

Other than running check disk on the operating system before I make a back up is there anything else I should be doing? Should I run a registry cleaner? Is there one that you would recommend? Is there any other form of check disk out there that would be better than the one that comes with W7. On XP I used to use System Works, but that is not available for W7. Is there some other soft ware that you would recommend?

Thank you all so much.

We have seen manufacturer's disk diagnosis tool find errors that ATI saw but not chkdsk /r, but this is very rare.
For registry cleaners, JV16 Power Tools has a good reputation, but some users beg to differ and some just dismiss the benefits of registry cleaning. Revo Uninstaller is useful to control how programs install/uninstall.