Network Drive Support
I wonder if y'all are trying to push more cloud storage by crippling support for backups to network drives.
Update five machines to 2017 and none would back up to network drives. In frustration, bought an NG license and it does.
Search the help database here and it says removing support for network drives in 2017 is a "feature" not a bug. But y'all put it back in NG.
Doesn't seem like 2017 is a smart upgrade for folks. You just lose your ability to backup to network drives and gain nothing.
I understand that NG is another matter, but sure wish I hadn't bought five 2017 licenses.
This is not a customer-friendly way to move, and it will just encourage new competitors, just when you've driven most of the old ones out of the market.
Sad.
Futher to Steve's comments, a new build of ATI 2017 for those with a perpetural licence is only a couple of weeks away (according to a post dated yesterday in another thread).
I am running build 6116 and I am not having any issues in backing up to my Synology NAS.
Ian
I recently purchased a 5 license version of Acronis TrueImage (ATI) 2017. I wanted to make a backup of a disk on my desktop across my network to my linux server. I mounted a drive specifically for this purpose in a directory that is already set up in Samba for temporary use at my desktop. There are no issues using this directory for any other purpose. I've been doing it for years.
When I attempt to configure a new backup in ATI 2017, it sees the server, but when I try to select it, it asks for credentials. I enter my Samba username and password, and it rtells me the "Connection Failed". I enter the username and password for my user account on the server, and it again tells me that the "Connection Failed." I enter the suername and pasword for my account on my Windows desktop, and it tells me, again, "Connection Failed."
I then try to cvonnect using a mapped drive to my desktop. Acronis sees the mapped drive, but won't let me drill down to a specific folder on that drive. So, I try to make a backup just using the root of the mapped drive, and it tells me, "Failed to check credentials."
So, I'm nowhere in terms of using Acronis True Image 2017 with my network. It seems to work using local drives, but I cannot do anything at all if the network is involved. Any advise would certainly be appreciated. I've tried all the credentials I have, which work with any other procedure I'm trying to accomplish on this network.
For Donald,
The kb articles suggest you can get around this by using an IP address or servername to access your network drives.
For the MVPs,
Acronis no longer reveals the version number when you're downloading an update. How does one know they are getting 6116?
Thanks Michael,
I read that too, and tried both. Didn't work.
Finding the build number: It depends where you look. I you go to www.acronis.com and follow the links you get to this page, where the lasest build for each Acronis product is listed. There are two downloads for True Image 2017, one for ATI 2017 New Generation (it is not made clear that is a subscription product) [build 6116] and other for True Image 2017 [build 5554]. If you log into you account and then select 'download' you get this page, which give a selection between the two versions of ATI 2017 but no information on the build number.
At some stage the build numbers for the two version will hopefully coincide and will have a unified installation file.
If you have a downloaded an installation file, you can find the build number by opening windows explorer, slecting the installation file, right click and select "properties" and then select "details"; the buld number is the Product Version. Currently the installation files have different names, one include "NG" in the file name.
Ian
Donald,
I too have an issue with a network drive that behaves just as you describe. What I found to work was to first logon to the network drive using Windows File Explorer then once connection is made close Explorer, open True Image and create a backup with the network drive as the destination. in my case when I do this True Image no longer asks for credentials, it let's me select the folder I desire and proceed with the backup no problem.
Success! I started from the bottom and worked my way up. Opening in Windows Explorer didn't work, but I have to admit that I've used that technique on occasion when I couldn't get my Lightroom to recognize my network drives.
Next, I used Ian's procedure to determine the build number, which was 5554.
Based on that, I used the patch suggested by Steve Smith near the top of this thread. While the program still asks for authentication, the credentials work this time and I was able to direct it to the specific directory on the server where I had the backup drive mounted.
It's backing up now, and I'll try my wife's machine when it's done.
Thanks a lot guys. It really helped.
Donald, thanks for the feedback and good to hear that you have been able to get this working to your network drive.
Great news. If you shutdown your computer and upon restart and then attempt to run a backup you face the same problem logon with File Explorer first as that usually fixes the problem.
It's a bit of a "compromise" to have to jump through the hoops, but this particular backup is not something I will do automatically anyway. I don't mind a bit. I have daily, automatic backups on my server using rsync, then these happen every week or so, using Acronis. I have to physically mount the drive for them anyway, so it's all part of the process. Thanks again.