Acronis does not seem able to detect when a previously removed backup drive is reconnected and seems to lose track of the backup files.
There seems to be a rather fatal flaw in TI's handling of backups stored on external drives. Acronis backups will always need to be manually reconfigured if the external drive is disconnected and than reconnected to the system. This is particularly noticeable with USB based drives that are frequently moved around. In my case my backups are stored on drive F:\SystemBackups which is an external HDD connected by USB. Any time I disconnect this drive from my computer all backups that write to it will fail the next time the drive is connected. AFTER the drive has already been reconnected Acronis still displays errors saying that it cannot locate the backup files. The file paths and drive letters have not changed at all but for some reason Acronis looses track of the drive when it is disconnected and despite the fact that the backup is pointed at F:\SystemBackups Acronis seems unable to figure this out unless I manually reset the destination. This makes no sense and if Acronis is unsure of whether the drive is inserted it should at least attempt to navigate to the folder path specified in the backup settings and take a look around to see if the files are there before throwing a error. it shouldn't matter which USB port the drive is plugged into It shouldn't matter what the disk number is It shouldn't care where or how the disk is connected to the computer as long as the drive letter and folder path remains the same. I suspect the root of the problem is an example of Acronis trying to be too smart for it's own good and using some arbitrary low level method of identifying hard disks that does not survive the process of ejecting a drive.


- Accedi per poter commentare

If the drive letter was changing you would have a point however the drive Is always assigned to F: and if it does rarely change its letter I do manually reassign the correct one before running backups but it seems more like the software doesn't attempt to try following the path to see if the missing files are presant and continues to display the error when in fact its really simple to have the program do an if something is off with drive follow path if files are present assume drive is presant
- Accedi per poter commentare

Actually when you mentioned it stores the drive UUID it gave me an idea as to what might be the problem. My external drives are in a 4 bay chassis and they are connecting via a port multiplier. I know some software can only see the information from the first occupied bay IE if bay 0 and 3 are occupied only the model and smart data from bay 0 are shown I wonder if what is happening is that when I pull the drive it starts reporting the model for bay 3 and keeps displaying this even if 0 is reinserted... that would explain how its getting confused and while an edge case also indicates a rather fatal flaw in the programming in that if the disk UUID cant be reliably displayed due to hardware limitations there is no fallback or fail over to default to using the drive letter. An example of what i call being too smart for it's own good where it tries to over complicate things and thus runs into problems such as this
- Accedi per poter commentare

Mike, if your synopsis above is correct due to using the port multiplier and 4 bay chassis, then this is a more unique scenario than the majority of users will have.
I can only suggest raising this via a Support Case direct with Acronis to get the developers to review this type of connectivity for backup destination drives and see whether they can accomodate this in their application design?
- Accedi per poter commentare