Aller au contenu principal

Consolidated backups creating multiple huge files...why????

Thread needs solution

Greetings,

I am creating a consolidated backup which is set to consolidate after 5 days.

On the first day, it creates the initial .tib file which is about 150 Gig.  Then,

on the subsequent 4 or 5 days I get a handful of 2 to 7 Gig files.  However,

on day 5 or 6 I get another huge file which has a string of letters, numbers,

and dashes in the name; it's about 137 Gig.  A day or two later, I get another

huge file again with the crazy long name and it's 118 Gig.  My goal was to have

one big file and a bunch of small files which consolidate into the big file every

5 days.  I am on version 9.*.  Is the way it is supposed to work????

0 Users found this helpful

Does your PC go into sleep mode whilst consolidation is running or do you get a warning about low disk space?

One thing that can cause what you see is if TI is interrupted for whatever reason whilst attempting the consolidation.

The tib file that has the CLSID type name is one of the consolidation working files. If the consolidation has been interrupted it will always start a new temporary file (sometimes from the beginning sometimes as a continuation file), often these files get left behind once the task has finished.

If as it seems from what you have written things have got out of wack, I suggest opening each real archive in Windows Explorer - check that they are complete and then delete the CLSID type temporary files. DO NOT DO THIS if you are using the SZ.