I've got 12 adsm servers (3-R40's, a 591, and rest S70's) and 540 registered
clients
got 138 on one server but getting ready to split half the load off to
another server

actually more important than the # of nodes but the jumber of files...
tons of little files drives the adsm server nuts more than bulk data

my largest takes in 1.3 TB  (client compresses down to 375 GB) daily from
just one of its clients
and total does under 500GB daily

Other environments that might only take in less than 200 GB daily do it in
tons of ## kb files and due to the number of adsm DB entries takes a lot of
time to do expiration, dbbackup, etc...

Dwight

> ----------
> From:         Talafous, John G.[SMTP:Talafous AT TIMKEN DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Friday, February 04, 2000 7:30 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Not the DB size but number of nodes?
>
> It seems to me that the larger challenge would be the number of
> nodes/clients your *SM environment supports. How many nodes do you
> support?
> How many servers? Nodes per server?
>
> John G. Talafous                         Sr. Tech. Prog/Anal
> The Timken Company                 Phone: (330)-471-3390
> P.O. Box 6927                           Fax  : (330)-471-4034
> 1835 Dueber Ave. S.W.
> Canton, Ohio USA  44706-0927
> talafous AT timken DOT com                  http://www.timken.com/
>