The bottle neck on any backup is usually NOT the CPU nor the memory.

The real speed comes from the I/O access and throughput.

So what changes were made to the Server HD configuration or SCSI Access
setup?

semper fidelis et paratus! /ALE

> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Teresa Biehler
> Sent: Wednesday, August 23, 2006 1:39 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Hardware upgrade and perf problems
> 
> Hi,
> 
>  
> 
> We're running NW v7.2.2.  We recently changed the hardware 
> from an E450 running Solaris 9 to a V880 running Solaris 10.  
> During the transition there was no change in the NW version 
> or configuration - /nsr moved from one server to the other 
> intact.  Well, after putting in a server with faster CPUs and 
> more memory, quite a few of our backups have slowed down.  
> 
>  
> 
> So, does anyone have any suggestions on tuning or how to 
> approach finding the problem?
> 
>  
> 
> Thanks.
> 
> Teresa
> 
> 
> To sign off this list, send email to 
> listserv AT listserv.temple DOT edu and type "signoff networker" in 
> the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any 
> problems wit this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or via RSS 
> at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER