8 hours does seem really long... I've got a couple of 20GB DB's and they
don't take that long to back up (bout half that)
I do full DB backups across all my adsm servers daily
I would fine tune adsm within mvs...
we did have two mvs environments but ditched them 'cause of the cpu cycles
required...
that is other clients on mvs bi@#$%# about adsm sucking all the horse
power...
our current 12 adsm servers are all RS/6000's
Oh, just checked again...502 registered clients with a current occupancy of
70 TB's
and I don't even want to try to count the # of files :-O

later,
    DWight

> ----------
> From:         Bill Colwell[SMTP:bcolwell AT DRAPER DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Friday, February 04, 2000 8:48 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Largest *SM DB
>
> What I am hearing is that you don't think *SM scales up the way it should.
> Is IBM/Tivoli really recommending not to go over 20G? It's news to me, and
> if so, will they please a clear public statement on scalability?
>
> My db stats are --
>
>            Total Usable Pages: 16,801,792
>                    Used Pages: 14,374,135
>
> The last full backup took 8:55.  I do it weekly, I take daily
> incrementals.  The server is os/390 1.3, *sm is at 3.1.2.50, 1450 nodes,
> 92M files, 5.6T total primary pool data, 9840 tape drives.
>
> I still think the ultimate solution for large databases is to have an
> option to host the db in db2 or oracle where the managment tools are very
> robust, and a 54G db is ordinary.
>
>
> --
> --------------------------
> Bill Colwell
> C. S. Draper Lab
> Cambridge, Ma.
> bcolwell AT draper DOT com
> --------------------------
>
> In <000c01bf6e9d$c6344b60$8404a8c0@balthasar>, on 02/04/00
>    at 09:48 AM, Bill Smoldt <smoldt AT STORSOL DOT COM> said:
>
> >And split it up, they should.  You shouldn't have a database this large
> >unless you're from Texas.  We aren't Oracle database administrators, who
> >all believe bigger is better.
>
> >I think the current support recommendation is to keep it under 20G.  The
> >last site I visited with a 50G+ database was taking too long to back up
> >the database.
>
> >For those of you with large DBs - how is your DB backup time?
>
> >Bill Smoldt    SSSI
> >Storage Solutions Specialists, Inc.
>
>
> > -----Original Message-----
> >From:   ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]  On 
> >Behalf
> >Of Joshua S. Bassi
> >Sent:   Thursday, February 03, 2000 2:17 PM
> >To:     ADSM-L AT VM.MARIST DOT EDU
> >Subject:        Re: Largest *SM DB
>
> >Keith,
>
> >This was talked about on the list about 6 months ago.  I believe the
> >largest DB reported here was 70GB.  Most customers end up splitting the
> >*SM implementation at that point into one or more servers.
>
>
> >--
> >Joshua S. Bassi
> >Senior Technical Consultant
> >Symatrix Technology, Inc.
> >jbassi AT gloryworks DOT com
> >(503) 702-3371
>
> >-----Original Message-----
> >From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf 
> >Of
> >Keith Nelson
> >Sent: Thursday, February 03, 2000 10:57 AM
> >To: ADSM-L AT VM.MARIST DOT EDU
> >Subject: Largest *SM DB
>
>
> >Who's managing the largest single instance of a *SM DB?
>
> >Keith Nelson                 Voice: 612.891.2867
> >Gresham Enterprise Storage   Fax:   612.891.4763
> >knelson AT openmic DOT com          Web:   http://www.gresham-computing.com
>