ATIH 2011 build 5105 doesn't retain modified backup settings
ATIH 2011 build 5105 on Win7 64 bit. - The backup settings editor has severe oddities which can potentially cause .tib files to get lost. Two examples follow here:
I created a backup process to G:\MyBackups and ran it. Then I changed the drive letter to D: and I wanted to change the backup settings accordingly. It accepted D:\MyBackups nicely but as soon as I started running the (incremental) backup then it suddenly changed the field to G:\MyBackups and prompted that it couldn't find the destination (obviously). Also changing the backup name seemed to work at first sight, again until the backup was started and the old name was used. During my experiments I lost a .tib file with some "old name", totally unexpectedly.
Another scenario which illustrates GUI oddities:
Create a backup config with location D:\MyBackups, backup name ABC.
Start the backup, it creates the file ABC1.tib . Cancel the backup.
Edit settings, rename the backup name ABC to DEF and press enter.
Restart the backup. It will create ABC(1)1.tib ! Cancel.
Rename it to XYZ. It will then create ABC11.tib .
Subsequent names after more renames are ABC1(1)1, ABC111, ABC11(1)1, ABC1111, ABC111(1)1 etc.
The danger here is also that it may potentially remove a .tib with an old name.
So, the GUI may have a beautiful look, it's logic doesn't look that beautiful. Apparently nobody tested it. Nah.
Andre

- Log in to post comments

Then I tried to "delete" the backup set ABC. The first time it said that it couldn't find all backup files (not sure about the right wordings). A next time it deleted the backup set - it left the file alone, fortunately. But shortly after the program produced an AV:
77018C19 inc dword ptr [eax+14h]
EAX 00000000
ESI 07974438
> ntdll.dll!77018c19()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!77018b28()
TrueImage.exe!00622d07()
TrueImage.exe!00581232()
TrueImage.exe!00582add()
QtCore4.dll!67014afd()
ti_managers.dll!04f1143c()
thread_pool.dll!20601a09()
thread_pool.dll!20602337()
msvcr80.dll!746e29bb()
msvcr80.dll!746e2a47()
kernel32.dll!76983677()
ntdll.dll!77019d42()
ntdll.dll!77019d15()
Andre
- Log in to post comments

Unless you are using the alternative backup place option, you will need to have two tasks - one for each drive location. TI keeps a track of the drive letter and disk ID assigned by windows to work out if the correct drive is attached for the corresponding task.
- Log in to post comments

Colin,
I do agree with you, but my point is that whatever the GUI allows you to enter should be processed in consistent manner - which is clearly not always the case.
The Acronis team needs only to put one tester guy during a few hours on it and he'll probably detect a multitude of bugs. That guy should NOT be a developer, of course.
I'm using TI since the beginning and fortunately the backup engine is of higher quality. Except the cryptic error messages. :)
Thanks,
Andre
- Log in to post comments