dd1980
Boron

scanner command error

Jump to solution
Hi Guys,

We have 2 environments 1 production and 1 DR. Both NetWorker servers run on 7.4.2. We use Datadomain for our disk backups, the data is then cloned off to tapes.

The block size on the Datadomain is set to (1024 KB). :

Also the server we are using is a proliant DL580 G2 with 4 CPUS 2794mhz
OS is Windows 2003 SP1
3.8 GB RAM
1.2GB Virtual memory
9.67GB page file.

When we try and run the scanner command to import index and media database information in case of the DR, we get the following error:

failed to create shmem object Global\lgtsm1006405: Input/output error
failed to create shared memory: failed to create shmem object Global\lgtsm1006405: Input/output error
scanner: SYSTEM error: not enough space

I have contacted EMC but we have got nowhere so far, has anyone seen this before?

Any help is appreciated

Thanks
Tags (1)
0 Kudos
15 Replies
ble1
Indium

Re: scanner command error

Jump to solution
I believe SP1 limit for bs to be 64KB was only for tapes so I would rule that out for now.

The error itself seems to suggest either an issue with heap memory or block size indeed. Did you try to increase heap memory?

Usually disk device has 128KB block size - I assume you change it manually?
0 Kudos
dd1980
Boron

Re: scanner command error

Jump to solution
Thanks for the response.

My customer was reccomended by the vendor to use block size 1024 in order to get the best writing performance to the datadomain.

I havent tried to change the heap memory as of yet, I need to contact an expert to do so as I am not quite sure how to do so.

Do you have any relevant articles you can point me to?

If not thanks for your help so far much appreciated.
0 Kudos
dd1980
Boron

Re: scanner command error

Jump to solution
I have done it, once tested I will let you know
0 Kudos
ble1
Indium

Re: scanner command error

Jump to solution
Just check for heap memory in Powerlink - there should be support article about it.
0 Kudos
dd1980
Boron

Re: scanner command error

Jump to solution
Hi,

we changed the memory heap in widows registry to 1024, restarted the NetWorker Server but we are getting the same error on the scanner command.

Any other ideas?
0 Kudos
ble1
Indium

Re: scanner command error

Jump to solution
Which heap is that? If I remember correctly there used to be 3 heap settings within same registry key... shared one and 2 desktop related...
0 Kudos
dd1980
Boron

Re: scanner command error

Jump to solution
This is what I did, I changed the SharedSection

1. Click Start | Run and run regedt32
2. Browse to the following key in the registry editor:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems
3. Click to modify the "Windows" value
4. Locate the SharedSection parameter within the data of this value. This parameter will have 3 or 4 values.
5. Increase the third value by 256 or 512

For example, when the SharedSection equaled "1024,3072,512,512" in one case, changing it to "1024,3072,1024,512"
0 Kudos
ble1
Indium

Re: scanner command error

Jump to solution
Are you trying to scan deleted volume or existing volume on top of the existing data?
0 Kudos
dd1980
Boron

Re: scanner command error

Jump to solution
we are trying to scan in data on top of existing one.
0 Kudos