This post is more than 5 years old
19 Posts
0
2921
NMM 3.0 SP1 + Hyper-V 2012 R2 cluster backup
Hello,
I try to backup our Hyper-V 2012 R2 cluster. It consist from 5 nodes. I created 5 clients for each physical nodes and 1 client for virtual cluster name. Each node has networker agent and networker module for microsoft applications. When i start group with virtual_cluster_name client it backup only VMs which hosted on current cluster owner node (for example node1), all other VMs (on other nodes) didn't backup. If i move core cluster resources to enother node it will backup only VMs which hosted on that node. My current save set APPLICATIONS:\Microsoft Hyper-V\
When i tried to backup some VM, that hosted on other node i used save set APPLICATIONS:\Microsoft Hyper-V\VM1 and my backup was failed ( i attached nmm.raw ). I tried different save sets, different options in Application Information but it didn't help. It always backup only VMs which hosted on current cluster owner.
Networker Server: Windows Server 2008 R2, Networker 7.6.4
Hyper-V nodes: Windows Server 2012 R2, Networker client 8.1.1, NMM 3.0 SP1
Virtual_cluster_name configuration:
Backup command nsrsnap_vss_save
Application Information NSR_SNAP_TYPE=VSS
NSR_FEDERATED_BACKUP=YES
NSR_VSS_FULL_BACKUP=YES
I will be glad for any help.
Aleksandr_Kuche
19 Posts
0
February 10th, 2015 07:00
I resolved my issue, so maybe it will be usefull for somebody.
I created new AD account and granted for it next permissions on each Hyper-V nodes:
Local Administrator
Access Control Assistance Operators
Backup Operators
Hyper-V Administrators
Remote Desktop Users
Users
The next step I provided access to cluster management for this account:
Open Powershell and type next command:
Grant-ClusterAccess -User domain\user -Full
And the last step I changed nsrexecd service log on property: I did it log on from account (which I created at first step)
Mandri
91 Posts
0
October 10th, 2014 00:00
I have the same error, please help!
Networker Server: Windows Server 2012 R2, Networker 8.2
Hyper-V nodes: Windows Server 2012 R2, Networker client 8.2, NMM 8.2
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
October 10th, 2014 00:00
Do you have a active-active cluster or a active passive cluster ?
Mandri
91 Posts
0
October 10th, 2014 01:00
Active-passive. The experimentally found the cause of the error: If the virtual machine is on a node that does not owner the quorum disk - backup does not start. If the virtual machine and the owner of the quorum disk to the same node, the backup is started.
Aleksandr_Kuche
19 Posts
0
October 10th, 2014 03:00
Active-Active.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
October 10th, 2014 04:00
So you have more than once virtual instance on your cluster ?
Aleksandr_Kuche
19 Posts
0
October 10th, 2014 04:00
No, just one virtual instance (virtual cluster name).
CarlosRojas
1.7K Posts
0
October 15th, 2014 03:00
Hi @Aleksander_Kucher
Have you checked the permissions and followed the steps in the documentation?
I can see OS permission denied error messages:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)))
Thank you,
Carlos
Mandri
91 Posts
0
October 15th, 2014 05:00
Hi Carlos Rojas !
Our networker 8.2 archives Exchange 2013 cluster, administrator domain account are used in settings of service Replication Manager on the client. Security settings are no more.
For Hyper-V cluster in the documentation does not indicate anything. But even with the settings service RMAgentPS - the problem persists.
The solution was found in this forum: https://community.emc.com/message/803090. Checked at all works.
Can someone explain why this solution helped and how to be safe for archiving mood cluster Hyper-V?
Mandri
91 Posts
0
October 15th, 2014 06:00
Yes, the properties of the client-cluster in the Administration Console, I ordered the username and password with administrator privileges.
Please tell me where it is necessary to prescribe a list? Through command nsraddadmin server ...?
like this?
nsraddadmin -u *@hyper-v_node1
thanks
CarlosRojas
1.7K Posts
0
October 15th, 2014 06:00
Hi Mandri,
What did you have set in the "Remote Access" field of the client configuration?
You should have at least the following information:
*@hyper-v_node1
*@hyper-v_node2
*@hyper-v_node3
*@hyper-v_node4
*@hyper-v_node5
*@hyper-v_virtual_node
Basically you need to add these lines into all Hyper-V nodes to allow each of them to access to each other.
Add as many physical and virtual Hyper-V nodes as present in your environment.
Thank you,
Carlos
Aleksandr_Kuche
19 Posts
0
October 15th, 2014 06:00
Hi Carlos.
All permissions are correct, in the "Remote Access Field" all nodes and cluster name are set as you wrote:
*@hyper-v_node1
*@hyper-v_node2
*@hyper-v_node3
*@hyper-v_node4
*@hyper-v_node5
*@hyper-v_virtual_node
I'll try to set "Domain admin" account in the "Access" field and then i'll write a result.
Aleksandr_Kuche
19 Posts
0
November 10th, 2014 01:00
Hello Carlos.
"Domain admin" account didn't resolve the issue. Maybe you know some other solutions?
sddc_guy
159 Posts
2
February 10th, 2015 20:00
I have seen many issues of that, most likely all result from inproper rights.
I described some common failures and the Solution to it here:
https://community.emc.com/blogs/bottk/2015/02/03/labbuildrnetworker-modules-for-microsoft-hyper-v-troubleshooting-with-l…
In my labbuildr toolkit i use this one to set rights for the Domain User on the local machines:
And this one to set the Networker Rights:
( note: all my Hyper-V Hosts start with HV, so i can filter an ad search guery to it.
If yiu can ot use the AD modules or run nsr on a non-windows box, you simply want to use nsraddadmin -u in 27 to 29 for each node