Backup fail due to Network share not being found (may not be share relatated it now seems)
Some of my remarks were around the direction of the article you linked more so than your comments - sorry I didn't make that clear.
I noticed from a wireshark log that only SMB2 is being used which surprised me. I know my NAS is quite happy with SMB3 and windows 10 should be.
I received a call from tech support which I thought was very personalised service. I've uploaded some specific wireshark and procmon logs with the Acronis system report. Included a link to this thread and updated my initial post for summary reasons. I'll see what they come up with :).
For the first time I have a new backup to a new location working. Will see if that translates into any persistent result. Earlier I was getting the same result of failure on an existing backup.
Will report back once I run a few iterations.
I would think that the existing backup would need to be reconfigured now, re-selecting source and destination for it to work. Hopefully that would do the trick.
Looking forward to further results.
so far it looks like no change :(.
same error. Same issue of only a single functional run before producing the error.
Hmmmm, not a good sign! Hopefully Support can find the problem.
yes indeed.
I'll likely have one last shot with a clean start and see what I can achieve now that the LAN setup appears more correct. Not holding out hope though as I think that since bonjour is seeing things on both that I'm dealing with a TI issue specifically.
mgrobins, I have asked our testers to replicate your use case in our labs and see if the backup failure reproduces (ref. # TTASK-23195). It would allow our Development Team fix the problem in one of the next updates. Thanks to the very detailed description, chances are high that we will reproduce the issue on our side.
I just have a few things to clarify the situation further and make sure our test environment, steps and test results will be as close as possible to yours:
1) does the backup fail only in WoL and 2 backup tasks scenario or the same error appears when a) the backup to NAS is the only backup that starts automatically?
2) does the backup fail the same way when you click "Backup now" button?
Quote: "Acronis scheduled to run daily backup on PC (local destination drive), then runs batch to activate 2nd daily backup task."
3) how exactly the second backup task is activated by a batch in the above quote?
THank you kind sir.
I have e-mailed responses to you with a detailed summary to side-step a lot of the forum discussion. Hope it helps and let me know please if you need more logs or testing :).
All,
I had some time over the last several days to take a big stab at this issue of always having to input the IP address of an NAS located on a secondary local subnet. What I found was quite interesting indeed.
Platform configuration:
ASUS motherboard with 2 Intel gigabit nics. i5 4690k CPU, 32GB RAM. Windows 10 PRO 1709 build 16299.371
Try as i might I simply could not get a secondary subnet to work on my test bed, a Windows 10 x64 PRO machine using just a Cisco gigabit managed switchfor the Secondary subnet. Windows 10 would not allow me to set that network as a Private network no matter what I did. This prevented me from connecting to the network period! I could disable the active Primary nic, use Powershell to change the secondary subnet to Private and make connection but, the connection exhibited slow response and intermittent connection. If the primary nic was re-enabled the secondary was once again changed by Windows to a Public network. I tried creating subnets in Class A B and C, all acted the same.
Finally I gave up and went looking for an old router I had put away. Finding that I hooked it up to my existing router and created a secondary local Class C subnet. So this configuration is:
Primary subnet: 192.168.1.1 (Network)
Secondary subnet: 192.168.2.1 (Network 2)
After a reboot of the managed Cisco smart switch the secondary was active and Windows readily connected. I went to Explorer and opened a Network view. Interestingly, other computers, and a USB HDD connected to my Primary (Network) router were visible but showed as connected to the Secondary (Network 2) subnet. The NAS which was physically connected to the Secondary (Network 2) was not viewable. I had to type \\NASname into the address bar of Explorer for the NAS to become viewable.
I decided at that point to see how True Image worked with this. I opened the app and setup a new backup task. True Image could not see the NAS either so I input the NASname into the address bar of TI and the device appeared shortly thereafter. I was able to select a share, create a new folder within that share, and successfully run the configured backup task to the new location without being prompted for credentials. The backup ran great. Total of 50.8GB transferred at an average rate of 631.8Mbps taking 7 minutes 44 seconds to complete.
I decided that now would be a good time to reboot the computer I was using here and see what would change. upon reboot Explorer exhibited the same behavior, no change at all. The only way to see my NAS device was via address bar device name input. True Image however was different. First thing I tried was a validation of the newly created backup. That ran without issue sans a slight delay in starting which is normal behavior. I thought I would setup another new backup task to see if the NAS now appeared in the Destination folder. First thing I did though was to just click on the Destination folder. When that screen opened my NAS was showing under the NAS folder. What was not showing under that folder which had been previously was my USB HDD connected to Primary Network router! This device now appears under the Browse\Network folder. Configuring a new task went without issue and selection of the NAS device was not a problem at all.
Conclusion:
For subnetting to work correctly a router is necessary to route traffic between separate subnets and avoid collisions and connection loss. Basic networking 101 here.
Since a validation task was run to conclusion on a previously created backup without pointing the app to the location of the backup on the local network indicates that if the network is properly designed and configured there is no issue. This backup is a weekly differential scheme so I will verify that the next differential does run but I will say that I fully expect it to do so.
I do think there is some issue yet with device discovery here. I was very surprised to see that my NAS and the USB HDD had exchanged locations in the Browse screen of the TI app. I believe that as my devices are currently configured they should appear in both places, not one or the other, and certainly should not change like reported here.
Interesting :)
Perhaps you can try my initial setup and see how it pans out.
PC to NAS through unmanaged switch and router/gateway (192.168.1.x / 255.255.255.0)
PC to NAS direct link no gateway/router. IP / 255.255.255.0)
See what is visible in the network and NAS tabs of TI. using IP not NAS name run a backup and then after NAS and PC rebooted try and run it again.
I'm in hospital so cant keep playing around with this but the support from Acronis have yet to nail down a cause either even after extensive logs and messing around.
As I said, it is not possible to get Windows 10 Pro to accept the configuration you had/have. I cannot explain this except to say I suspect it is due to SMB/Network security concerns and TCP/IPv4 Protocol itself. It is necessary to have a router in the mix to get Windows 10 to play nice with two subnets. If it turns out to be an issue with having both nics on board rather than one on board and one via PCIe I would be quite surprised given that MAC addresses are different for each independent nic no matter what.
It appears to me that Windows is itself, largely at play here. In my case, Windows will not keep the secondary network as a Private network unless it has gateway access via router. If you remove that segment Windows immediately will change the network to a Public network and the connection becomes inaccessible. I believe this is also due to the fact that TCP/IPv4 requires a gateway to function correctly and Windows enforces this via this Private/Public network setting.
Sorry to hear of your hospital confinement, my best wishes to you in a speedy recovery.
Interesting given all of my other software works fine with it - Including TI 2016 ....