Hi @DJ,

     You might have to control the utilization on the client side by controlling the number of save's that are run during a backup which in turn as controlled by the client parallelism.

Hi crazyrov, Thanks for your reply.

Thats pretty much what I was thinking, was just wondering if it had changed with v9.

Thanks again

It's not a NetWorker thing, but you can drop the priority of nsrexecd on the client at startup.  The new priority should be inherrited by any child processes unless this is changed by NetWorker itself (as it runs as root/administrator).

This should mean that even if backup processes bump up your server to capacity, that additional usage will have minimal impact on your production environment.

You can set this in the startup file in Unix by preceding nsrd/nsrexecd with

nice 15 nsrexecd

nice 15 nsrd

(or bump up the priority of your production application processes at startup using nice -10 to increase the priority)

In Windows you need a 3rd-party tool to change these at runtime, as per https://www.raymond.cc/blog/permanently-set-process-priority-in-windows-task-manager-with-prio/