|
 Problems with "too many processes"
spartakich wrote:
Hi!
Actual Netvault version is 8.5.
Did you try to search in "Knowledge base" area on bakbone website ? There is description and solution for this problem.
You can also try change parameter - nvconfigurator, Process Manager >> "Number of progress buffers available to plugins" value. and put for example value 20 , so you be able to launch 20 jobs simultaneously.
I looked through the knowledge base and had already tried the following so far:
From Error 'No more processes permitted' when opening some NetVault windows
From the NetVault server:
1. Open the NetVault configurator
2. Stop NetVault Service (Service tab)
3. Go to Process Manager tab
4. Change the 'shared Memory (Kb) Used for Process Table to 16000kb (default is 500kb)
5. Change the 'Shared Memory (Kb) Allocated To a Progress Buffer to 10kb (default is 1)
6. Click the Apply button
7. Restart NetVault service in order for the new NetVault process table to be created
I couldn't set the shared memory allocated to a progress buffer to 10kb. Netvault wouldn't start when I set that parameter. If I increase it to 2, it starts up, but can't run any jobs. The jobs will just hang.
From: Recommended Configurator settings for the NetVault Server
2. Process Manager Tab
Change “Shared Memory (Kb) Used for Process Table” to 16000
On Linux, Unix and OS X, ensure that you have enough shared memory configured, before increasing this value.
If you will be running more than 30 jobs at the same time, contact customer support for help increasing this value beyond 200.
Change “Number of Progress Buffers Available to Plugins” to 200
I've tried increasing the number but so far it doesn't seem to have had any affect.
From: "Too many NV processes running at this time"
*** NVBU8.x has a maximum Process Table size of 128MB. On modern servers with large amounts of RAM it is recommended to Increase "Shared Memory (Kb) Used for Process Table" in increments of 8000KB (8MB), up to a maximum of 128000KB (128MB).
Increasing the shared memory for process table from the default helped a bit but usually after running 4-5 simultaneous jobs, the problem persists.
I could try potentially bumping up process table to the maximum value. Wasn't sure if there were any ramifications for doing so.
+----------------------------------------------------------------------
|This was sent by rickylee21 < at > hotmail.com via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------
------------------------------------
|