Hi all,
we are currently implementing a backup solution to back up our HyperV2012R2 Failover Cluster VM's. The VM's have their disks on a 2012 R2 StorageSpaces Server shared via SMB3. The 'file server vss agent' service is installed on the storage system.
The HyperV host has several nics.
-One 1Gbit nic for management. The Host is registered in AD with this nic and the DNS entry points to his DNS name 'server.domain.local'
- One 10Gbit nic for the SMB Storage traffic in another subnet. The storage machine has a second Name who points to the ip of the 10G nic 'storage.domain.local'
- Other nics for cluster communication and VM traffic
The VMs are configured with the 10G name of the storage server and everything works well with hyperv.
Everytime i try to back up a machine (via the Software or with the Shell on an Hyper-V Host via DISKSHADOW) there is the following error message:
--------
DISKSHADOW> add volume \\storage.domain.local\vms01\server01
The provider does not support volume shadow copies for this volume in this context.
You must either change the context or add a different volume.
Note that changing the context might cause existing volumes in the shadow copy set to become unsupported.
--------
When i use his AD DNS name it works:
--------
DISKSHADOW> add volume \\server.domain.local\vms01\server01
DISKSHADOW> create
....
--------
Am i missing something? Has anybody an idea what the problem could be? Do I have to register the second name or nic in the storage server system or in the VSS providers?
Thank you for any help!
