Results 1 to 4 of 4
  1. #1
    Join Date
    Dec 2009
    Thanked 0 Times in 0 Posts

    Default recovery log filling up fast

    I'm currently monitoring a tsm server where the recovery log fills up quite fast.
    (TSM level
    The recovery log is at 13 GB (=the maximum for TSM 5.5)

    I'm wondering why the log fills up so fast.
    The database backup trigger has to kick in around midnight each day because the log exceeds 80% used.

    The normal scheduled database backup is usually around 11 AM (depending on how long the backup stg processes have run), but by midnight, the log is usually at 80% again.

    The database is in rollforward mode.

    On another tsm environment that I am monitoring, with more or less the same amount of data,
    and a recovery log smaller than 13 GB, one db backup per day is enough.

    What can I do to adjust things so that only 1 database backup per day is necessary?
    Where should I look to find out why the log is filling up so fast?
    Could it be because an external scheduler is used that defines heaps of clientactions each day (instead of normzal convential tsm schedules) ?

  2. #2
    Moderator moon-buddy's Avatar
    Join Date
    Aug 2005
    Somewhere in the US
    Thanked 233 Times in 228 Posts


    First, find out what is causing the log to fill up. What is running differently on this server versus the other server?

  3. #3
    Join Date
    Oct 2009
    Thanked 0 Times in 0 Posts


    Check which session is pinning the log by using this command...

    1)show logpinned

    Cancel the session as this is the one which is increasing the log at a drastic pace.

    checkout for any processes running such as backup stg pool and expiration..

    the log size is increasing coz there is more data being backed up..

  4. #4
    Join Date
    May 2004
    Victoria, Australia
    Thanked 0 Times in 0 Posts


    If you are not getting any logpinning issues, you could just simply schedule some additional incremental database backups to run throughout the day, perhaps to a sequential FILE device class such that you don't need to waste tapes or hold up tape drives.

    Generally a lot of log entries indicates that you may still be suffering from logpinning (as suggested above), but you may have some large file clients with lots of changes going on.

Similar Threads

  1. archive log growing very fast
    By iulianr in forum Performance Tuning
    Replies: 5
    Last Post: 11-26-2009, 08:32 AM
  2. MSSQL Transaction log filling up.
    By osi9400 in forum Microsoft SQL Server
    Replies: 1
    Last Post: 06-19-2009, 06:02 AM
  3. Log file growing fast... no idea why?
    By spiffy in forum Performance Tuning
    Replies: 0
    Last Post: 10-01-2008, 09:20 AM
  4. Recovery Logs overcommited, cannot extend new recovery log.
    By kenlee in forum Administrative Client
    Replies: 8
    Last Post: 01-17-2007, 11:18 PM
  5. Log Filling Up Quickly
    By Jcage in forum Performance Tuning
    Replies: 5
    Last Post: 09-07-2006, 04:09 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts