Salta al contenuto principale

Is Shrinking a sector-by-sector .tib file possible?

Thread needs solution

Hello,
I created a 147G tib file, onto my portable drive using ATI Home 2010. i did this as my first time with ATI and chose sector-by-sector, is there a way to shrink this 147G .tib file to only the 12G of actual data used on that drive. ?

thanks.

0 Users found this helpful

Michael:

In order to get smaller backup files you cannot use "sector-by-sector" mode. This mode copies every sector on the disk, including ones without files and empty sectors, to the backup archive. You want the normal backup mode. Try the backup again but this time de-select the "sector-by-sector" option.

Unfortunately i cannot run the backup again the system drive has died.. and the replaced drive is smaller..
so thats why im trying to shrink the .tib file.. to get rid of all the unused space information.

thanks.

Michael:

I understand now. Well, this presents somewhat of a dilemma. Did you use sector-by-sector mode because you had bad sectors on the original disk? That might complicate restoration of the image to a new disk.

If not, maybe this will work. Borrow a disk that is the same size or larger than your failed disk and restore the image to this temporary disk. Then create an image of the temporary disk using normal compression. This new image should then restore to your new, smaller hard disk.

No the drive had issues trying to start powering up.. once powered up and spinning it had no actual data errors.

So that brings up a good question.. could i restore it to a virtual hard disk, temporarily, then create a image using normal copy. (non sector by sector)

(( has anyone tried that? ))

The answer is "yes and no".

The yes part is you can do a sector-by-sector restore to a VHD, as long as the VHD is sized to be larger than your 147GB image.

And that sets up the "no" part. Even if the VHD is "dynamic", a sector-by-sector restore will force it to expand to the size of the image, so your VHD will *physically* grow to the full 147GB of the image. In the end, it won't help your current situation.