Skip to main content

I WANT Acronis to forget networked drive and it won't

Thread needs solution

Hi,

My issue seems somewhat opposite of what others are experiencing with mapped drives. I absolutley WANT Acronis to forget my mapped drive and it won't.

I have a network location (SAMBA to a USB3.0 drive hanging off my ASUS router) that was once mapped as the Z: drive. I've stopped using this reference, yet everytime I navigate to this location and change the job's config using a \\networkname reference, at runtime Acronis complains that it can't find the Z: drive. I've successfully used the \\networkname reference fine on other backups jobs. This one will not let go of the fact that it once used the Z: drive reference.

The Z: drive is absolutely not mapped, I've rebooted to prove it is no longer on my system, I've searcched the registry and no references, yet every time I navigate to the required network backup location, at runtime Acronis thinks this is the Z: drive. I've even changed the job to a completely different location, saved it and then changed it back to what I want, it keeps thinking this is the Z: drive.

I've even enabled my router to present this folder through FTP and created an Acronis FTP location. It all connects and authenticates fine, but when it runs it again complains that the Z: drive is not found.

Where does Aconis store these backup location settings so I can attempt a hard override? I didn't see it in the registry or any config file on disk? It's as if the folder location is cached somewhere as Z: ? I'm running Windows7, could it be stuck in the O/S somewhere?

I'm being a bit stubborn here since I want Acronis to work as it should. And, everytime I have small issues like this I have to delete the job, create a new one, lose my backup chains, and start all over. Getting pretty frustrated with my upgrade to ATI 2015.

Thanks for any help you can lend,
Steve

0 Users found this helpful

I cannot say where the information is stored, but you have pretty much only the choice you are having: delete the task and create a new one. Before you delete the task, you can move manually the existing TIB files to another directory for safekeeping, and delete them manually when you assess it is time. I would recommend against bringing existing TIB files into a new task, although the product allows for it when you choose "add backup".

So am I misinterpreting the error message as it cannot find the location for a new version file, when it is really saying that it cannot find the previous version to link onto as a chain? So it insists all versions should be in the same referenced location?

I think your last summation is correct. This is due to the fact I believe that the app is task specific. In other words once a task is created the parameters of that task lay out the specifics so when those specifics are broken so is the task and any subsequent usage of the task produces errors.