Change destination of backup after IP change
I backup to a local NAS as well as the Cloud. The NAS was selected using an IP. I had to redo my internal network and so the IP address needed to change. Acronis still thinks the backup should go to the old IP address. I managed to update the .tis file in the scripts folder and the GUI now shows the correct IP address for the backup however when it tries to authenticate it still tries the old IP address which fails. I haven't found any other place or file to change the IP address. When trying to select the change location option it first requests the authentication credential against the old IP address so doesn't allow the destination to be changed (this seems like a bug to me).
Any help appreciated. Thank you.
Hi Steve,
thank you for the welcome. I opened the link you suggested and I had such high hopes but the suggestions do not work.
I don't won't to create a new backup task since as it is just an IP change I figure there has to be a way to update this.
I went into the registry and deleted the smb key. Even after a reboot the authentication box I get shows ATI trying connect to the old IP. I can't click options or change destination without getting the authentication prompt, and that's always against the old IP so of course it won't connect, and then eventually all I can do is cancel or ignore, and ignore give me a failure message. There is a place somewhere that ATI is storing the old IP but I can't find it, either in the registry or in the ATI files. Perhaps the IP address stored is transformed in some way that ATI can read but then it makes it impossible to see it to change it. Any other suggestions?
This is the persistent authentication against the old IP:
After updating the .tis file and deleting the smb key the updates are correct:
since there hasn't been any more explanation nor help in the last few days I'm posting a fix that I managed to do in the hope that it might help someone in the future, if they search for a similar problem - or perhaps some of this advice can make it into the solution documents that were posted above.
What helped for me was to
1. map a drive to the NAS folder holding the backups
2. open the backup with Acronis by right-clicking the backup and choosing one of the Acronis options
3. Acronis seemed to recognise it and after putting in encryption password opened the backup.
4. Then I closed that window first, or restarted Acronis first, or straight clicked on the NAS backup options (can't remember) and this time it did not complain about the 192.168.1.9 address. I'm guessing that somewhere the internal pointer/reference was updated.
Still, the original instructions/solutions did not work. There seems to be another place the reference is kept besides the registry and the .tis file (perhaps in the backup itself?). This seems like a bug or bad design which at least is not remedied by the current instructions.
Gerry, thanks for sharing your solution to this annoying issue, glad that you were able to resolve it.
Hello Gerry,
Thank you for bringing up this topic! Would it be possible for you to reproduce the issue and then send us the diagnostic information via the Feedback option in the product? Then I'll pass the log files to the development team for analysis. Thank you in advance for your time and cooperation!
Ramz, great work and thanks. I had the same issue after modifying the destination IP in the tib.tis file. Never would have thought to open the destination and use the right-click context menu. Indeed, it updated the destination IP and allowed me to resume backups.
The other solutions (clone and recreate; delete and reconfigure) were wretched.
The ability to change the destination IP addressing should be core functionality.
Cheers.
Hello Joshua83702, I've passed your feedback to the product team, thank you!
Many thanks to Ramz for his method a few posts above - it works a treat.
Could not find ANY other solution that solved the problem - thanks for nothing Acronis support!
I had a disc go south on my 4 bay QNAP and thought I would be clever and transfer all the stuff I needed on to a large portable drive so I could replace the disc in the NAS and then reconfigure it at the same time before putting the files back from the portable backup.
All went well until I could not edit the path to the Acronis backups on the NAS?
Just to clarify,
1) Map your NAS drive to a drive letter in windows explorer
2) From here right click on the backup file on your NAS and select open - leave it open for now
3) Open TIH and you should now see your backup at the bottom of the list under "other backups" - if you select it you will see that the only option is to "reconfigure".
4) Before you do so I would suggest that you select the old version of the backup, from the top list, and select "Delete" and "Remove from list" ONLY
5) Then you can reconfigure your new version and set all the options again (they will have defaulted) - whereupon your new "other backup" magically moves back up to the top list to replace the one you deleted from the list - back to square one - blimey what a rigmarole!
6) Go back to win explorer and close the window showing the contents of your backup. You can always un-map or disconnect you mapped NAS drive if you no longer need to see it listed in explorer.
I had 3 different backup plans so I just repeated the above with all three and I have subsequently run and validated and all went according to plan.
Obviously an oversite by Acronis as you CAN change the location of a normal backup - in fact for USB drives it seems to find them automatically when Win has assigned a different drive letter - BUT for existing backups on Network locations, even though it offers "Change Destination" when you hover over the location backup icon it ONLY allows you to specify and test log-in credentials and NOT the path so obviously this always fails as the stored path is now incorrect!
This seems to have been a problem for a long time now (years?) so it would be nice for Acronis to sort it out ready for the next time someone might want to reconfigure a NAS with backups on it.
glad this has helped Joshua and Nigel and thank you both for posting. Maybe it was fixed in the newest version. I don’t know as I’m still on 2018 but I recently received a suggestion to move to Veeam Free Community edition as that supports backup to several clouds. It’s a pity since overall Acronis has worked very well and I’d definitely stay and probably upgrade but it’s 2020 and lock-in to one cloud provider is no longer acceptable. If Acronis Cloud is competitive enough it will be chosen, if not Acronis faces irrelevance in the future.
No, it is NOT fixed in the new version - I am on 2020 and all up to date!
That is the one thing Acronis are good at - they keep prompting you to buy the new version even though I have a perpetual licence (no cloud for me) and if you judge it just right and accept the offer when it has dropped in price enough you can get a reasonable deal. I got a 3 PC upgrade licence for less than £15 which was just what I needed.
Anyway, thanks again.