Dear Hrvoje:

Understand!!!

BTW,I cannot find any article about this limitation from NA...

Finally,thanks for your kindly reply.

BR

Danny

Dear Hrvoje:

Thanks for your kindly reply.

For our test,it looks too many files in this directory,I select some files, not all, then can do restore.

So,this is NA not able to handle it,not Networker issue?

BTW,in this situation,we should do the saveset recover,right?

Thanks.

BR
Danny

This NA... the error with buffer comes from ndmpd which is on filer side.

If you do ssid restore, whole thing will be restored - if that is not an issue that is ok. However, on filers you will find locations where you have many files to restore, but whole volume might have much more and you do not wish to restore whole thing. In that case partial restore, in smaller chunks, is the only thing to do (ndmp wise).

Thanks.

I believe this has been discussed once or twice here, but searching it now would probably not yield results... I might look in my notes later and if I find it I will let you know here.

Do you happen to know how many files did you select?  It looks as if nlist is hard locked to 10240 files (see here). I think in the past I have seen messages where nslist would be mentioned so I'm not willing to put my hand into the fire that this article matches the problem you have stumbled upon.

Sorry about ugly formatting, it was copy and paste and I guess EMC and NetApp page are not so compatible

The bottom line is that in the past you could crash (panic) filer with this and then fix was to hard code limit (the message we see today).

Sure, here it is:

 An NDMP recover request containing a large number of individual file names (nlist entries) can potentially cause the filer to panic.  The fix for this bug limits the maximum number of nlist entries that can be sent in a recover request to 10240. Recover requests with more than 10240 entries will no longer panic the filer. Instead, the request will return with an NDMP_ILLEGAL_ARGS_ERR error.  Note: this only affects NDMP selective file recovery or direct Access recovery operations.  Directory based recovery operations that specify a single path are unaffected by this problem.  

 Limit the number of files selected in the recovery request to 10240. 

Dear Hrvoje:

Sorry,I don't know how many files I selected.

But there is a test log from our other site.

nsrndmp_recover:ssid'2891921994':Performing DAR Recovery..

nsrndmp_recover:ssid'2891921994':data start recover: illegal arguments in request

nsrndmp_recover:ssid'2891921994':Unable to start the NDMP restore process.

nsrndmp_recover:ssid'2891921994':NDMP Service Log: Maximumof 1000000 nlist entries supported

ERROR: NDMP XDR message rec_len 3996 (+ total_len 12800000) larger then max 12801024 -- ignoring

Above messages prove you said.

Thanks for your kindly discuss with me.

BTW,the link I have no permission to access,can you post here?

Thanks.

BR

Danny

HA HA,EMC not hope show NetApp .

WOW,so this situation may impact filer to panic

I will adjust hard limit right now.

Thanks for your professional  and kindly reply.

BR

Danny