I'm fairly certain that does not apply if you create an ndmp user account 
on a NetApp filer.  The documents have said that for years and we've 
managed fine with a user-defined account.  However, we are not using NBU 
6.

We did have to limit the NDMP passsword length to 8 characters, which was 
a documented restriction.  You do that on the NetApp prior to generating 
the encrypted password.  However I note in the original question that was 
ruled out as an option.

William D L Brown




"Marianne Van Den Berg" <mvdberg AT stortech.co DOT za> 
Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
05-Jun-2009 20:32
 
To
"Jeff Cleverley" <jeff.cleverley AT avagotech DOT com>, 
veritas-bu AT mailman.eng.auburn DOT edu
cc

Subject
Re: [Veritas-bu] NDMP authentication failing for NetApp.






Have a look at this doc:
ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/267773.pdf
 
Extract:
The username used with the tpconfig command must be defined as root for 
each data mover.
 
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jeff 
Cleverley
Sent: 05 June 2009 19:20
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] NDMP authentication failing for NetApp.
 
A quick update is that I was able to configure the NetApp using the 
tpconfig -add -nh command line.  It finished with no errors and the NDMP 
host gui window now shows the NetApp.  The set_ndmp_attr -verify works and 
seems to talk to the filer OK.  The tpautoconf still fails.  A test backup 
policy fails with error 57 and the connection refused to host message.

I think I'm getting closer.  Any additional suggestions would be 
appreciated.

Thanks,

Jeff

Jeff Cleverley wrote: 
The tpautoconf doesn't work because it won't let me set up the filer as a 
host.  I've turned on the debug level but I'm not seeing any entries from 
the master server.  It appears the requests are not actually getting sent.

The pbx is something I don't know much about.  Is it possible this isn't 
configured correctly and may be causing the problem?

Thanks,

Jeff

pharrold AT comcast DOT net wrote: 
Run "tpautoconf -verify ndmp_host_name" and verify that access is granted
 
Its located in /usr/openv/volmgr/bin
 
If it failes, enable ndmp debugging on the filer (ndmpd debug 50), and 
re-run
 
Check the filer's ndmps log (generally in //filername/$/etc/ndmpd.log) for 
clues.
 

----- Original Message -----
From: "Jeff Cleverley" <jeff.cleverley AT avagotech DOT com>
To: veritas-bu AT mailman.eng.auburn DOT edu
Sent: Thursday, June 4, 2009 7:48:06 PM GMT -06:00 US/Canada Central
Subject: [Veritas-bu] NDMP authentication failing for NetApp.

Greetings,

I'm trying to get a remote NDMP backup connection going between my new 
6.5.3 RHEL master and one of our NetApp filers (7.2.5.1).  We have a 
non-root account on the filer (ndmpuser) and have given it a password. 
This has been used by Operations Manager in the past with no problems. 
When I try to set up credentials for that NDMP host, I use the user name 
"ndmpuser" and the encrypted password I got from running "ndmpd password 
ndmpuser" on the filer.  This fails authentication.  The filer is running 
NDMP version 4.

The error message is coming back saying the media servers could not be 
reached or the credentials are invalid.  The tape library is on the master 
server so I have not set the filer up as a media server.  The filer is a 
production system getting backups from 4 different countries so I'm 
reluctant to start changing NDMP levels or password length options. 

Please tell me what I'm missing.

Thanks,

Jeff
  

-- 

Jeff Cleverley
Unix Systems Administrator
4380 Ziegler Road
Fort Collins, Colorado 80525
970-288-4611
jeff.cleverley AT avagotech DOT com