Direkt zum Inhalt

Changed drive letter prevents editing of an existing backup task

Thread needs solution

Using Acronis 6525 on Windows 8.1 pro x64 it is not possible to edit an existing backup task if the drive letter (physical or network) becomes different from the assigned one in the task.

So if the drive letter has changed you cannot edit the backup task and change the target of the backup.

This was at least possible in TrueImage 2014 and has been confirmed to be an issue by the support. Hence there is still no update for this issue.

Please fix, that you can change the target of an backup any time, even if the assigned target becomes invalid / inaccessible.

0 Users found this helpful

Previous versions of ATI were allowing the change of destination during a backup task execution. This was a mess. At restore time, ATI would ask for the files on the various drive letters that were used during the backup chain. That would make recoveries fail.

This is why you see the more experienced users:
- assign fixed drive letters to the USB disks (typically in the very last part of the alphabet) so that attachment of USB doesn't change drive letters at the whim of Windows UPnP,
- create new tasks when the destination of a backup needs to change (for example, alternating USB backup disks).

I am fine if you cannot change a drive letter during a task execution but this does not explain why it is not possible to change existing tasks.
The support said it is a bug as you can go into edit task mode but not save it.
That's how I see it too, so I request a fix.

- create new tasks when the destination of a backup needs to change (for example, alternating USB backup disks).

It is really annoying if you have to do this, if you use plans, complexer methods and settings you simply want to avoid this. Again it is a bug that you cannot save a task once a drive become invalid. Using drive letter replacement to A: or B: or the last letter is a workaround, true that, not a fix of the issue.

bumped because there is no official comment on this yet this bug still exists.