I would suggest keeping maxDsiz smaller that physical memory if possible
otherwise it may encouraging swapping.  We also tend to significantly
increase maxTsiz and maxSsiz (but not necessarily on account of Networker).

Try comparing your kernel parameters between the 2 systems.  Also, check
where are the tape drives and if the path to them the same (ie direct or
network).  Check the clients for same (ie. is old server a client w/ LOTS
of data that is now network traffic?).

Chuck Davis
Army Medical Surveillance Activity
Walter Reed Army Medical Center
Washington DC

On Thu, 24 Oct 2002 03:54:08 -0400, Tore Eikanger
<tore.eikanger AT MERKANTILDATA DOT NO> wrote:

>Hi
>
>Moved our NetWorker 6.1.2 from 1 CPU server to 2 CPU server, and the full
>backup went from 24 hours to 35 hours.  During backup NSRD uses almost
>100% CPU and there are MANY processes in queue.
>
>>From the admin guide, we are recommended to increase the maxdsiz parameter
>from current 64MB to 2GB.  Could this explain the trouble we are having,
>or are there other suggestion we should implement during our scheduled
>downtime tonight?
>
>Best regards
>
>Tore Eikanger
>Sr. Systemsengineer - LCNS
>Eterra AS
>
>--
>Note: To sign off this list, send a "signoff" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=