cancel
Showing results for 
Search instead for 
Did you mean: 

EMM server unable to process request (78) - NDMP / Isilon

bunsen82
Level 4

Hi,

Trying to add a new NDMP device. We have existing NDMP devices but are trying to add a new one for our new cluster (Isilon)

I repeatedly get the EMM server is unable to process the request when adding the NDMP device via credentials/NDMP hosts. I get this when trying any credential option (use default, define creds etc) and I get no further. 

I have tested connectivity to the device on port 10000 and I can reach the hostname on that port. If I specify a random credential (ie creds that are not defined within NDMP settings of Isilon) I get an Invalid credentials type error, so that suggests to me that it is reaching it but for some reason, NBU is not liking the response. 

I have tried defining new credentials as the "default" NDMP creds (via host props/Master server) and again I get no further. 

I have tried restarting the EMM service, the Server and NDMP devices, no luck.

I have tried adding the device via tp config, and get similar errors:


D:\Program Files\Veritas\NetBackup\bin>tpconfig -add -nh backup.gbwwslivifs02.if
s.DOMAIN.com
Failed adding NDMP host backup.gbwwslivifs02.ifs.eu.sony.com.
The EMM server failed to process the request

D:\Program Files\Veritas\NetBackup\bin>

I wondered if any of the existing NDMP devices were affecting, so attempted to delete those in order for a "clean" setup - but also get the EMM server is unable to process the request when trying to delete.

How can I get this going? Is there a particular NDMP type log I can review? I have attached the server log but nothing stood out to me there, other than performance warnings

9 REPLIES 9

bunsen82
Level 4

Strangely, I am getting a further error of NDMP credentials already exist when using tpconfig -add, again, if I specify credentials not existing on the NDMP San config, authorization fails indicating that it defo seems to be reaching the cluster

D:\Program Files\Veritas\NetBackup\bin>tpconfig -add -nh backup.gbwwslivifs02.if
s.DOMAIN.COM -user_id test -password test
Credentials already exist for NDMP host backup.gbwwslivifs02.ifs.DOMAIN.COM

 

D:\Program Files\Veritas\NetBackup\bin>tpconfig -add -nh backup.gbwwslivifs02.if
s.DOMAIN.COM -user_id test1 -password test1
NDMP failed to verify host
Authorization failed for NDMP host backup.gbwwslivifs02.ifs.DOMAIN.COM

running tpautoconf -verify seems to confirm the device, with the "ndmp" creds

D:\Program Files\Veritas\NetBackup\bin>tpautoconf -verify backup.gbwwslivifs02.i
fs.DOMAIN.COM
Connecting to host "backup.gbwwslivifs02.ifs.DOMAIN.COM" as user "ndmp"...
Waiting for connect notification message...
Opening session--attempting with NDMP protocol version 4...
Opening session--successful with NDMP protocol version 4
host supports TEXT authentication
host supports MD5 authentication
Getting MD5 challenge from host...
Logging in using MD5 method...
Host info is:
host name "GBWWSLIVIFS02-15"
os type "Isilon OneFS"
os version "v8.0.0.4"
host id "0007430a97267710ef595111ffc49a37efd9"
Login was successful
Host supports 3-way backup/restore
Host supports LOCAL backup/restore

tpautoconf -probe output below:

 

D:\Program Files\Veritas\NetBackup\bin>tpautoconf -probe backup.gbwwslivifs02.if
s.DOMAIN.SONY.COM
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" SCSI device model "<SPECTRA PYTHON 2
000>":
Device "mc001" attributes=0x0
SERIAL_NUMBER=92100056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape013" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10420056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape012" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10340056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape011" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10320056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape010" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10240056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape009" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10220056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape008" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10140056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape007" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10120056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape006" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10310056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape005" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10110056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape004" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10330056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape003" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10210056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape002" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10230056E2
Host "backup.gbwwslivifs02.ifs.DOMAIN.COM" tape device model "<IBM ULTRIUM-TD6
H990>":
Device "tape001" attributes=(0x4) RAW
EXECUTE_CDB=t
SERIAL_NUMBER=10410056E2

D:\Program Files\Veritas\NetBackup\bin>

 

So looks like all the commands are also working correctly.. Just a small question so what’s the issue out here..

Credentials added, commands also working successfully..

To view existing ndmp username added on media server run the below command on each of the required media servers

tpconfig -dnh

if you need it for all the media servers the. tpconfig -dnh -all_hosts

Hi Amol,

The issue is adding a new NDMP device. I either get EMM server unable to process the request (78) or unable to set filer wide credentials. Credentials already exist (99)

The default ndmp creds (ndmp/ndmp) are defined on the SAN within NDMP settings. I have also added test/test.

When I tell NBU to "use global ndmp creds for this host" I get the 78

When I tell NBU to "use the following credentials for this ndmp host on all media servers" I get the 99

When I tell NBU to "use different credentials for this NDMP host on each media server (use advanced)" and using ndmp/ndmp or test/test I get the 99 error

When I do the verify, all seems to be OK. What am I doing wrong?

 

D:\Program Files\Veritas\NetBackup\bin>tpautoconf -verify backup.gbwwslivifs02.i
fs.DOMAIN.com
Connecting to host "backup.gbwwslivifs02.ifs.DOMAIN.com" as user "ndmp"...
Waiting for connect notification message...
Opening session--attempting with NDMP protocol version 4...
Opening session--successful with NDMP protocol version 4
  host supports TEXT authentication
  host supports MD5 authentication
Getting MD5 challenge from host...
Logging in using MD5 method...
Host info is:
  host name "GBWWSLIVIFS02-15"
  os type "Isilon OneFS"
  os version "v8.0.0.4"
  host id "0007430a97267710ef595111ffc49a37efd9"
Login was successful
Host supports 3-way backup/restore
Host supports LOCAL backup/restore

D:\Program Files\Veritas\NetBackup\bin>

 

 

The fact that verify is working means that ndmp credentials are already added in Netbackup.. try tpconfig -dnh command to see the added credentials..

If this is a new ndmp host and the credentials present in nbu is not correct then try removing the existing credentials first, verify that the credentials are no longer there by running “tpconfig -dnh -all_hosts”
then try adding it from the gui or the cli.

as per the output the username added is ndmp for this host

Connecting to host "backup.gbwwslivifs02.ifs.DOMAIN.com" as user "ndmp"...

Hi Amol,

 

The credentials defined in netbackup are ndmp/ndmp. I have now removed these from the config. tpconfig -dnh -all_hosts now only shows 1 NDMP host 

D:\Program Files\Veritas\NetBackup\bin>tpconfig -dnh -all_hosts
==============================================================================
Media Server:                   gbwwsclobkp01.DOMAIN.com
NDMP Host Name:                 a100_2
User Id:                        ndmp2 <Filer>
==============================================================================

D:\Program Files\Veritas\NetBackup\bin>

 

I am going to try defining a completely uniqie set of global NDMP creds in host props and see if it will autoconfig. What I am struggling to understand is why I can verify (succesfully) yet I cannot add with exactly the same creds?  

If it is set to use global credentials then you would still be able to run tpautoconf verify..
I think cli to list default ndmp credentials was similar to previous command with an extra D in it
tpconfig -ddnh or something like that

Still cannot add, still getting EMM server is unable to process the request (78) Verify works fine, yet it gives this error when trying to add with the default credentials specified.

Can I have some pointers on resolving this? Or what is the correct way of getting support from Veritas rather than community forums?