Please help: VMWare Guest backup to host share
Question: In VMWare workstation, how to backup Windows guest to a VMWare shared folder?
I use Acronis to backup Windows guests in VMWare workstation. In older versions, I was able to do so by typing the location in the "Back up to:" input box, like "\\vmware-host\Shared Folders\Backups\Acronis\". Now I upgraded to 2018. True Image 2018 does not see the shared drives even though they just work fine at Windows. I am first prompted for password, then get a connection failure.
I have upgraded 3 WIndows guests, all same result. Uninstall True Image 2018, reinstall True Image 2015, work fine again.


- Log in to post comments
Did Mr. X or anyone else ever resolve the issue Mr. X reports?
I, too, find that a VMware Windows 7 virtual machine (guest) running Acronis TI 2018 and now Acronis TI 2019 cannot back up to a VMware-host\Shared Folders destination. A dialog demands authentication credentials (that I provide) and then fails, irrespective of whether I specify the destination as a UNC path, e.g.: "\\vmware-host\Shared Folders\AcronisTI2019\MyVM" or as a mapped drive that's been mapped within the Windows 7 virtual machine's operating system, e.g.: "H:\".
On the host's Windows 7 OS, I've granted "Full Control" privileges to "Everyone" (though this should not be necessary, as a user within the guest VM can write or edit any file it wants without the need to specify any credentials).
This problem renders Acronis True Image useless to me unless I can resolve it. Any tips?
- Log in to post comments

I don't have 2018 to test with, but try to play with this with 2019 later today. I don't have issues mapping from the VM into my NAS or primary PC shares from the VM, but haven't tried the other way around to backup from the physical PC into a VM share before.
One thing I'm wondering about (although if it works in an older version and not 2018, maybe it's not the issue)... Is the physical machine already mapped to that device using different credentials? For instance, if your physical machine has a mapped drive to the VM in Windows Explorer to one share with credential #1, Windows has a limitation of mapping to share #2 on the same device (at the same time) when different credentials are needed. This is actually a Windows limitation though. Again, if not and working in 2015 and not 2108, probably something else, but wanted to bring up the possibility.
Also, just curious, but how is the network adapter of the VM machine configured? Is it using the physical computers network adapter with NAT, or is it configured to show up on the network as it's own separate node (with its own IP address). Asking to make sure that the VM Host is maintaining a static IP address (or dhcp reservation) that isn't changing.
- Log in to post comments
Hi, @Bobbo_3C0X1 ,
Thanks so much for your reply and your thoughts!
I had mapped a drive letter to that location from within the VM, but -- upon discovering that Acronis TI couldn't use a mapped drive -- I deleted that mapped location.
I'm using NAT for the vm's connectivity to the host's network, so my vm does not have a static address.
I'm using VMware workstation's built-in "share" capability to the host's drive, rather than a proper network share, as my host machine has company policies that forbid sharing folders on a local network. The very user who's operating the Acronis interface can read and write files to the share, directly, with no authentication issues.
It did just dawn on me that Acronis's service that's attempting to write to the share is likely not operating under my local user credentials -- that may explain why Acronis is demanding credentials to access the location?
- Log in to post comments

Yeah, Acronis usually uses the credentials that launched the app. However, for network shares, you usually provide credentials for that in the backup task. If it's on a domain, you may need to enter the share as
Domain\username
or if it's in a workgroup...
Computername\usename
I've not tested the VM setup your using since you can't create network shares. Where is that setting at so I can test later?
Also, what about using the default hidden Microsoft admin share with $?
Example...
\\computername\c$
Maybe not ideal, but that's how I've gotten around not being able to create shares as well, so long as I can connect with my admin credentials
- Log in to post comments
VMware shared folders setup:
VMware Workstation Main Menu -> Settings ->Options -> Shared Folders ->Add -> provide name and path -> Click "Enabled"
Attachment | Size |
---|---|
489132-164094.png | 103.43 KB |
- Log in to post comments

Thanks iLDavo! Funny I never even noticed that option before. I just never really had the need since my VM's are typically the ones connecting to my local shares at home instead of vice-versa.
I didn't have a chance to play with this yet, but hope to this weekend.
- Log in to post comments