Wanda,
I don't have access to the dsmserv.opt, but I will discuss this with
the admins tomorrow.
I don't think "ALLOWREORGTABLE NO" is turned on, because I have been
seeing messages like:
05/12/2010 06:41:31 ANR0293I Reorganization for table Backup.Objects
started.
05/12/2010 06:41:36 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 07:10:31 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 07:19:48 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 07:21:44 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 08:25:08 ANR0000I Table reorganization for Backup.Objects
paused.(SESSION: 10542, PROCESS: 1)
05/12/2010 08:45:13 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 12:05:28 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 12:08:03 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 12:09:28 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 12:18:04 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 13:46:04 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 13:46:44 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 13:51:45 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 14:01:25 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 14:08:39 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 15:02:09 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 15:16:38 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 15:24:28 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 15:33:21 ANR0000I Table reorganization for Backup.Objects
paused.
05/12/2010 15:36:31 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 15:36:43 ANR0000I Table reorganization for Backup.Objects
paused.(SESSION: 13263, PROCESS: 16)
05/12/2010 15:56:33 ANR0000I Resuming table reorg after pause for
Backup.Objects.
05/12/2010 18:16:22 ANR0294I Reorganization for table Backup.Objects
ended.
So, the reorg of that table ran off and on for 12 hours. There were
pauses in it, but I can see how this would generate a lot of logs.
Best Regards,
John
-------- Original Message --------
Subject: Re: [ADSM-L] TSM 6.1 automatic database backups
From: "Prather, Wanda" <wprat...@icfi.com>
Date: Thu, May 13, 2010 7:42 pm
To: ADSM-L@VM.MARIST.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
