File backup size explosion
I'm using TIH2012, and normally, use it to backup whole disks, using max compression. That approach usually results in a size reduction (relative to the data size on the drive being backed up) of between 50 and 70%.
I used the file backup option recently to save selected file folders on a large disk otherwise containing a lot of working data. I was surprised to see that - even using max compression - the resulting .tib files were huge relative to the source data. Typical examples:
case 1 - original folder data size 19.6Mb, .tib file size 806Mb
case 2 - original folder data size 181Mb, .tib file size 961Mb
case 3 - original folder data size 243Mb, .tib file size 996Mb
Is there any rational explanation why - using the files backup option - the compressed backup file should be between 5 to nearly 100 times the size of the data being backed up??
Davidk
Small - depends on your definitions I guess.
Compared to the disk level backup tho - the files approach looks crazy. If I back up a full logical disk - NOT sector by sector - that just has games on it, at a comparable size of data, the details are: original size - 115mb, compressed drive backup - 14Mb. That's a reduction of 10x, nearly. Note, reduction in size.
So a technique at a specified folder level rather than files at a disk level - ie a folder backup as opposed to a full disk backup - explodes it by 10x really calls into question the veracity the design and function of that mode in the software. An outright copy of files would be a better utilization of the available disk space to get a backup copy.
Davidk
I think your units may not be correct. I cannot imagine that your full disk, with installed games, is only 115 MB. I think you may mean GB.
When you image a drive or partition, large compression is possible as there is typically a wide range of compressable files on it. When backing up files only, much depends on the nature of the files. Files that are already compressed, such as jpg, mp3, etc., cannot be further compressed. It is a known phenomenon that compressing such non-compressable files into an archive results in larger, not smaller, size. This occurs with other containers such as Zip files.
For such files, I prefer to use a tool that backs them up in native format. I use Robocopy, but there are many other file-based backup tools available.
I appreciate the feedback, but the drive numbers are as stated.
Two drive level images (screenshots, cropped to show the relevant details) from windows explorer to demonstrate that - 1) properties of the logical drive; and 2) the drive level backup file in the archives drive. Backed up file name has the drive letter name and date in it, and is part of the whole of PC archive, dated 31Aug 13.
