Chuck Mattern asks:

> We are in the process of setting up ADSM on MVS.  It will support 20 HP9000's
> and 30 Novell 3.1[12] file servers.  In looking at the total storage out there
> we may end up with over 300 gig's in the storage pools.  In looking at the
> Server Instalation Manual I see a reccomendation for allocating space for the
> database equal to something between 1% and 5% of the total storage.  For us
> that translates into to something along the lines of 3-15 gigabytes.  This
> seems excessive.  I am curious as to why we would base the database size on
> the total storage size rather than the number of files stored.  In addition my
> boss, who is more of a mainframe type than I am, tells me that we use much
> less thant this to manage shm, tlms, etc for over 1.5 terabytes of datasets on
> the MVS machine in the other areas.
>
> Could I please have some feedback as to experiences of other ADSM users in
> sizing their database?

I took the information in the installation manual with a huge grain of salt -
rock salt, that is! I'm not sure that there really is an accurate way to size
the database, because there are so many variables. Knowing the number of
files doesn't necessarily help, because you also have to take into account
the number of versions you'll keep, which mode you are using (absolute or
changed only), how frequently the data changes, etc.

Here are statistics for my shop. Note that BACKUPPOOL is my disk storage
pool, and is around 17 GB in size. DISASTER_RECOVERY is my copy storage
pool, which effectively mirrors my ARCHIVEPOOL, BACKUPPOOL, and TAPEPOOL.

My database is around 1.9 GB, and is 72% full.
My recovery log is 900 MB (I'm running it in roll-forward mode).

I've got around 100 clients, and my standard management class provides for
up to 15 backup versions, with inactive versions expiring after 15 days.

As far as comparing to HSM: I'm pretty sure that we have less than 100,000
data sets in our data center, yet our HSM Control Data Sets (CDSes) combined
take up about as much room as my ADSM DB, which is inventorying around
4.5 million versions. I think this is pretty good! I know this isn't exactly
apples-to-apples (comparing live data sets to number of backup versions),
but I'd say that we have nowhere near 4.5 million versions in our HSM CDSes.
Not with less than 100,000 live data sets on the mainframe.

I hope this helps (statistics follow below my name and company).

Andy Raibeck
Connecticut Mutual
203-987-3521



==========================
Statistics by storage pool
==========================
Pool:           BACKUPPOOL
Files:          66776
Occupancy (MB): 12478.44

Pool:           DISASTER_RECOVERY
Files:          2229540
Occupancy (MB): 299670.82

Pool:           TAPEPOOL
Files:          2128033
Occupancy (MB): 285672.27

Pool:           ARCHIVEPOOL
Files:          34955
Occupancy (MB): 1774.26



======================
Statistics by platform
======================
Platform: NetWare

   Pool:           BACKUPPOOL
   Files:          43705
   Occupancy (MB): 9805.76

   Pool:           DISASTER_RECOVERY
   Files:          1533282
   Occupancy (MB): 196006.36

   Pool:           TAPEPOOL
   Files:          1471736
   Occupancy (MB): 184776.48

   Pool:           ARCHIVEPOOL
   Files:          17841
   Occupancy (MB): 1563.91

   Total NetWare files:          3066564
   Total NetWare occupancy (MB): 392152.51

Platform: AIX

   Pool:           DISASTER_RECOVERY
   Files:          230908
   Occupancy (MB): 8403.79

   Pool:           TAPEPOOL
   Files:          227018
   Occupancy (MB): 7968.26

   Pool:           BACKUPPOOL
   Files:          3890
   Occupancy (MB): 445.61

   Total AIX files:          461816
   Total AIX occupancy (MB): 16817.66

Platform: SQL-BACKTRACK

   Pool:           BACKUPPOOL
   Files:          78
   Occupancy (MB): 1230.51

   Pool:           DISASTER_RECOVERY
   Files:          5314
   Occupancy (MB): 72425.54

   Pool:           TAPEPOOL
   Files:          5236
   Occupancy (MB): 71195.19

   Total SQL-BACKTRACK files:          10628
   Total SQL-BACKTRACK occupancy (MB): 144851.24

Platform: SCO

   Pool:           BACKUPPOOL
   Files:          4516
   Occupancy (MB): 50.09

   Pool:           DISASTER_RECOVERY
   Files:          72111
   Occupancy (MB): 790.50

   Pool:           TAPEPOOL
   Files:          51058
   Occupancy (MB): 610.19

   Pool:           ARCHIVEPOOL
   Files:          16537
   Occupancy (MB): 192.19

   Total SCO files:          144222
   Total SCO occupancy (MB): 1642.97

Platform: OS/2

   Pool:           BACKUPPOOL
   Files:          6821
   Occupancy (MB): 587.15

   Pool:           DISASTER_RECOVERY
   Files:          71173
   Occupancy (MB): 8102.09

   Pool:           TAPEPOOL
   Files:          64352
   Occupancy (MB): 7530.33

   Total OS/2 files:          142346
   Total OS/2 occupancy (MB): 16219.57

Platform: Windows

   Pool:           BACKUPPOOL
   Files:          7766
   Occupancy (MB): 359.32

   Pool:           DISASTER_RECOVERY
   Files:          316752
   Occupancy (MB): 13942.54

   Pool:           TAPEPOOL
   Files:          308633
   Occupancy (MB): 13591.82

   Pool:           ARCHIVEPOOL
   Files:          577
   Occupancy (MB): 18.16

   Total Windows files:          633728
   Total Windows occupancy (MB): 27911.84



============
Final totals
============
Total files:          4459304
Total occupancy (MB): 599595.79