Aller au contenu principal

Act of mounting an image as Read/Write creates a .tib file?

Thread needs solution

I wanted to look at some Registry entries in a backup this morning, so I mounted one of my backups as a Windows drive e.g. as I:\ from this file:

backup_2014-06-02_full_b1_s1_v1.tib

and I mounted it as Read/Write lest regedit.exe complain when I attempt to Load Hive.

Well it works of course but I see later after unmounting the .tib file that a new file has been added to my backup drive:

backup_2014-06-02_full_b1_s1_v2.tib

Note the "v2" on this file, and it is one-hundredth the size of the original i.e. 350MB vs the original 33,000MB.

I did not afaik make any changes to the mounted image, at least I certainly INTENDED no changes, I only Exported a key from it, so

1. Is there anything of value in this v2 file i.e. anything ATI needs in there for the future?

2. Can I delete it from my backup drive?

I'm a long-time user of ATI but have never, ever worked with versioning--I've only always made complete backups each time--this smallish file concerns me now...

EDIT: I've now mounted another .tib, this time right-clicking it in Windows Explorer from the list of .tibs on my backup drive, and I see that the simple act of mounting the .tib in R/W mode causes a v2 file to be created. I want to delete these and assume I can do so with no impact to the original full backup?

0 Users found this helpful

Hi Tom,
I see your helpful postings. Keep it up!

Use the TI program to delete the added file and it should be ok. You can validate afterwards for more assurance.

GH5. How to delete backup files using Acronis Backup 'Explorer'

Thank you GroverH! While waiting on a reply, and thinking about this some more, it occurred to me that AFAICT the original backup had not been touched in any way, therefore I surmised that it ought to be perfectly useable without the v2 file.

I didn't know about the Versioning stuff your Help pic shows. Guess it's time I actually used the software huh! For too long now I've been buying licenses but then I've only used the "boot disk" functionality! Though I did observe after making my first backup at the Windows desktop that it is almost an order of magnitude slower that from a boot disk. Handy though.

Thanks again.

For the record, the easy way to get-rid of these R/W mount additions is to right-click on the date and Delete, then right-click on the initial backup date and Validate.

Unhappily for me, I tried first to Validate by clicking the Settings icon for a backup, which opens a sorta useless dialog while the Validate progress bar occurs in the background. If you Close that open window it kills your validation mid-process.

Thanks for the follow-up.