Everyone gives netware a hard time, me included BUT you can crank it
up with the PROCESSORUTILIZATION parameter and the fact that you can
run multiple DSMC's... we run about 5 or 6 and push 6+ GB/hr...
later
Dwight
______________________________ Reply Separator _________________________________
Subject: Doing Eval of ADSM, a couple of questions . . . . . .
Author: ADSM-L (ADSM-L AT VM.MARIST DOT EDU) at unix,mime
Date: 4/5/97 2:56 AM
We are evaluating ADSM, it hasn't been pretty :-(.
Our eval system is a RS6/k-590 with 512MB, as much disk as
I need to put on it, a DLT drive, and a Qualstar 46120
8mm tape lib (4 8505XL drives). It's attached to a ATM
network which connects to the Netware server I'm testing
with on a FDDI.
May I ask a couple of questions?
1) ADSM on SMP
The var were dealing with stated we did NOT want
to put ADSM on a SMP system, it doesn't scale. I
talked with a person from ADSM performance who indicated
that on a 2-way system is around 1/7x. The performance
model IBM ran indicated we would need around 2 590 class
systems. How well does ADSM work on SMP?
2) We are mostly looking at backing up our Netware systems,
which have a small average file size (< 50k). From going through
the list archives it appears that I can expect about 1GB/hr
restore rate. What kind of restore rate do you get
when restoring Netware servers (our servers are at least
a 90mhz pentium with f/w scsi drives on a fddi network)?
3) Is anyone familiar with what changes are planed for ADSM
to allow it to handle small files better?
4) Is anyone using the Wang/Kodak HSM software for Netware that
interfaces with ADSM? What is your experience with it?
5) What kind of load does ADSM put on a Netware client during
a backup?
Thanks!
Rick
----------------------------------------------------------------------
Richard L. Rhodes rhodesr AT ohioedison DOT com
Richard L. Rhodes rhodesr AT ohioedison DOT com
Ohio Edison Co. Phone: 330-384-4904
Fax: 330-384-2514
--MimeMultipartBoundary--
=========================================================================
|