Direkt zum Inhalt

Network Support in Universal or Simple restore?

Thread solved

Has anyone been able to get either Universal Restore or the simple restore working with network support? My backups are on a NAS and there is no way to recover them that I can find. Nothing I've tried, and I've tried every combination comes up with network support. This looks like a serious limitation to me.

0 Users found this helpful

Glenn, welcome to these public User Forums.

First, to deal with the purpose of Universal Restore - this is not intended to be able to connect to your NAS and restore a backup image.  Its purpose is to be used after such a backup image has been restored via the normal rescue media, and then AUR is used to prepare the OS that has been restored by identifying any changed hardware devices and substitute generic device drivers for these where available, else to ask the user to provide device drivers.

See KB 65413: Acronis True Image 2021: Restoring to dissimilar hardware with Acronis Universal Restore and in particular review Steps 4 and 5 of this document.

Also KB 2149: Acronis Universal Restore

KB 36187: Windows activation required after restore with Acronis Universal Restore, cloning or converting backup to virtual machine

KB 45432: Acronis Software: Troubleshooting Universal Restore and Bootability Issues

KB 46405: Acronis True Image: Restored Operating System Fails to Boot

For the regular Acronis bootable rescue media, the recommended option is to use the 'Simple' method of creating this as this will use the files and drivers found in the Windows Recovery Environment on your PC and can then allow for networking to work.

One key limitation of working in the stand-alone rescue environment (after boot the media) is that there is no DNS support, so you will probably need to use the UNC notation for your NAS to be able to connect to is.

\\192.168.0.29\Folder  instead of using \\MyNAS\Folder

You can test whether you have any network connectivity by trying a simple Ping command to the network address of your NAS or router etc.

It is also possible that if PING works, that you could map a network drive to a drive letter from the command prompt.

net use N: \\192.168.0.29\Folder /user:MyName password

See webpage: How to Map Network Drives From the Command Prompt in Windows

And KB 58000: Acronis True Image 2016: Troubleshooting Issues with NAS Devices - which still applies to later versions.

Well, THAT was really helpful. The background explaining that WinRE is used to build the media was the key to my happiness. As luck would have it, I don't have the recovery environment on my current box. That will be addressed shortly. Then I hope I will be able to migrate to my new system disk with minimal trouble.

BTW, I actually did get the basic recovery gizmo to work in the WinPE environment by adding all the drivers that seemed germane at the time I added them. There are probably 20 drivers it doesn't need but the network worked well enough to get me back on the air.

FWIW, a couple of comments on my experience:

First, all the support people say to use the Linux version rather than the Windows version. I couldn't get the network working there and I do have some Linux experience.

Second, I'm sure I could have learned a ton by reading the articles you mentioned above. But I had no way of knowing those articles even exist! I suppose it's reasonable to have  the view that "nobody reads the directions anymore", but I think these tools are not real well documented. I would never have guessed at the intended use of AUR as explained above  by reading the scant info available from within the main Acronis app. I've found that to be true elsewhere in various operations. My experience so far is that it doesn't "just work", which is OK, but problem are not intuitively sorted out. 

Anyway, thanks for all your help. I sincerely appreciate it!   Glenn....

Glenn,

The MVP community here on the Forum are trying to find ways to FIX the ailments you point as well as others that exist.

As for Support suggesting to use the Linux based recovery tools, that needs to stop as the Preferred Method of recovery has been WinPE/RE based for the past several years.  Chalk this up to communications failure between Development and Support.

Nonetheless, glad to hear you have your issue sorted.  Don't hesitate to check in here if you have further issues.