2011-11-22 08:34 AM
when i start ndmpcopy -f ,spend some time waiting for the above.
FAS3210B*> ndmpcopy -f /vol/vol0 /vol/vol8
Ndmpcopy: Starting copy [ 4 ] ...
Ndmpcopy: Socket connection to source FAS3210B failed
Ndmpcopy: Issue 'ndmpd on' on the source filer to enable NDMP request then retry the connection
FAS3210B> options ndmp
ndmpd.preferred_interface disable (value might be overwritten in takeover)
but , i check the options ndmpd and ndmp status , not any problem...
please to help me , and give me good solutions,tanks
2011-11-22 10:22 AM
There can be issues when the primary interface (check /etc/hosts and see where the hostname FAS3210B is used.. the one with more than one name with both the interface and host names) then make sure that interface is up. Often we find when it is down ndmp local won't work...even though it uses the loopback adapter it needs the primary interface defined to the host online.
2013-05-07 02:16 AM
are there any updates to this issue? We experience the same problem, "Issue 'ndmpd on' on the destination filer to enable NDMP request then retry the connection"
hosts file looks good, interfaces are all up, name resolution works fine.
This issue occurs on a local ndmpcopy job only, from a remote filer the ndmpcopy job runs well.
2013-05-15 01:48 AM
We could solve this issue. This is due to a bug in OnTap 8.1 and some others too, but fixes in Release 8.1.1
There are Zombie NDMP Sessions left which prevent to start new ndmp jobs. Here´s the Solution:
OEM: Data ONTAP 8.1 NDMP daemon does not allow new NDMP sessions
Protection manager jobs or NDMP backups fail for a NetApp storage controller running Data ONTAP 8.1.
The following error message is displayed:
ERROR: maximum number of NDMP processes (392) forked.
The ndmpd status command displays no ndmpd sessions.
In Data ONTAP 8.1, the ndmpd daemon follows the UNIX convention of forking a copy of itself for each NDMP session. For some reason, the daemon gest corrupt and cannot fork any copies, even though there are no copies running.
The following is a BUG in Data ONTAP 8.1:
BUG 587756 - NDMP service disruption, NDMP does not serve any client requests
In the public BUG report, the workaround says 'Restart NDMP service,' but is sparse on details. The following is the procedure to do that:
The ndmpd daemon needs to be restarted to clear it and allow it to start spawning copies again. Rebooting the storage system will accomplish this, but getting permission to reboot is difficult for many users.
Perform the following steps to stop and restart only the ndmpd daemon process:
Note: BUG 587756 is listed as fixed in Data ONTAP 8.1.1.
2015-08-05 05:05 AM - edited 2015-08-05 05:06 AM
Interestingly enough I worked around this issue by specifying localhost as the filer.
ndmpcopy -sa user:pass -da user:pass locahost:/vol/myvol localhost:/vol/myvol2