Unsolved
This post is more than 5 years old
5 Posts
0
3087
April 30th, 2013 03:00
NDMP to Backup Exec 2012
Hi All, we are looking to backup CIFs servers on our VNX5500 to tape (tape library is connected to the Backup Exec server, not the VNX) via NDMP and Backup Exec 2012.
I have read and followed the EMC configuring NDMP Backups on VNX guide whith the only change on the VNX being to add a user and password:
/nas/sbin/server_user server_2 -add -md5 -password ndmpadmin
I haven't change any other settings as the defaults all look fine for now.
in Unisphere > settings > Network >Settings for File > Network Services I can see that NDMP is enabled for TCP on port 10000 for node server_2
My issue is that I can get Backup Exec to connect to it! In the Backup Exec wizard it asks for a servername, username, password and port. I'm using port10000 and the username and password created with the above command but I have no idea what to use for the servername. I have tried all the IP addresses for the control stations, I have even added server_2 to the hosts file on the backup exec server with all the IP's with no joy.
Any ideas what I'm doing wrong? Is there a way to test that NDMP is working without using Backup Exec (i've tried telnetting to port 10000 on the control station IP, but get no response.
Thanks in advance for any help.
Ed.



ble1
4 Operator
•
14.3K Posts
0
April 30th, 2013 03:00
You should ask this on VNX forum. As VNX is similar to Celerra (same actually), what we did was to create listener and we backup over listener. You do not backup control station so that approach is wrong.
lmosla
25 Posts
0
May 1st, 2013 11:00
Hi, is server_2 the server name?
Lenora
Backup Exec Support Engineer
Rainer_EMC
4 Operator
•
8.6K Posts
0
May 1st, 2013 14:00
server_2 is the internal management name for the data mover.
Thats ok for user in the server_user command to create an account for NDMP
In you backup exec you need to use one of the external interfaces on the data mover
name would be whatever you configured in your DNS for that interface IP
any external interace on the data mover that you can see with "server_ifconfig server_2 -a" and can ping from your BE server
(NOT the internal networks el* on mgmt1/2 or loopback) will work for NDMP
Rainer
ble1
4 Operator
•
14.3K Posts
0
May 1st, 2013 15:00
I believe you didn't configure it well. \\IP errors suggests that. If you are using NDMP backup, you define client with name of listener and you define save set as reported by server_mount server_2.
EdNewman
5 Posts
0
May 1st, 2013 15:00
Thanks everyone for your help so far. Using Rainer's suggestion I ran the command and got this output for the CIFS server I'm trying to connect to;
fsn01_userhome protocol=IP device=fsn01
inet=10.2.36.144 netmask=255.255.255.0 broadcast=10.2.36.255
UP, Ethernet, mtu=1500, vlan=0, macaddr=0:60:16:4f:56:e8
I have tried connecting using:
IP 10.2.36.144 (which pings ok)
s0vlfsuh01 (which pings OK and responds on the above IP, I have also added this to the windows hosts file on the backup server for good measure).
But I know get a different message in backup Exec:
Unable to connect to "\\10.2.36.144\".
An Invalid parameter was specified.
Any other ideas / suggestion gratefully received!
EdNewman
5 Posts
0
May 2nd, 2013 01:00
Sorted it! When I ran the command Rainer gave me to find the host IP I also recreated the user to make sure it wasn't a typo with that. Turns out that I recreated the user without MD5, so recreated it again and all is working now.
Thanks all for your help!
Ed.