Unsolved

This post is more than 5 years old

8 Posts

1541

February 27th, 2009 03:00

NS20 NDMP Backup with Networker 7.4SP3 Solaris configuration.

Coming from Netapp experience.. EMC is giving me a proper mind block here! Here goes ..

Trying to set up NDMP backup for our new NS20.
Backup server is a Solaris OS running Networker 7.4SP3 with SL500 LTO2 library attached.
would like to stream over network without reserved drives
(so don't want to do the jbconfig and set a drive NDMP only)

I have created the ndmp account/pw on the server using this
# /nas/sbin/server_user -add -md5 -password ndmp
on the control station. have not added to server_3 as its a passive

and followed document id:esg83108 (NDMP Client Resource Configuration).

yet when I run the job in networker i get the following error :
No full backups of this save set were found in the media database; performing a full backup
42571:nsrndmp_save: Failed to connect to port 10000 at host 'Datamover' :Connection refused
42576:nsrndmp_save: Couldn't connect to service
42884:nsrndmp_save: Not able to connect or authorize the client 'Datamover' : Failed with error(s)

ndmp server is enabled on the Celerra Manager\Security\Network Services.

On our netapp filers .. all I did was enable NDMP on the filer, and run the following backup command: nsrndmp_save -M -P "backup-server" -T dump
with HIST, UPDATE and EXTRACT_ACL set to =y and that works fine.
There appears to be much more to the EMC process ...
I guess I cannot get my head around the datamover config part of the EMC.
The fact that my unix\linux exposure is only now 5 months and counting ... so not overly familiar with the NS20 CLI.

Any hint tips to point me in the right direction would be greatly appreciated.

6 Operator

 • 

8.6K Posts

February 27th, 2009 03:00

sounds like you want to do 3-way NDMP

first check if your NDMP user account was created correclty

server_user server_2 -list should show it

then try to ftp to the data mover and login using that username password

first from the control stations like "ftp server_2" then from the backup server

BTW there is a subforum here for EMC Networker and NDMP
see Products -> Storage Software -> NDMP

8 Posts

February 27th, 2009 04:00

Thanks for such a speedy response !

just a quick question .. how do i change the prompt from [root@"controlstation"]# to [root@"controlstation"]$ so as to be able to run the commands ?

also I can ftp from the controlstation to server 2 with ndmp acount but not from the backup server.

I get connection refused.

6 Operator

 • 

8.6K Posts

February 27th, 2009 04:00

if ftp is enabled (server_ftp) check your network/routing from the backup server to the data mover

I you mean running the few commands that need root like server_user just su from nasadmin to root
(Dont use "su -" as this gets the root enviroment which doesnt have the path and variables to run the nas_* and server_* commands)

6 Operator

 • 

1.5K Posts

February 27th, 2009 07:00

A quick clarification -

you need to login as "nasadmin" - then change to root using "su" (NOT"su -" ).

If you create the nasadmin user with root user profile, it will not work with the NAS environment. The NASDB variables need to be set, which is done when you login as nasadmin. But to create the user you need root privilege - thus doing su, without changing the profile.

My 2 cents :)

Thanks,
Sandip

8 Posts

February 27th, 2009 07:00

Thanks All ....
Starting to get the idea with the CLI !! I had been actually logging on as root.

Is there a security seeting thats needs to be set on the datamover server_2 ? I can i can ping the datamover fine from my backup server .. But if i ftp to it i get connection refused before any prompt for login.

btw ..when setting up the client on Networker, I simply used the ip-address assigned to the Datamover as the client name. ( Its not named and registered in DNS yet so figured IP would be the best bet at least for testing )

Thanks again ...

6 Operator

 • 

1.5K Posts

February 27th, 2009 08:00

Good - we are making progress :)

Were you able to test the ftp from the backup server as well. Since you were able to test ftp from CS - FTP must be enabled on the data mover. Ensure you are using the correct IP address while testing FTP from the backup server.

ftp .

Lastly - can you confirm that the backup configuration is using the IP address - not the name (i see you have given a name "datamover") - you may consider creating a local host file on the server keeping the datamover entry - so that the name resolution also works.

It seems, Rainer had some connection issues to access this forum - but I am sure, he will be back soon with his suggestions/ideas. In the mean time, please try the above.

Regards,
Sandip

6 Operator

 • 

