This is the next issue that arose after the previous post I made here, which was resolved. I am not sure they're related thus a new post.
On a Windows 2012 R2 server that acts as a hyper-v host, I am using the windows server backup wizard to define a daily backup of the hyper-v guests. The destination a network location - in fact one of the hyper-v guests...is that an issue? Because when I manually invoke the backup, it reports back immediately "windows backup cannot write to the backup storage location".
The host is not in the domain. The destination dir in on a hyper v guest that is the app server in a domain. The drive which holds the destination dir is *attached* to the guest, but it is a real hard drive not a vhd.
If it's not possible to back up to a network location that is attached to the guest being backed up, I can adjust how I do this. The message doesn't provide any detail. At first I thought it was an authentication issue, but I can create a mapped drive to the guest using the same credentials.