Bill,
        We've got ADSM managing about 850 GB of backed up and archived data -
our database is 8 GB - with mirroring, that brings it up to 16 GB.
So... the numbers in the book are about right (1%).  However, keep in
mind that the database can be extended and reduced on the fly.  Also,
we're not using copy storagepools yet - I've head this adds another 20%
to the database.  We backup about 25 GB every night.

Tim Pittson
tpittson AT himail.hcc DOT com
>----------
>From:  William Kral[SMTP:wkral AT TNE DOT COM]
>Sent:  Wednesday, June 12, 1996 3:30 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       ADSM Database Allocation
>
>In the ADSM Admin Guide for MVS, I read that the ADSM Database should
>be
>allocated to between 1-5% of the total data expected to be backed
>up..... If
>I plan in backing up (initially) 200 Gig of data, does that mean the
>DASD I
>should allocate on the Host should be between 2 Gig and 20 Gig? And if
>I
>mirror it, between, 4 Gig and 40 Gig? It sounds like a awful lot of
>DASD to
>allocate. Can anyone rely some of their experiences with database
>allocation
>and the amount of data they backup. Any help would be appreciated...
>Thanks
>in advance.
>
>Bill Kral  -   WKral AT TNE DOT COM
>