Change backup destination

Please see KB 58004: Acronis True Image 2016: Troubleshooting Issues Related to NAS Credentials which should help you to clear the old NAS credentials and be able to enter new ones.

Hi,

Thanks but I have already tried clearing the credentials as per the kb article and I can create a new job using the new path just fine, but that’s not the issue, the problem is that the existing jobs path is wrong, but there doesn’t seem to be a way to change it?

You can remove the saved UNC path and credentials from Windows registry, then reconfigure the task destinatiion location to correct this.

You will find the registry entry at:\HKEY_CURRENT_USER\Software\Acronis\Connections\smb\

Locate the UNC path in the above key and delete it (path only not the entire key) from the key.

After delete the entry close regedit and reboot the computer.  once booted open the True Image app, select the backup task in the backup list, click on the destination location and select the new path and supply credentials when prompted.

After supplying credentials click on the Test connection button to test the connection.  Once connected the task should now run to the new location.

Hi,

Thanks, but that didn’t fix the problem, I found and deleted the key, rebooted, then opened TrueImage again and clicked the destination (it still prompts for authentication for the old unc path destination, I would expect it to allow me to browse for a new location, but this doesn’t seem possible).

In the destination screen at the top you should see the path. Can you enter the new path there then on the right side of the path box click on the arrow in the square box.  Does this change the location?

Though the suggestion below should not be necessary, it may be worth trying if the advice from Enchantech have not helped resolve this issue:

Open C:\Program Data\Acronis\TrueImageHome\Scripts and find the correct script file for your NAS destination backup task - hopefully this will be the most recent script file (date/time stamp).

Open the script file and look at the following section of the XML document to check whether the correct NAS UNC path is being shown or not.

<volumes_locations>
    <volume_location device_instance_id="" password="******" uri="nas://MyNAS/Backup/Dell/Win_full_b8_s1_v1.tib" username="xxxxxxxxx" volume_id="638918221" />
    <volume_location device_instance_id="" password="******" uri="nas://MyNAS/Backup/Dell/@task@.tib" username="xxxxxxxxx" volume_id="0" />
</volumes_locations>

The above is from one of my own NAS backup tasks so the information you see will be different according to your backup task name, NAS name etc..

Make a backup of the script file before attempting any changes to this information. 
I would advise to only try modifying the uri="nas://...  portion of the XML if any.

Hi,

There's no option anywhere to enter or change the path, all I get is this dialog which shows the path which I cant change :(

You need to look at the top of the GUI destination screen.  You will see a field in which the path is displayed.

Hi,

I edited the script and changed it to the correct path (three lines) I didn’t change anything else.

But its STILL asking for authentication for the old path! I've searched the registry for this path and its not there (at least as a string anyway), I’ve no idea where its reading the old path from?

As Enchantech wrote, you should be trying to change the path using the box at the top of the panel as the screen shot below:

If you are not able to do this, then the other option might be to try using the option to 'Add existing backup' and select the latest backup file from your new NAS location, then reconfigure this new backup with the settings you use for the original one apart from the destination.  You may need to remove or rename the original backup task before being able to do this as the file names will match that original task.

Hi,

I cant get past the authentication dialog, so I never get the 'backup to' location tree view, this is the problem.

The program must be reading the old path from somewhere no?

It looks like I'm going to have to start from scratch, reset and configure all my jobs again, not to mention run all my backups from 0. Which is insane, all I wanted to do was change the backup destination.

xer0w,

Sorry, had to leave this for awhile.  What happens if you click on Cancel, will that allow you to get to the backup location tree view?

I myself did this a few months ago as I reconfigured my network.  In trying to recall how I changed the path I am certain that I changed it by entering the new path in this way.  I am fairly sure that I did have to cancel out the logon credentials screen to do so.

You should not have to start from scratch to accomplish this, 

FYI. I added an entry to my local hosts file for the old hostname, I could then edit the job.

Glad to hear you have a solution, thanks for sharing the feedback.

