Delete NSR Peer information

nsradmin -p nsrexec

print type: nsr peer information; name:

delete

y

Thanks..

Deb

Please Like my Post if you liked it, Please Mark it as Helpful if it helped you, and mark it as Correct Answer if it resolved your query

One of my most-loved daily tasks in test dev :-)

wrote a small powershell script ( assuming Server on Windows ):

<#
.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
.EXAMPLES
remove-nsrpeerinfo.ps1 -client hvnode1
this removes the client hvnode1 from networker peer info ( domain appended automatically )
#>
#requires -version 3
param(
[Parameter(mandatory=$true)][string]$client
)
$ScriptName = $MyInvocation.MyCommand.Name
$Host.UI.RawUI.WindowTitle = "$ScriptName"
$Builddir = $PSScriptRoot
$Domain = $Env:USERDNSDOMAIN.tolower()
$Content = "delete type:NSR peer information;name:$client.$($Domain)"
Set-Content -Path .\delpeer.nsr -Value $Content
& 'C:\Program Files\EMC NetWorker\nsr\bin\nsradmin.exe' -p nsrexec -i .\delpeer.nsr

this deletes the client form nsr peer information.

you can remove line 19 if you are not as lazy as me and want to specify the doamin name yourself :-)

That removes it on backup server - OP asked for this procedure when targeting nsrladb on client.  In essence, he can use the script and modify just line where nsradmin is called by adding -s with client name plus removing reference to client in delete action.

I'm not sure why OP needs that on client as 99% of nsrauth issues with exchange of keys are resolved by removing client reference on the server only.