Skip to main content

Recovery thumb drive utility cannot find the backup files on my NAS

Thread needs solution

I've created an disk image file on my NAS and created a True Image 2019 recovery drive but when I boot from the drive and try to access the image from the menu option for NAS, the GUI utility cannot find it.

Any help would be appreciated.

0 Users found this helpful

Ian, welcome to these public User Forums.

How are you connecting to the NAS when booted from the Acronis bootable media?

Most of the rescue media has very limited support for wireless adapters so you should be using a wired network connection.

See the following KB documents that may be of help here:

KB 57992: Acronis True Image: NAS Is Not Detected - this has a section dealing with rescue media.

KB 46015: Acronis Bootable Media: Troubleshooting Network Browsing Issues

KB 58000: Acronis True Image 2016: Troubleshooting Issues with NAS Devices

KB 58004: Acronis True Image 2016: Troubleshooting Issues Related to NAS Credentials

Hi Steve. Thanks for the response, but no matter what I try The NAS is not detected when  I boot from the USB drive. I fear I have wasted my money on backup software that I can't recover with. Disappointed.

Ian, sorry to read your update on not making any progress!

Which type of rescue media are you using here?
How are you connecting to your local network?
What NAS do you have?

Hi Steve

Rescue media is a Toshiba 16GB thumb drive.

Connection to the network is Cat5e to the NAS via an Asus RT-AC86U modem in router mode and a ISP supplied cable modem router (that I use to admin my 2.4Mh wireless devices).

The NAS is a Netgear Pro 6 of mature vintage. It's no longer supported by Netgear.

I have to say, nothing else on the network has any problems read/writing to/from the NAS.

Ian, thanks for the further information.

Which version of rescue media have you created on your Toshiba 16GB thumb drive?

Also which version of Windows OS is involved here?

For the rescue media, there are 3 different versions available:
Simple:  created based on your Windows Recovery Environment for WinPE media.
Advanced: created based on Windows ADK (or AIK for earlier OS versions) - WinPE media.
Advanced: created based on a small Linux distro OS (BusyBox).

Given your statement about your NAS being of mature vintage, you may want to test using the Linux media provided your computer hardware does not include any devices that Linux does not support.

@Ian Garthwaite, I have a similar configuration to you. Have you tried manually inserting the device name - I sometimes have to do that to connect to my 4+ years old Synology NAS. In my case:

//DISKSTAION/homes

seems to do the trick.

Caveat: I have not tried if for a while from the recovery media - I use either WinRE or WinPE (create by MVP tool).

Ian

Ditto to Ian,

Since OS's keep updating security (including the preboot /  rescue environments), things like earlier versions of TLS and SMB are being turned off by default.

In the rescue media, the easiest method I find in my setup to my NAS is to just start typing the NAS IP (that way DNS isn't involved either.

such as:

\\192.168.1.X\

Usually, when you hit the \ after the IP, you'll then be prompted to enter credentials and/or it may even display the shared folders just before the credential window.

When using the ATI GUI under network or NAS, it is hit or miss that it will actually find a certain networked device, but the direct IP method has been nearly flawless (in most cases).

Still no luck!

I've tried inputting the IP of the NAS in the file location field. Unsuccessful.

Oddly enough, if I use the GUI when booting from my thumb drive, the entire network and not just the NAS isn't seen.

Yet if I close the GUI I can ping the NAS and get a return as you would expect.

I cannot use the shell if the GUI is active, at least any command I type in isn't visible but inputs become visible when the GUI window is closed(even the gibberish that I typed to see if the window was in focus prior to GUI closing :) ).

Just to clarify, none of the backups are invoked from the thumb drive they are automatically generated from the desktop app at a specified time and are incremental. I know everything is as it should be as I get an email report every day and can browse to the timestamped files on the NAS from my PC.

Ian Garthwaite which version of the rescue media did you build?  Could you check to see if there is a source folder on the root of the drive and boot.wim in it?  Curious if this is the Linux rescue media, WinPE rescue media or WinRE rescue media. As you apparently have a network connection (since you can ping the NAS), it should be possible  to map the drive, but different security settings of network devices will determine what can be seen and how, based on the type of rescue media built.

I would first try the WinRE (simple rescue media method in the media builder tool in Acronis True Image) and check for boot.wim on the usb drive when it's done completing.  This would build rescue media based of your installed OS Windows Recovery partition and include local system drivers already in your main OS.

As for mapping the NAS, there are various options to try.  One of them may be to use command prompt and "net use" to map it as a drive letter.  I rarely can connect to a network resource in Acronis using the "network" dropdown and only some NAS devices show up when you select the NAS option.  If permissions are correct on the NAS, you should always be able to input the full NAS IP AND THE FULL share path and be prompted to enter credentials... NAS behavior is different here though, so be prepared to know and enter the full path to your backups...

i.e.

\\192.168.1.x\Acronis\Backups <enter>

username / password

Also, if you haven't tried the MVP rescue media builder - I'd recommend giving it a try and building WinRE with it.  It does everything the default Acronis tool does, but adds lots of other tools like a file explorer (which makes mapping drives with explorer ++ or A43.exe even easier through a GUI), and things like that.  

Hi lan,

i agree with you definitely,

I am newbie to this form, btw. sorry for my English not so good but... i bought ATI 2019 two weeks ago and still struggle with this limited software and recovery media thing. i really disapointed, so

1- I have advanced license with cloud for 5 computers, i have try 10 times for recovery media and used 16gb sandisk thumbdrive i try all options; winPE basic, advanced (injecting drivers) etc.

I have 3 different computer which have 2 of them running win 10 and 1 is Win 7 but ATI 2019 not able to detect NAS even whole network then İ decide to create Linux based media and strangely it worked with network support, detected NAS even it does not have drivers but it was limited then WinPE.

 

2- I have also 13" UX360 flipbook with screen resolution 4K, running Win10 and i setup ATI 2019 and imaged it then i need to be sure if i able to recovery with recovery media? Surely NO...

it does not detect NAS and Network, also i blind to see the UI because the resolution was very high and letters on screen very small.

I start to research in KB. on Acronis site found that https://kb.acronis.com/content/3836 but disapointed again;

this is just for ATI 2010-2011 releases and not working with ATI 2019 then i decided and wrote to Acronis customer support again and again 3 or 4 times.

Solution: Nothing

Verdict,

It is truely frustration, I regret buying this product

I have used a dirrerent backup and image software 30 day trial (MR) and was really happy with it even working recovery media flawlesly but what was the reason for buying ATI2019? as an old Acronis user... i thougt it has acceptable backup security, good options for backup plan and customer support,

but i was wrong...

just an addendum to Ian's comment.

I exited the menu and did a 'net use' to map a drive letter to the NAS, which I could ping. Then went back into the GUI and I could restore from the new drive letter

JC