The error itself seems to indicate issue with shared memory - but I haven't seen that before. Try following - try to scan some smaller saveset and see if you get this. I wonder if size of what you are scanning has something to do with it.

Just tried running it on a small saveset and still getting the same issue...

even if I run it with other options I get the same problem.

Hi Guys,

Looking at the deamon.log it shows that the record size of the file device is 1024KB which is wrong, and the advanced file device block size should be 128KB.

Does anyone know hoe to change this manually in windows registry?

Hi dd1980,

As the problem is looking to shared memory so you can increased the shared quota of that particular drive in which the NSR folder is .You can also do try by deleting the content of /nsr/tmp folder .

Hi Guys,

thanks for all your pointers, the customer was advised to set the environmental value NSR_DEV_BLOCK_SIZE_ADV_FILE (variable value: 1024), to optimise write speeds to our DataDomain filesystem.

They have 2 sites 1 UK 1 US, and they have been experiencing the problem with the scanner command on both servers.

I have looked in the event viewer and they do not seem to be experiencing any issues with memory usage whist the scanner command is running.

I have contacted EMC with this issue, but all they have advised is to change the block size on the devices to 128kb, however this is a bit tricky as both datadomains have data residing on them.

Any ideas are appreciated.

Hi Guys,

EMC have come back to me advising that this is a known issue and they are working to get it resolved.

Thanks for all your help.

I do understand this is pretty much old post, but it is quite relavant to the situation I am in.

the new aftd device advanced properties doesnt have an option to sent the BS.