Hello Vijay,

  I had your problem too once (although I'm running 3.1)
  The remedy is to backup up the ADSM DB, e.g. do a "backup db"
  Once the backup is done the recovery log will be cleared and you have
another 5 GB of transactions
  before it happens again (so do another "backup db" before. I do it at a
fixed time every day from cron).


Could you please post back to the mailing list when you feel cetain
that you know what corrected you problem.
I suggest you then use the subject line "SUMMARY: LOG usage over 100% -
backups failing"


-- good luck
Peter Koblauch
Peter Koblauch







Vijay Havaralu <vhavaralu AT CHUBB DOT COM>@VM.MARIST.EDU> on 12/11/2000 
08:36:26
AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Peter Koblauch/Corporate/Manulife)
Subject:  LOG usage over 100% - backups failing


Hello every one,
We are running tsm-server ver 3.7.20 on aix 4.3.2 with about 400 gb per day
backup.
Our adsm db-size is close to 100 gb and growing daily.
Almost each day log is overflowing with 100%, all backups fails, and server
recovers & continues
We are already using max 5.4 gb of log and can not increase any more on log
volume.

I appreciate, if anybody has any solutions this problem to reduce log usage
or extend log beyond 5.4gb.

Thanks, vijay.