Bug: TI 9 changes drive letter and makes files not visible

I found a significant problem using demo TI 9.
I am using a multiboot system. All OS are windows 2000 (latest updates as of last week).

I backup to external USB drive, swapping the drive every few daze to protect the backups.

Last night, I ran a full image backup of my system. The USB drive is drive N.
I then played with TI's menus and options.
Next, I wanted to use the other USB drive, so I unplugged the drive using the proper mechanism in the system tray.

To my surprise, when I plugged in the other drive, NO files were listed.
So, I unplugged, then replugged the drive, still same problem.

So, I then rebooted to one of the other OS (that does not have TI) and voila, the files were indeed still on the drive.

I then rebooted back to the OS in which TI was installed. Now, the files were listed but, and I do have a big butt, the drive letter had been changed from N to O!!!!. Note that the drive letter might have actually changed to O when I first plugged in the drive, but, if so, I did notice it because I was more concerned that the files were not listed (since the drive has my latest Retrospect backup)

In addition, when I tried touse windows 2000 to change the drive letter back to N, the drive letter was N was not even listed as available!

What business does TI have causing my drive letters to change?!!!
The backup files themselves can be used to keep track of drive signatures, there's just no excuse.

This is a showstopper!

I used Retrispect to restore the drive on which the OS lives, to get rid of TIm and, as expected, the drive letter got set back to N when I rebooted.

 

I forgot to mention that I was using the 2302 demo.
As we speak, I'm downloading the demo again to see whether it has been updated to version 2323,

 

Perhaps, the problem was fixed in build 2323.
When I encountered theproblem described in this thread, I was using build 2302 and created a base recovery set for all drives.

Earlier tonoght, I installed build 2323, but this time, to speed testing, I created a base recovery set for only 1 drive. I would not expect this to have invalidated the test.

In any case, this time, when I swapped in the alternate USB drive, the drive letter, correctly, did not change. So I must conclude:

1. The problem has been fixed after build 2302, or
2. The problem still exists, but does not happen all the time.

It would be useful if Acronis would tell us whether the problem had been explicitly fixed.

 

Hello Howard,

Thank you for your interest in Acronis Disk Backup Software and for posting back with the results of your investigation.

Actually, I have not heard about such problems of Acronis True Image 9.0 before and so I'm inclined to believe that most likely some kind of an accident took place. Moreover, there is no way to find out what exactly has happened since you have already restored the "non-changed" operating system from the Retrospect image.

However, if the problem will appear again with 2323 or any further build of Acronis True Image 9.0 then please collect the following information:

- Create Acronis Report and Windows System Information as it is described in Acronis Help Post;

- Make a screen shot of Windows Disk Management by following Start -> Control Panel -> Performance and Maintenance -> Administrative Tools -> Computer Management -> Disk Management;

Please keep any of your external hard drives connected while creating Acronis Report, Windows system information and the screen shot of Windows Disk Management.

- What exactly happens when you try to change the drive letter of your external hard drive?

- Describe actions taken before the problem appears step-by-step;

Submit a request for technical support with the subject indicating that you want to contact Alexey Popov. Attach all the collected files and information to your request along with the link to this thread. I'll forward this information to our Testing Team and they will certainly do their best in order to find out the reason for this problem.

Thank you.
--
Alexey Popov

 

Such problems are no accident.

At least the problem did not occur wit build 2323, but a far worse problem occurred. I may post a separate thread on that disaster.