Re: ADSM concern on Database size.

Kelly,

I run a full on sat/sun; it takes about 8 hours.  The rest
of the week I run an incremental.  The incremental is scheduled
for 15:30 but lately I have also been getting a triggered incremental
before that.

Bill
- -
In <00a501c0bc72$123e2490$0602a8c0@lipstr>, on 04/03/01
   at 03:41 PM, "Kelly J. Lipp" <lipp AT STORSOL DOT COM> said:

>Bill,

>How long is a db backup taking?  Are you doing full db backups daily or do
>you use a full/incremental scheme?

>My experience has shown that a db restore is just about as fast as db
>backup.  That is once the process starts reading data from the tape.  The
>most annoying thing about restoring the db on NT, if you have to rebuild the
>db and log volumes, is the length of time it takes to format those volumes.

>I looked at one of the db volumes using a text editor.  The word eric
>appears over and over and over...  Who is Eric?

>Kelly J. Lipp
>Storage Solutions Specialists, Inc.
>PO Box 51313
>Colorado Springs CO 80949-1313
>(719) 531-5926
>Fax: (240) 539-7175
>Email: lipp AT storsol DOT com or lipp AT storserver DOT com
>www.storsol.com
>www.storserver.com


>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
>Bill Colwell
>Sent: Tuesday, April 03, 2001 10:53 AM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: ADSM concern on Database size.


>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?

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