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.
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.
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.
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.