What is the cache hit ratio on the database?
With 1GB RAM you should have your database buffer set pretty high.
I'm not sure how high ADSM can go but I have 300MB of RAM and a database
buffer pool of 30MB, 30720KB

CR

__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / ADSM
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com

Dilbert words of Wisdom:
I love deadlines.  I especially like the wooshing
sound they make as they go flying by!


> -----Original Message-----
> From: Shirley Chirico [SMTP:SChirico AT OKIDATA DOT COM]
> Sent: Friday, February 05, 1999 11:18 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Windows NT ADSM server
>
> Something is wrong with your set up if you are only getting 1.5gb/hr!  And
> especiallyif you are using a 25 gb disk pool.
> We back up a 35gb database (true, each file is about 1.5gb) in 2 hours.
> (over network). It goes to disk pool. Important to have disk pool be
> bigger
> than one bu session (else migration will auto kick in).
>  Check your activity log to see
> if something else is happening while your bu is taking place, like a
> migration or reclamation. Also important to have
> compression parameters and NT parameters set right (I'd have to look them
> up to report them - and probably depends on
> particular HW anyway). And our NT server is not as powerful as yours! It
> might be worth it to get a qualified IBM/ADSM rep in to audit your set up.
> (Also we have ADSM v2, which is reportedly slower than v3)
>
>
>
>
>
> "Ross, Mitch" <mross AT PSD.COMPUCOM DOT COM> on 02/05/99 09:25:03 AM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:    (bcc: Shirley Chirico/OKIDATA/OKI_DATA_CORP/OKI_ELECTRIC/US)
> Subject:  Re: Windows NT ADSM server
>
>
>
>
> Funny you should ask. I've been working on that quite a bit recently.
>
> IBM NetFinity 7000
> 4x200MHz P2 CPU's
> 1gig RAM
> dual 100mb Ethernet (one dedicated for backups)
> +25gig RAID 5 for disk storage pools
> 3447 DLT Tape library with dual DLT drives
> NT 4.0, SP4
> ADSM 3
> Client compression on, TCP/IP tuning, etc.
>
> The best we can do with this machine is restoring 1.5gig/hr over the
> network.  The data we're backing up is lots of small (<1meg) files that
> don't compress much.  (My understanding is that if you have huge
> mega-files,
> ADSM does better.)
>
> We've got a requirement to restore 260gig overnight or better. ADSM just
> isn't good enough.  An early test with BackupExec on a much lesser machine
> gave 6 to 7gig/hr. (DSS3 12gig tape, 1 CPU, 200meg RAM)
>
> If this holds true on production quality hardware, we're dumping ADSM.
>
> ____________________________________________________________
> Mitchell Ross                           mailto:mitch.ross AT ncgroup DOT com
> CompuCom Systems, Inc.          http://www.ncgroup.com
> The Source for Technology Deployment Processes and Standards
>
>
>
> -----Original Message-----
> From: Loon, E.J. van - SPLXM [mailto:Eric-van.Loon AT KLM DOT NL]
> Sent: Friday, February 05, 1999 8:10 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Windows NT ADSM server
>
>
> Hi ADSM-ers!
> Last week I posted a question about the performance of ADSM on a Windows
> NT
> server with a 3575 library.
> I would like to rephrase my question in order to receive more replies. ;-)
> I'm looking for performance figures for a Windows NT server. I found a
> report called "ADSTAR Distributed Storage Manager (ADSM) for Windows NT
> Version 3 Release 1 Performance Evaluation Report" but it's dated October
> 31, 1997. For this test a 2-way 166 Mhz. Pentium processor was used.
> Hardware and processors are much faster nowadays, so I'm curious about
> performances from the field.
> I'm very interested in performance over 100 Mb. Ethernet or FDDI.
> Any reply is VERY much appreciated!
> Kindest regards,
> Eric van Loon