Hi all,

I'm having an issue where I can't restore all the indexes using nsrdr. I have multiple Networker environments and I've been asked by Management to test a disaster recovery for all environments.

We use Networker 19.5.0.0 along with a Data Domain in Windows 2016. I uninstalled Networker from the server and then reinstalled Networker with a clean slate. I then add my Data Domain using NMC (without checking to re-label the storage) and issue nsrdr -N.

I've done this in the past in a previous environment with much less data and files and there were no errors. Now, with this environment, I can't restore the indexes for 1 client. It's actually probably the biggest (in file count and size) of all my clients. The error that nsrdr gives is this : Cannot lock file index for client xxx (Too many open files)

I tried a couple of times to restore only the indexes of this client using nsrdr -c -I xxx, but it still gives me the same error.

It restores about 90GB out of 94GB, and then gives up.

I've done some researches on Google and in Networker official documentation, and I can't find something related to my environment. The only thing I find is a ulimit setting related to Linux. I'm running Windows.

I tried something else; wasn't sure if it would be working but anyway. I had taken a backup of all /nsr/ folder before uninstalling Networker. I tried to just copy the indexes of that client over the /nsr/indexes/xxx folder. Once the copy was done, I tried running an nsrck -v -L 6 xxx. The same error comes up.

There is no log in daemon.raw related to this and I can't find a log file that gives me more details. Google doesn't really help either.

- Can I "import" the indexes that I had previously backed up ? If so, was I doing it the correct way ?

- What is this error message ? I think it's Windows throwing it to Networker, but I can't find any clues related to this. Maybe there's a config file in Networker somewhere that I can edit to fix this ?

Thank you.