ADSM-L

Re: Image backup CPU time.

2003-02-03 00:10:27
Subject: Re: Image backup CPU time.
From: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sat, 1 Feb 2003 08:18:08 -0500
This is about what I would expect.  Eventhough you are using the SAN agent,
you could be still using the IP stack internal to the machine to get the
data from the client to the SAN agent.  And, if this is TDP for Exchange or
TDP for SQL, there is even more CPU overhead.  Without more information, I
can not analyze what could be driving up the CPU.  The other piece is the
type of disk technology you have attached and are you using client
compression.  I would not be surprised if you get no improvement by adding
the additional CPUs.  If your average was 90 to 100, then yes, but likely
not for 70 to 90.

Paul D. Seay, Jr.
Technical Specialist
Northrop Grumman Information Technology
757-688-8180


-----Original Message-----
From: Martinez, Matt [mailto:matt AT IDEXX DOT COM]
Sent: Friday, January 31, 2003 10:35 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Image backup CPU time.


First some stats about the servers involved

TSM Server- Windows 2000 TSM Server-Ver 5.1.1
TSM Client Windows 2K- 2CPU's@700MHz each 1Gig of RAM TSM Client
Version-5.1.1 with SAN Agent.

When I do an image snapshot backup on the client the CPU Averages around
70-90%. Is this normal? Will adding 2 more CPU Alleviate this problem and
improve performance. I am using 2 LTO Drives to do this backup and I am
averaging around 32MB/sec. Any help will be appreciated.



Thank You,
Matt Martinez
NT System Administrator
IDEXX Laboratories, Inc
207-856-0656
Fax:207-856-8320
matt AT idexx DOT com

<Prev in Thread] Current Thread [Next in Thread>
  • Re: Image backup CPU time., Seay, Paul <=