Merging .tib Files
In the past I backed up one former employees laptop to a FAT32 drive and it divided the files up into 4GB pieces. While I can still easily access the image, it looks messy where I'm storing it relative to the other backups of former employees:
http://img51.imageshack.us/img51/438/0uj5.png
How can I use Acronis to merge these FAT files into one? Meanwhile, I'm manually copying all files from the image and going to see if I can use Acronis to rebuild a single image from the raw files.
Fichier attaché | Taille |
---|---|
a1.png | 66.68 Ko |

- Se connecter pour poster des commentaires

Yeah I guess that would be the best bet, restore then re-create. I did manually copy the files from the split up image then re-imaged the files. While the new single file I created is no longer bootable, it still puts my mind at ease than having scattered tib files.
Thanks!
- Se connecter pour poster des commentaires

Not to mention you can have more full backups on the same storage medium for extra security.
- Se connecter pour poster des commentaires

Just thinking out loud, you might be able to convert the archive to VHD using the True Image utility and then either leave the VHD image or then convert the VHD image back to tib format, which will result in a smaller file than the VHD one.
- Se connecter pour poster des commentaires

Good idea if you want to stick with just the single existing backup. Each conversion risks a bad byte and only one is all it takes to ruin the backup. so consider having spares.
- Se connecter pour poster des commentaires

Colin B wrote:Just thinking out loud, you might be able to convert the archive to VHD using the True Image utility and then either leave the VHD image or then convert the VHD image back to tib format, which will result in a smaller file than the VHD one.
How would I go about that? If I convert to VHD, I can then mount and (propably) create an image of that mounted drive. My question is; would that still be bootable? The VHD seems to include the system partitions when I check in dis manager, but the drive letter is of course no longer C (in my case the mounted drive is F).
I am referring to mounting it as a drive under windows 10 Enterprise but not mounting an actual virtual machine here. That would be possible with my win10 version, but I have zero experience with virtual machines.
- Se connecter pour poster des commentaires