Acronis TI 2013 build 6514 Metadata database file

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Regular Poster
Messaggi: 22
Commenti: 86

Build 6514 Windows 7 64 bit Pro.

Is there any way, other than removing and re-installing True Image, and deselecting "search for back-ups" after install, of clearing the history in the metadata database file, located somewhere? Or what would happen if an older version of that file in a back-up, were replaced with a newer file from a clean install?
Thanks.

Dom, 09/22/2013 - 16:22
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Messaggi: 8
Commenti: 1344

Changes made in the program usually update the .xml automatically when the program is closed and reopened. I would not recommend making changes manually. If you are having problems, I would suggest performing a repair install. If the .xml is badly damaged, I would back up my settings, perform an uninstall, use the clean up utility (follow ALL instructions) , reboot, then reinstall and import my saved settings, Tasks, etc, If you are referring specifically to disabling the scan for back ups when the program starts, Grover's Help guides have the steps to do this, including the registry changes that need to be performed BEFORE you start the program for the first time.

Version changes can get broken if you restore to a previous point in time and have back ups that exist and are present after this date. The program is suppose to recover from this gracefully, but this does not always happen and in the case of multiple back ups and version chains is even less possible. If the back up you restore has not been updated to the same naming convention used by the currently installed version, once again, problems can result. Again, however, back ups which are deleted, then re-added to view will then appear in the .xml and then become "known" to Acronis.

Dom, 09/22/2013 - 18:12
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Regular Poster
Messaggi: 22
Commenti: 86

Thanks for your reply. Search for back-ups is always off and I only make full back-ups, nothing else. I've had a random on-going problem with the software since day 1. It's re-emerged after uninstalling and reinstalling TI 2013 about 4-5 times now. I've also tried different downloads to insure it wasn't a particular download being problematic. A new install has no history of back-ups prior to the install so that's how I've been clearing history. I actually believe the problem is most likely caused by the design of the software. I create full back-ups in custom named folders, stored either within or outside of the "my back-ups" folder on external hard-drives. Doesn't matter which is the case and the problem follows the drive used. I properly delete back-ups using the TI console that I no longer want, which removes the name from the back-up list and deletes the tib files that were in the folders, but leaves the empty folders on the drive where they were located. I then use the Windows OS to delete the folders. No problems at this point. Sometime in the future after the deletions, maybe a few days, maybe more, the software places empty folders where they were previously deleted, with the correct names of the deleted folders. I'm getting a new computer in a few days and will be installing all software myself. I use TI as an alternative to Windows system restore, which doesn't always work, in case of install problems, and make a number of full back-ups along the way, during my install software, deleting unwanted back-ups as I go. This aforementioned problem creates havoc for me. I imagine I could store all of the tib back-up files in a single folder or in my back-ups, but I find that harder to read, than separate titled folders containing the tib back-ups. Also, if I go to tools, mount image, most if not all of the deleted tib file names appear in the window, even though they have been properly deleted. The only solution I can think of as to history, in lieu of removing and reinstalling the TI software, would be if there was a way to clear the history database. But I've no idea how to do that.

Dom, 09/22/2013 - 21:02