Thanks xer0w for the hint. Had a similar problem with Acronis True Image 2019: I moved the nas in another location and was unable to change backup destination.
So I added to the windows host file the new nas IP followed by the path shown in the authentication settings (img on post #7 of this thread) and it worked again.

Thanks as well for the workaround. Though I must admit that it's pretty crappy for one ofe the best rated backup solutions to have to go to such lengths. Moving a backup and including an older backup from another location is definitely not something the overall very simplistic user interface will allow. try registry keys, script files an the windows host file - thanks, but no thanks.

Sorry Acronis. I've had to deal with this on a few occasions now for various reasons and I have to say it's ridiculous for a product of this caliber not to simplify such an essential function. I hope this is addressed in a future build. 

JamesAce wrote:

Sorry Acronis. I've had to deal with this on a few occasions now for various reasons and I have to say it's ridiculous for a product of this caliber not to simplify such an essential function. I hope this is addressed in a future build. 

Dear James,
thank you for your honest feedback, registered it as a vote for the change request TI-170272 Allow changing the plan settings when the target location is not available. 

A thank you from me too, and I wholeheartedly agree with the sentiment that having to jump through such hoops is disconcerting, to say the least. I simply changed my NAS and now I cannot use my existing backups unless I give the NAS the exact same name as the old one? I find that absurd. The same problem arises if I copy the backups to a local drive, it still looks for the files in the old network path.

Anyone knows if this has been fixed (because I can't help but consider it a bug) in versions 2020/2021 of TrueImage?

FF wrote:

A thank you from me too, and I wholeheartedly agree with the sentiment that having to jump through such hoops is disconcerting, to say the least. I simply changed my NAS and now I cannot use my existing backups unless I give the NAS the exact same name as the old one? I find that absurd. The same problem arises if I copy the backups to a local drive, it still looks for the files in the old network path.

Anyone knows if this has been fixed (because I can't help but consider it a bug) in versions 2020/2021 of TrueImage?

Hello FF,

thank you for raising this topic - indeed, it's not possible to modify backup plans, if the target location is not accessible, because the plan settings are stored in the backup archive, which requires the backup storage to be accessible for the product. I've registered your feedback as a vote for the existing change request  (internal ID for ref TI-170272)

Hello.

Register another vote please. For god's sake, I can't believe such an issue still exists in one of the best backup software.

Sergey wrote:

Hello.

Register another vote please. For god's sake, I can't believe such an issue still exists in one of the best backup software.

Hi! Added your vote, thank you!  

I also moved my hard disks from one NAS to another - data is literally the same, all that has changed is the NAS name - I was quite surprised that there was no easy way to point to a new location..

Please, I would like this feature to be added. I am not willing to do registry editing etc. to do something I think should be core to what otherwise is a very great tool.

Jonathan Ford wrote:

I also moved my hard disks from one NAS to another - data is literally the same, all that has changed is the NAS name - I was quite surprised that there was no easy way to point to a new location..

Please, I would like this feature to be added. I am not willing to do registry editing etc. to do something I think should be core to what otherwise is a very great tool.

 Jonathan, passed your feedback to the product management, thank you!

I have also changed my NAS, moved all backups to the new NAS and now I have to recreate all backups jobs from scratch?

This is utterly insane. Every other backup software in the world allows you to change backup path destinations.

Thomas Reimann wrote:

I have also changed my NAS, moved all backups to the new NAS and now I have to recreate all backups jobs from scratch?

This is utterly insane. Every other backup software in the world allows you to change backup path destinations.

Dear Thomas, sorry to know you encountered this limitation! I've registered your feedback in our internal system  

With all respect, Ekaterina, what is the point of logging this with your peers? It's been an outstanding issue for years now and they either don't care or don't see it as a problem. It's really a fatal flaw for most of your users who no doubt have migrated to other solutions where they can have this feature.

JamesAce wrote:

With all respect, Ekaterina, what is the point of logging this with your peers? It's been an outstanding issue for years now and they either don't care or don't see it as a problem. It's really a fatal flaw for most of your users who no doubt have migrated to other solutions where they can have this feature.

Hello JamesAce ,

I understand your frustration here.. Unfortunately, the current product architecture prevents some of the changes\fixes from being implemented even so they might look easy to fix. We document each and every feedback internally to have the updated statistic and to drive important fixes with the higher priority.