The 2 node HyperV Cluster along with the VM's is already in place and I am doing a SMHV config.
I did create the shared snapinfo and dedicated report LUNS for each host using SnapDrive 6.2, but the CSV with VM's already existed.
SMHV keeps throwing these vague errors about licensing!
When I move all VM's to a single host and create a dataset of all VM's , then the backup is successful from each host. ( Which means that both hosts see the SMHV filer license )
However, when the VM's are owned by 2 nodes and are in a single Dataset, then the backup is successful on the node that I execute the backup from and fails on the other with license error. Is it by design that the SMHV backup is redirected to each host that owns the VM's even tough the all VM's belong to a single CSV?
Also, when I try to create a schedule, it fails in the last step when it tries to create the schedule for the other host with a credential error.
I tried SnapDrive and SMHV with local admin users and also with Domain users.
Not sure what the issue is. I have 2 support cases open for 3 weeks but to no avail.
Also I am not sure if you saw this in our release notes
You need to install SnapDrive for Windows on all hosts before installing SnapManager for Hyper-V.
If the hosts are members of a cluster, all nodes in the cluster require the installation of SnapDrive for
When SnapManager for Hyper-V starts it communicates with SnapDrive for Windows to get the list
of all virtual machines running on a host. If SnapDrive for Windows is not installed on the host, this
API fails and the SnapManager for Hyper-V internal cache does not update with the virtual machine
You might receive the following message:
Error :SnapManager for Hyper-V is not licensed on the host or in the Storage
System, backup is aborted:
The credentials issue can be because communication is not happening properly across the cluster so please check the cluster config too. Also in a cluster environment you should be using domain user and not local user.
So in the SMHV configuration did you add the cluster name? If the cluster name is added you need to give the domainname\administrator ( for all CSV. Cluster configurations). For a dedicated host a local account should be fine. I think you should also check the cluster configuration once to make sure that communication between the nodes is happening properly. Since a case is opened with NGS they will take a look at the complete configuration and let you know where things are failing exactly.