UNSOLVED
Backup 2016 Hyper-V CSV Cluster
Hi,
I'm trying to configure new backup of 2016 Hyper-V CSV Cluster.
It has 2 physical nodes and 1 virtual cluster node. OS is Windows Server 2016 Datacenter.
I have installed 9.2 FS client and 9.2 NMM in each physical nodes.
Hosts are:
- cluster.domainA.com
- node01.domainA.com
- node02.domainA.com
Where domainA.com is the backup networker. DomainB.com is the production network.
I have added the virtual cluster node client using the wizard, but after the " Select the Hyper-V backup objects" screen appears the following error: unable to connect to server.
After that, I have created an Hyper-V client manually copying a client and configuring manually the options.
I have added this options:
- Save set: APPLICATIONS:\Microsoft Hyper-V
- Remote user: Domain\user and password
- Backup command: nsrnmmsv
- Aliases: cluster, cluster.domainA.com, cluster.domainB.com
- Server Networker interface: networker IP
- Remote Access: node01.domainA.com, node02.domainA.com
- Storage node: nsrserverhost
But the following error appears:
The index client name 'node01.domainA.com' has been resolved to fully qualified canonical name ''. Changing backup name NODE01 to primary name node01.domainB.com for multi-NIC configured client.
Any help?
Regards.
Hi,
Thanks for your help.
I have added client instance for each physical nodes before configured the cluster.
But I'm not sure if this instances must be "dummy" or "hyper-v" instances.
Which configuration must have this instances?
Whithout this instances cluster wizard can't be done?
Regards.
- Now, Node02 is working and take backup of one VM. But the Node has 3 VM. And just one of the is taking backup. Allways the same VM. Node01 is taking backup of configuration. Not VM. And launching the Cluster, just the Node01 is working. Node02 is not begining when cluster is working. Regards.
- The hostname Node0X that you mentioned are the physical nodes correct? The backups should be done using the virtual node that is assigned the Hyper-V service. The physical nodes just need to be configured as clients they need not belong to any group or have to be configured to backup Hyper-V.
Yes, Node0X are physical nodes.
The backup is launched using the cluster/virtual node with Hyper-V service.
Node0X have filesystem backup as "dummy" instances.
Now, I have been able to make it backup of Node02. Using the cluster node.
But VM than are in the Node01 are not beeing backuped.
Regards.
crazyrov
6 Operator
•
1319 Posts
2014
0
Posted May 22nd, 2019 22:00
Have you created a client instance for each of the physical nodes with the domainA.com FQDN ?