Problem when restoring back up
Greetings,
I have a network at work with a small number of PCs (say two A and B).
I got a new PC (say C) with lots of storage to store periodic back ups via the local network. We want all the work to be done automatically from PC named C with minimal configuration.
All PC run Windows 10 Pro of Pro for Workstations.
I tried the evaluation version of Acronis Cyber Backup but I face numerous issues.
To begin with I had to disable UAC (can you work without doing this?).
The biggest problem is that restore never works. I can back up total images and seperate files from PC A via network using the interface of Acronis Backup on a local location on PC C. When I use the choose on PC C to do a resoration on PC A it always fails.
The error is this
Error
Failed to open the backup location.
Failed to resolve the host name.
It is very vague. I don't know what I am supposed to do. Any ideas are welcome
Péter Szatmári wrote:Hello Georgios!
To begin with I had to disable UAC (can you work without doing this?).
UAC only has to be disabled for remote management of the machines, and only because they are not part of a domain. The workaround would be to install them normally on PC-A and PC-B
The biggest problem is that restore never works. I can back up total images and seperate files from PC A via network using the interface of Acronis Backup on a local location on PC C. When I use the choose on PC C to do a resoration on PC A it always fails.
This seems like a network configuration issue (see https://kb.acronis.com/content/61913), the error you posted also points to this. Does your router and PC-C have static IPs?
-- Peter
Thanks for the reply. The network is part of a larger work network and has not static IPs. The full error is as follows:
Error code: 46
Module: 64
LineInfo: 0xA1D3981537C68817
Fields: {"path":"file://ipreteaserver/d/Pavlou%20George/DESKTOP-A38Q5EC-AA6509C4-3D40-4A85-99A3-AC7836D33287-87E72402-43DA-4D9F-83E8-3114D6B440A9A.tibx","$module":"disk_bundle_glxa64_14330"}
Message: Failed to open the backup location.
------------------------
Error code: 46
Module: 64
LineInfo: 0x97675718D2B52D34
Fields: {"path":"\\\\ipreteaserver/d/Pavlou George/","$module":"disk_bundle_glxa64_14330","user":"admin"}
Message: Failed to open the backup location.
------------------------
Error code: 66
Module: 89
LineInfo: 0x28EDBBF5D246C484
Fields: {"$module":"nfs_supp_glxa64_14330","HostName":"ipreteaserver"}
Message: Failed to resolve the host name.
Hello Georgios!
Yes, however frustrating the vagueness of this error is, there aren't really more details to be added. You'll have to track down why the name of PC-A can't be resolved.
Some tips I do with this type of error:
- Ping PC-A from PC-C by hostname and by IP
- See if the ping reply comes from the same IP as the PC-A ipconfig output
-- Peter
Péter Szatmári wrote:Hello Georgios!
Yes, however frustrating the vagueness of this error is, there aren't really more details to be added. You'll have to track down why the name of PC-A can't be resolved.
Some tips I do with this type of error:
- Ping PC-A from PC-C by hostname and by IP
- See if the ping reply comes from the same IP as the PC-A ipconfig output
-- Peter
Thanks for the suggestion. I tried something more "drastic".
Using ipconfig /all I saw the IP, Sub, Gate, DNS and put them manually in ip4 settings in both PC-A and PC-C from my original example. The restoration worked as should.
I am not sure if by rebooting the PCs the IP will change dynamically since I am not sure how the networking works but after a reboot this does not seem to be the case.
Hello Georgios!
If you mean the window in my attachment, you've configured static IPs from a DHCP address range. You said the network is part of a larger one, in that case contact your network administrators and ask for an IP reservation or a static IP you can use. Otherwise you'll have IP conflicts when the same IP is assigned to a different computer.
These changes will persist across restarts, unless a domain policy overrides it.
-- Peter
Péter Szatmári wrote:Hello Georgios!
If you mean the window in my attachment, you've configured static IPs from a DHCP address range. You said the network is part of a larger one, in that case contact your network administrators and ask for an IP reservation or a static IP you can use. Otherwise you'll have IP conflicts when the same IP is assigned to a different computer.
These changes will persist across restarts, unless a domain policy overrides it.
-- Peter
Yes, I meant that I configured the window on the right in your attachment by giving specific numbers in all fields. I already asked for static IPs. Apparently it is forbidden which is inconvenient but understandable.
I have to look for a different solution now.
Hello Georgios,
thank you for posting on Acronis forums!
Since the restore went flawlessly when you manually enter an IP address, we advise that you create a Bootable Media with a static IP address (which is not used in your network) and use it for restore to workaround network issues.
We also recommend that you open a case with Acronis Support Team who will help you to identify the exact issue with your network by analyzing your restoration logs.
So I would like to pose a follow up question with more details.
Apparently the dynamic IPs on the network are from a central DHCP server.
What happens when I do full system restore via the client PC-C to another PC-A as described in my initial example what happens is the PC-A reboots in the Acronis restore program, stays there for a few seconds where nothing happens and the PC-A simply reboots without doing anything.
What I am afraid is that in this small time Acronis on PC-A doesn't even have "time" to connect ot the network provided that after rebbots Windows sometimes take even 20 seconds to connect ot the network.
Any additional ideas are wellcome :-)
Maria Belinskaya wrote:Hello Georgios,
thank you for posting on Acronis forums!
Since the restore went flawlessly when you manually enter an IP address, we advise that you create a Bootable Media with a static IP address (which is not used in your network) and use it for restore to workaround network issues.
We also recommend that you open a case with Acronis Support Team who will help you to identify the exact issue with your network by analyzing your restoration logs.
Thanks for this suggestion I will look into this.