I have worked with customers that are getting 120 G/hr going directly to 6
3590 tape drives using 6 parallel backint sessions on a 10k in an 8 cpu
(250mhz) domain ( ADSM server, backint, and Oracle all in the same domain).
The key is avoiding  I/O contention,  each backint session works on a
separate set of table spaces laid out on separate disks with a separate set
of resource on the server as it's target.  Restore same environment
105G/hr.

Disclaimer(I like my job): A reasonable amount of effort went into the up
front design of the database lay out with backup performance as a primary
goal, your mileage may vary.

Over the last year the E10k has become very popular and we have several
ADSM E10k customers that are very happy with performance all around. We now
have one in our lab, so feel free to email direct if you need specifics.


Thanks...Jim Riehl
Tivoli-ADSM Sun Server Development



Roger Hohmann <Roger_Hohmann AT WESTLB DOT DE> on 04/08/99 03:30:53 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: James Riehl/Tucson/IBM)
Subject:  Performance on Solaris E10K





Hi ADSMers,

I was asked to realize a backup/restore scenario on a Sun E10000, with
150 Gig backed up within not more than two hours, split into oracle db
(connect agent recommended) and files in filesystems.

The E10K will have some Gigs of RAM , 20 CPUs and a Disk Array.

I thought about installing a local adsm server, backing into another
Disk array and migrating into another adsm server  via server-server
communication later.

Anyone realized such a scenario before? Is the E10K fast enough? (There
is no other processing planned when backup occurs)


Roger Hohmann

WestLB
Division: 009 Services
Abteilung: 001-80633
Herzogstra?e 15
D - 40217 Dusseldorf
Tel.: +49211 826 8155
mailto:roger_hohmann AT westlb DOT de