OK, I've got 12 adsm servers across 4 locations in 3 states...
mainly S70's... 3 R40's still and 1 591 (or 59H ? I can't remember)

FIRST of all... force client compression... if they don't have the horse
power to perform it, they should upgrade their processors !
(but also upgrade your processor by all means ;-)  )

Now you will notice that the file size has a lot to do with task times
within adsm.
It can move more GB's in less time if it consists of a minimal quantity of
files.
(100 - 1 GB files takes longer to back up than 1 - 100 GB file)

On one specific S70 we take in about 1.7 TB of client "filespace" data
nightly (per 24 hour period)
(OK, it takes about 15 hours currently 'cause we push it down one fddi pipe,
we are looking at splitting it across two in order to reduce time)
With client compression ('cause it is mainly a big oracle db) it packs down
to under 400 GB.
It comes in through a single FDDI interface
We only have 4 - 3590B's on this box and most of the time not all of them
are being used.
(remember, migration process limits are A) number of drives available B)
your set migration proc limit C) number of unique client's data within the
pool being migrated )
Here is a vmstat while this box is under client load...

 > vmstat 3 3
kthr     memory             page              faults        cpu
----- ----------- ------------------------ ------------ -----------
 r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
 r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
 0  0 131127   122   0   0   0 570 1146   0 517  965 1100  6 22 14 57
 2  4 130836   132   0   3   3 3438 3899   0 2730 4437 5443  8 32  2 58
 2  2 130836   133   0   0   0 3599 5787   0 2681 3787 5425  5 29  1 64

This is with 30 inbound client sessions and one migration process running

I just noticed you are in town... I'll give you a call...

Dwight

> ----------
> From:         Patten, Stacy H.[SMTP:shpatten AT SAINTFRANCIS DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Thursday, December 16, 1999 9:18 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      ADSM system scaling
>
> Having never scaled an ADSM setup I would appreciate input for our
> situation:
>
> Current Hardware:
>         1 - H50  -512MB / 1-300MHz
>         24GB disk pool
>         1 - 3494 Library w/ 3 3590 drives
>         1 - ATM NIC (emulating token ring)
>         1 - 100BT NIC (not currently in use)
>
> Current Backup:
>         148GB
>
> We expect that by Dec 2000 we will be at 542GB a night.  We barely make
> the
> current backup routines, and this number will increase to 223GB with the
> addition of Exchange, SQL, and ORACLE clients.  Our backup window 10:00pm
> to
> 6am so we should have plenty of time to perform this, with the exception
> of
> migration consuming our tape drives twice a night.  Our servers are on
> different subnets, so the backup traffic goes across our ATM backbone and
> back before it hits the ADSM server.  Also, most of our servers are
> running
> 100BT ether with some on 16MB token ring.  We have (over?)estimated the
> following hardware setup to hopefully solve our capacity issues until at
> least the end of 2000.
>
> Proposed Hardware:
>         1 - H50 - 1GB / 2-300MHz
>         150GB disk pool
>         1 - 3494 Library w/ 8 3590 drives
>         2 - ATM NIC (emulating token ring & ethernet)
>
> Is this enough machine?
> Is this enough disk pool?
> Is this enough tape drive?
> Is this enough bandwidth?
>
>
>
> Stacy Patten
>
> Senior Network Engineer
> St. Francis Hospital
> phone- 918-494-9465
> pager- 918-646-8497
> email- shpatten AT saintfrancis DOT com
>