ATIH 2011: Unexpected change of backup storage folder

Alexander,

This can happen when the user edits the backup name without navigating back to the desired destination folder: before you edit the name of a backup or create one, you have to navigate using the left navigation panel, double clicking you way until your desired target folder is open, then you can enter the task name.

BTW: I recommend against using the tags in the file name and/or using taks names different from the file names. There are corner cases where these create problems. YOu should be fine if you let your backups run without changing, deleting, etc. Also note that the default ATI naming (adding suffices to the name) will help you track which one is a full versus a partial backup.

I saw your other posts and don't know the answer to these questions.

Pat, thank you for your prompt reply and your suggestions!

However, i'm pretty sure that i ...

• did navigate to the destination folder when creating backup tasks. (This happened just by intuition: The dialogues did'nt let me feel certain that ATIH 2011 saved a chosen/changed desuitination folder without going the more cumbersome way.)
• did not change the backup name. I created the backups in the midst of January and saw the first backup tasks working fine. Now in April, i visited the site again and found several backups wrongly in "X:\My Backups".

Do you have another idea what could have happened? Or could you specify the conditions when ATIH 2011 uses "My Backups" instead of the desired folder for backup destination?

If i leave out tags in the backup file name, what naming rules does ATIH 2011 use? In the manual for ATIH 2010, there was a section "3.3 Backup file naming conventions" but that's missing in ATIH 2011 manual.

The ATIH 2011 installation on the computer has an unfortunately long history (starting with ATIH 2010, updating, upgrading to ATIH 2011) with a lot of troubleshooting because of several problems which in the end seemed to be solved by Acronis support. In this process, backup tasks have been created, changed and deleted many times. If i really should not touch backup tasks after creation(?!), what do you recommend to get a "clean" ATIH setting again? (Hope your answer won't be "uninstall + install from scratch" ...)

Alexander,

Based on my experience when I was searching my way with ATI 2011, you may have edited some backup settings and not paid attention to the default location. That's my hunch only, and not an accusation :-)

If you don't put the tags, ATI will add an integer between brackets at the end of the backup for the full backup, and an integer by itself after that for a partial backup. For example, MyBackup(2)2 is the first partial after the second full backup (there is no MyBackup(2)1, for some reason)). Or, MyBackup(3) is the second partial after the first full backup MyBackup.

Here is what I do when I do a clean install, I:
- move the backups I want to preserve to a hidden folder, so that ATI doesn't find them when I reinstall,
- export my backup settings,
- uninstall ATI,
- run the cleanup utility,
- delete any remaing tib file that I didn't preserve,
- reboot,
- reinstall ATI,
- import by backup settings back,
- run my backups for a while until I decide that the backups I preserved can be deleted manually, then I delete them.

A simpler way is to:
- do the move in a hidden folder thing,
- export your backups settings,
- delete all your backups from the backup lists (ATI will complain, crash when you insist rightfully),
- delete any remaining file in c:\programdata\Acronis\TrueImageHome\database, and \TruImageHome\Scripts,
- delete any remaing tib file that I didn't preserve,
- reimport my backup settings and get going just like above.

The simple cleans up the database

Pat,

thank you for sharing your experience and best practise. Moreover, thank you for not accusing me ;-)

As per your hint i deleted the old backup tasks, created new tasks from scratch, now without any tag in the backup file name, saved the tasks - and reopened them to verify the settings. I will check the results next week (when tasks should have run several times again). If the error should occur again, I'm afraid there's nothing left for me to clean up ...