ATIH changed the path to my NAS???
This is actually for ATIH 2019, but posted here for urgency.
I don't check my backups that often. But I did today.
At the end of May was my last successful backup.
After investigating, it appears that Acronis added *.HT.HOME to my NAS path.
Instead of my NAS path being \\Storage\Backup
Acronis changed it to \\Storage.ht.home\Backup
The revised path doesn't work.
I can't edit the script, because the first thing Acronis wants is for me to log in to the NAS.
Any hints on how to fix this problem. I leave for holidays tomorrow, and I kinda want my laptop backed up before I go.
Yes that works, but results in a full backup, not an incremental one.
The problem still exists. When with ATI decide to corrupt the path in the new task?
BrunoC wrote:Roy, have you tried to just create a new backup task from scratch rather than trying to modify what's there?
Roy, I have been helping in these forums for many years along with being a NAS user myself (using a Synology NAS) and I have never encountered an issue as you have described with the path to the NAS being changed / extra path information added.
If this is an Acronis code issue in ATI 2019 then you are the first user to report it to my knowledge, and unfortunately as you are well aware, Acronis is not providing any support for any version of True Image as used by users with perpetual licenses. The issue would need to be reproduced using the latest version of ACPHO build #40338 in cooperation with Acronis Support to collect diagnostic data. The downside being that ACPHO is a subscription only product unless the issue can be recreated within a 30 day trial period, along with the simple fact that Acronis would not port any remedy back to older True Image versions.
Returning to the original issue...
One option instead of creating a new backup task that will definitely start off with a new Full backup image, would be to use the option in the ATI GUI to 'Add existing backup' - that option is hidden behind a caret 'v' to the right of the obvious + Add backup (for new tasks).
Using 'Add existing backup' will open up a navigation window that will allow you to navigate to your NAS location where existing files for the original task are stored, then to select the most recent of those files.
Note: before doing the above, you need to first remove the settings for the corrupted task by clicking on the Delete option, then remove only the settings. This is necessary as information for that task and its associated files is stored in an internal database.
When the 'existing backup' is added, then it will generate a new task in the GUI using the selected file, i.e. my_backup_inc_b?_s?_v1 that you can rename to remove the extra characters while keeping the original stem file name. The new task will still need to be reconfigured for the Source selection and Options settings, so make a note of these if needed before removing the original task settings.
Roy Jensen wrote:Yes that works, but results in a full backup, not an incremental one.
The problem still exists. When with ATI decide to corrupt the path in the new task?
BrunoC wrote:Roy, have you tried to just create a new backup task from scratch rather than trying to modify what's there?
Roy, yes you would get a new full backup, but if your last backup was in May wouldn't you want to start with a new full backup?
When you say the problem still exists, do you mean the name is changed again in the newly created task? If that is the case, my initial suspicion is that it is something on either the NAS or in Windows. I use ATI 2019 with a Synology NAS and have never seen anything like what you are experiencing.
As a diagnostic aid, you could grab the MVP Assistant (link in my signature below) and go to the Acronis Configuration page. From there you can see the backup tasks and scripts associated with them. You could monitor to see what action may cause the change to occur.
Roy, are you running ATI on a MAC?
First search made me think is was a MAC thing, but additional research seems to point to the possibility that you have a "Connection-specific DNS Suffix" of ht.home which may have come from something you did last May. Something done in Windows? Something done in MacOS? Something done in your router?
At this point I suggest just doing a Google (or whatever engine) search for Connection-specific DNS Suffix and it will hopefully lead you to a solution.
At this point I suggest just doing a Goggle (or whatever engine) search for Connection-specific DNS Suffix and it will hopefully lead you to a solution.
Bruno, that is very interesting and something new to learn about!
Webpage: How to configure DNS suffixes on Windows - looks to offer one method of this being done!
It also can be set using Powershell ...
Set-DnsClient -InterfaceIndex 12 -ConnectionSpecificSuffix "corp.contoso.com"
So there are probably a number of sources of where this could arise from.
Just a theory... there is an app called HT Home from Hundai which is used for home devices such as security cameras, etc. I'm thinking perhaps Roy installed some device and software which caused the DNS suffix to be placed in the configuration. I did find a few posting on some other forums where people had ht.home installed as the DNS suffix, but I could not find enough detail to confirm my theory.