ADSM-L

Re: [ADSM-L] TSM 6.1 automatic database backups

2010-05-13 23:07:32
Subject: Re: [ADSM-L] TSM 6.1 automatic database backups
From: "John D. Schneider" <john.schneider AT COMPUTERCOACHINGCOMMUNITY DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 13 May 2010 20:06:29 -0700
Wanda,
     I will check out ALLOWREORGTABLE NO.  Thanks, that could be very
important.

     As for the second issue, can anybody tell me why the automatic
database log isn't running, even when the filesystem for the archives is
filling up?  What triggers it, and how do I control it?  
    I guess I can just write a script to monitor it and perform the
"backup db" when the filesystem gets close to full, but since this is
supposed to be an automatic feature, it seem like something is wrong
here.

Best Regards,

John D. Schneider
The Computer Coaching Community, LLC
Office: (314) 635-5424 / Toll Free: (866) 796-9226
Cell: (314) 750-8721



-------- Original Message --------
Subject: Re: [ADSM-L] TSM 6.1 automatic database backups
From: "Prather, Wanda" <wPrather AT ICFI DOT COM>
Date: Thu, May 13, 2010 7:42 pm
To: ADSM-L AT VM.MARIST DOT EDU

John, 
Make sure you have in the dsmserv.opt file:
ALLOWREORGTABLE NO

There is a bug in 6.1 that lets the automatic DB table reorgs go nuts
with the log.


1) On one instance, each day a full TSM DB backup gets done, but within
about 16-18 hours, the archive filesystem is filling up. The archive
filesystem is 50GB, which is of course much bigger than it was under
5.5. We have only migrated a fraction of the TSM clients over to
this instance, so I shudder to think how much archive space is going to
be require when all the TSM clients are in place. Can anybody give me
any tips on reducing the amount of log data that gets created so it
doesn't fill up so fast?


2) I used "set drrecovery dbb_full" to point this to a FILE type
devclass where we want the DB backups to go. According to the manual,
this should cause the database to get automatically get backed up. But
the manual is totally obscure about how full it is going to get before
it kicks off the backup. It describes the vague criteria, but doesn't
seem to give the admin any controls. We have seen it 98% full, and
gave up and performed the 'backup db' manually. Can anybody give me
more details than the manuals have about how this works and how to
control it?


Best Regards,

John D. Schneider
The Computer Coaching Community, LLC
Office: (314) 635-5424 / Toll Free: (866) 796-9226
Cell: (314) 750-8721