Unsolved
1 Message
0
91
NDMP backup failing , data connect: failed to establish connection
Anyone please advise.
NDMP backups are failing. Connection is fine , and credentials are also valid. Please review logs and advise.
savefs also succeeded.
savefs netappudbimg: succeeded.
144324:nsrndmp_save: Adding attribute *policy action jobid = 1693209
.144324:nsrndmp_save: Adding attribute *policy name = NDMP
.144324:nsrndmp_save: Adding attribute *policy workflow name = NDMP Netapp Misc
.144324:nsrndmp_save: Adding attribute *policy action name = NDMP Daily
.42617:nsrndmp_save: NDMP Service Log: Session identifier: 82047
83320:nsrndmp_save: Performing incremental backup, BASE_DATE = 5991328841
42794:nsrndmp_save: Performing backup to Non-NDMP type of device
174908:nsrdsa_save:Saving the backup data in the pool 'ddvxblock'.
175019:nsrdsa_save:Received the media management binding information on the host 'aeqa'.
174910:nsrdsa_save:Connected to the nsrmmd process on the host 'aeqa'.
199815:nsrdsa_save: Successfully connected to the Data Domain device for DFA mode.
129292:nsrdsa_save:Successfully established Client direct save session for save-set ID '2923658633' (netapp:/svm_core_netapp/Data) with Data Domain volume 'ddvxblock.005'.
42658:nsrdsa_save: DSA savetime = 1698921865
85183:nsrndmp_save: DSA is listening for an NDMP data connection on: 172.1.1.1, port = 8313
42597:nsrndmp_save: data connect: failed to establish connection
42886:nsrndmp_save: Unable to start the NDMP backup process.
42951:nsrdsa_save: Successfully Done.
netapwp: /svm_core_netapp/vol_Data level=incr, 1 KB 00:01:34 0 file
42913:nsrndmp_save: Save session closed with NW server successfully
backup failed.
bbeckers1
1 Rookie
1 Rookie
•
120 Posts
0
November 17th, 2023 14:24
so how is this setup? what is supposed to be talking to the netapp? is this a 3 way setup, using a NW storage node, or rather the backup server to act that is to read from the netapp?
multihomed setup of the systems acting as NW storage node, that might have two or more network connections in different subnets to the netapp in question? This as the ndmp backup will start a process on the NW storage node and expects to be able to talk to the NW server AND the NDMP host (the netapp) over the same interface of the NW storage node being used.
We had an design issue in the past where the dedicated NW storage node had two interfaces it could talk to the backup server on (one of them was intended to be in the same network as the netapp to have a short route for the backup traffic and another was used to make the filesystem backups of said NW storage node), hence the nw server was spawning the DSA communication service on the wronf interface on the NW storage node. That one could NOT talk to the Netapp. One could not control which interface that this should occur on, hence we got rid of the backup interface that was intended to make regular filesystem backups for the NW storage node and only used the interface in the same subnet as the netapp, which was also routed to the backup server subnet. So the NW storage node only had one leg left to talk to the NW server instead of two.
How did you validate the connection and credentials are actually fine from the NW storage node end? Using the NW CLI command ndmpsup (ndmpsup -c <NMDPhost> -o <output.log>).
Garfield33
10 Posts
0
February 28th, 2024 12:16
Please check on the NDMP client (isilon etc) if static route is correctly set. how many NICs is dedicated for this backup ? Are the firewall ports between client, NW server , storage node and dd opened on service ports and 10000 ? also check priority on the nics in the NAS client, i would also check hosts file is there are any antries for NAs client, if there are hash them and let use round robin selection.
(edited)