1.5K Posts

February 27th, 2009 08:00

FTP may not be enabled on the data mover - thus refusing the session - you don't need FTP for the backup purpose, Rainer mentioned that only to ensure that the user creation was done correctly.

So - you got the point now - you need to re-create the ndmp user logging in as nasadmin and then changing to super-user mode with only "su".

Using IP Address on the Networker client should work without any issue - it can be any IP address assigned to the data mover - but ensure the IP Address is reachable from the Networker server.

All the best - :)
Thanks,
Sandip

8 Posts

February 27th, 2009 08:00

I have now recreated the ndmp user as advised and tested with Rainer's Method.
Again only works on server_2 from control station.

Running the job in networker still flag the same connection refused.

6 Operator

 • 

8.6K Posts

February 27th, 2009 09:00

However.. I just ran the traceroute on the backup server to the datamover .. 1st hop is the CS then it
seems to be timing out (i.e 3 asterix per hop but no response.)


that should be the case - the DM needs to be reachable directly and not through the CS

are you sure you are using the external IP address of your data mover in the Networker config and the ftp test and not the 128.221.x.x ?

8 Posts

February 27th, 2009 09:00

Many thanks for you help so far Sandip! I am really appreciating the walk-thru !

To confirm .. the "datamover" is the IP of the datamover (Did not want to list the IPs in the forum.)

Also I have tried to ftp from the backup server with the conection refused response.

However.. I just ran the traceroute on the backup server to the datamover .. 1st hop is the CS then it seems to be timing out (i.e 3 asterix per hop but no response.)
Yet It pings fine from the backupserver ?

6 Operator

 • 

1.5K Posts

February 27th, 2009 10:00

Sorry - did not check Rainer had already replied. I was composing my reply when I had to go to a data center and just came back and finished my reply - but it was really late :)

6 Operator

 • 

1.5K Posts

February 27th, 2009 10:00

That's not good - please check the routing and the IP addressing. The data mover IP should be directly reachable from the host - Control station should not come in between as a router.

Please ensure that you are using the correct IP and routing is done properly. In fact, if the data mover IP and the backup server IP addresses are in the same subnet - there should not be any routing at all.

Regards,
Sandip

8 Posts

March 2nd, 2009 02:00

I am using the external IP address allocated to the mover ... 160.61.x.x

I have run a traceroute from my desktop. It still routes thru the CS. But there is a reponse.

Also going back to FTP. On CS CLI, I ftp to datamover via server_2 alias and it works fine .. when I ftp via external IP of the datamover I get connection refused .. yet it all pings ok.

Message was edited by:
JRQA2009

6 Operator

 • 

8.6K Posts

March 2nd, 2009 13:00

I am using the external IP address allocated to the mover ... 160.61.x.x

I have run a traceroute from my desktop. It still routes thru the CS.


That definitely should not be the case

Please check your system or open a service request

I guess that either your cabling is very wrong or you have a network config problem on the Celerra or use the CS as the default gateway on your client.

Also going back to FTP. On CS CLI, I ftp to datamover via server_2 alias and it works fine .. when I ftp via external IP of the datamover I get connection
refused .. yet it all pings ok.


ping often isnt much help since it ICMP and can be treated differently than IP

If ftp is enabled (check with server_ftp server_2 -info) you need to be able to ftp to the data mover and get a login prompt

Also if you do a "telnet 10000" you need to get back some gibberish character and not connection refused - unless you have NDMP turned off
you can see if NDMP is turned off in the GUI in Security->Network Services

IMHO if you dont get an ftp prompt or a response to telnet to the NDMP port there is no point in continueing with the Networker setup

Rainer

8 Posts

March 6th, 2009 04:00

Resolved !!

Thought I would post something up so others don't make the same silly mistake.

Datamover Internal IP - 128.221.x.x on mge0
Datamover External IP - 160.x.x.94 ???
CIFS Server on IP - 160.x.x.123 on cge2

The IP for datamover ( external ) was not working as posted so far in the forum.
So I used the CIFS IP and it worked. I have since assigned cge3 to a dedicated backup LAN. FTP / Inquire -N "host" -T from networker server works now.

So there you have it ! Thanks verymuch for you help guys !
Next step is to figure out how to mirror NIC setup on failover - datamover.
I am sure I will be back !
No Events found!

Top