Mandri
2 Iron

Re: NMM 3.0 SP1 + Hyper-V 2012 R2 cluster backup

Jump to solution

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

0 Kudos

Re: NMM 3.0 SP1 + Hyper-V 2012 R2 cluster backup

Jump to solution

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.

0 Kudos

Re: NMM 3.0 SP1 + Hyper-V 2012 R2 cluster backup

Jump to solution

Hello Carlos.

"Domain admin" account didn't resolve the issue. Maybe you know some other solutions?

0 Kudos

Re: NMM 3.0 SP1 + Hyper-V 2012 R2 cluster backup

Jump to solution

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)

View solution in original post

0 Kudos
Highlighted
sddc_guy
3 Argentium

Re: NMM 3.0 SP1 + Hyper-V 2012 R2 cluster backup

Jump to solution

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-tr...

In my labbuildr toolkit i use this one to set rights for the Domain User on the local machines:

<#

.Synopsis

   Short description

.DESCRIPTION

   labbuildr is a Self Installing Windows/Networker/NMM Environemnt Supporting Exchange 2013 and NMM 3.0

.LINK

   https://community.emc.com/blogs/bottk/2014/06/16/announcement-labbuildr-released

#>

#requires -version 3

[cmdletBinding()]

param (

[parameter(mandatory = $false)]$PlainPassword = "Password123!",

[parameter(mandatory = $false)]$BackupAdmin = "HyperVBackupUser"

)

$ScriptName = $MyInvocation.MyCommand.Name

$Host.UI.RawUI.WindowTitle = "$ScriptName"

$Builddir = $PSScriptRoot

$Logtime = Get-Date -Format "MM-dd-yyyy_hh-mm-ss"

New-Item -ItemType file  "$Builddir\$ScriptName$Logtime.log"

############

Function Add-DomainUserToLocalGroup

{

[cmdletBinding()]

Param(

[Parameter(Mandatory=$True)][string]$computer,

[Parameter(Mandatory=$True)][string]$group,

[Parameter(Mandatory=$True)][string]$domain,

[Parameter(Mandatory=$True)][string]$user

)

$de = [ADSI]"WinNT://$computer/$Group,group"

$de.psbase.Invoke("Add",([ADSI]"WinNT://$domain/$user").path)

} #end function Add-DomainUserToLocalGroup

$ADDomain = (get-addomain).forest

$maildom= "@"+$ADDomain

#$PlainPassword = "Password123!"

$SecurePassword = $PlainPassword | ConvertTo-SecureString -AsPlainText -Force

New-ADUser -Name $BackupAdmin -AccountPassword $SecurePassword -PasswordNeverExpires $True -Enabled $True -EmailAddress "$BackupAdmin$maildom" -samaccountname $BackupAdmin -userprincipalname "$BackupAdmin$Maildom"

foreach ($ADgroup in ( "Remote Desktop Users"))#, "Windows Authorization Access Group"))

    {

    Write-Verbose "Adding $BackupAdmin to $ADgroup"

    Add-ADGroupMember -Identity $ADgroup -Members $BackupAdmin

    }

Grant-ClusterAccess -User $ADDomain\$BackupAdmin -Full

$Nodes = get-cluster . | Get-ClusterNode

foreach ($Node in $Nodes)

    {

    foreach ($localgroup in ( "Administrators", "Backup Operators", "Hyper-V Administrators","Remote Desktop Users"))

        {

        Write-Verbose "Adding $BackupAdmin to $localgroup"

        Add-DomainUserToLocalGroup -computer $Node.Name -group $localgroup -domain $ADDomain -user $BackupAdmin

        }

    }

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

<#

.Synopsis

   Short description

.DESCRIPTION

   labbuildr is a Self Installing Windows/Networker/NMM Environemnt Supporting Exchange 2013 and NMM 3.0

.LINK

   https://community.emc.com/blogs/bottk/2014/06/16/announcement-labbuildr-released

#>

#requires -version 3

[CmdletBinding()]

param(

[Parameter(mandatory = $true)]$BackupAdmin,

[Parameter(mandatory = $true)]$Hostprefix

)

$ScriptName = $MyInvocation.MyCommand.Name

$Host.UI.RawUI.WindowTitle = "$ScriptName"

$Builddir = $PSScriptRoot

$Logtime = Get-Date -Format "MM-dd-yyyy_hh-mm-ss"

New-Item -ItemType file  "$Builddir\$ScriptName$Logtime.log"

############

foreach ($Client in (Get-ADComputer -Filter * | where name -match "$Hostprefix*").DNSHostname)

{

& 'C:\Program Files\EMC NetWorker\nsr\bin\nsraddadmin.exe'  -u "user=$BackupAdmin,host=$Client"

& 'C:\Program Files\EMC NetWorker\nsr\bin\nsraddadmin.exe'  -u "user=SYSTEM,host=$Client"

& 'C:\Program Files\EMC NetWorker\nsr\bin\nsraddadmin.exe'  -u "user=Administrator,host=$Client"

}