Bill,

how quickly does your 121GB db backup & restore?  How long does reclamation
run?

Steffan

At 12:52 PM 4/3/2001 -0400, you wrote:

David - I am running tsm 3.7.4 on os/390 r6.  I do have a much bigger
database.
It has continued to perform well.  Here is a 'q bd'  --
adsm> q db f=d

          Available Space (MB): 121,888
        Assigned Capacity (MB): 121,888
        Maximum Extension (MB): 0
        Maximum Reduction (MB): 12,008
             Page Size (bytes): 4,096
            Total Usable Pages: 31,203,328
                    Used Pages: 28,128,310
                      Pct Util: 90.1
                 Max. Pct Util: 90.2
              Physical Volumes: 52
             Buffer Pool Pages: 65,536
         Total Buffer Requests: 100,564,851
                Cache Hit Pct.: 98.06
               Cache Wait Pct.: 0.00
           Backup in Progress?: No
    Type of Backup In Progress:
  Incrementals Since Last Full: 2
Changed Since Last Backup (MB): 1,152.03
            Percentage Changed: 1.05
Last Complete Backup Date/Time: 04/02/2001 15:36:25


As to worrying about db restore times, as always, it depends.  How fast is
your cpu and disk subsystem?  What restore time is expected? Demanded?
If you can get the disk space for a short time, you can create a new
instance of
tsm and restore your production db into it to practice db restores.


--
--------------------------
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------



In <OF26F5AAE2.D76B8B53-ON85256A23.00532334 AT humana DOT com>, on 04/03/01
   at 12:52 PM, "David Browne." <dbrowne AT HUMANA DOT COM> said:

>One of our ADSM databases runs on  OS/390 2.10  and is 44GB.
>Does anybody have a recommendation for how big you should let the database
>get?
>Does anyone have one on OS/390 that's much bigger?
>Is there a limit on the size?
>I'm concerned about the length of time it would take to recover.
> Are there other considerations?