locked
Transaction logs filled out RRS feed

  • Question

  • The volume stored transaction logs for a database is filled out and no space left. I would like to know the instructions for safely removing the log files for this Exchange 2010 database.

    Note: - We have Database copy enabled using DAG. This database has one active and 2 passive copies.

    Thanks in advance...

    Monday, April 18, 2011 8:19 PM

Answers

  • Two ways...1) perform a Full backup, this will flush the logs and is the recommended approach.  2) enable circular logging.  This should only be used if you can accept that you will only have point in time restore capabilities from you last successful backup.
    Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Lync 2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington
    • Marked as answer by -Edatha- Tuesday, April 19, 2011 8:24 PM
    Monday, April 18, 2011 8:23 PM
  • To save you in teh future I always create or dump in some large files (iso's or whatever) that in the event of a full disc can be deleted to create some space quickly to get everything going.

    running out of transaction log sequence with Exchange 2010 or 2007 is very unlikely since the numbers haev increased a lot.

     


    lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com
    • Marked as answer by -Edatha- Tuesday, April 19, 2011 8:24 PM
    Tuesday, April 19, 2011 8:14 PM
  • Well, the criteria for log truncation is here.

    http://technet.microsoft.com/en-us/library/dd335158.aspx

     

    I agree with Tim, if the backup isnt working, I would enable circular logging and let Exchange handle the log truncation with replicated copies. Though in theory you could apply in principle, the same KB to all the copies of the store when manually removing the logs.

    Dont forget you also have the ability to reseed the passive nodes.

    • Marked as answer by -Edatha- Tuesday, April 19, 2011 8:23 PM
    Tuesday, April 19, 2011 8:19 PM

All replies

  • Two ways...1) perform a Full backup, this will flush the logs and is the recommended approach.  2) enable circular logging.  This should only be used if you can accept that you will only have point in time restore capabilities from you last successful backup.
    Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Lync 2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington
    • Marked as answer by -Edatha- Tuesday, April 19, 2011 8:24 PM
    Monday, April 18, 2011 8:23 PM
  • Thanks I was actually looking for the procedure to manually remove the transaction logs in DAG environment. Sorry for being less descriptive in the question.

    In exchange 2003 we have to dismount the databases of the storage group and mount it after moving the logs. In current scenario how can I move the logs manually for the exchange 2010 database? I was able to find the KB for exchange 2003 but not for Exchange 2010.

    Ref : http://support.microsoft.com/kb/240145

    Tuesday, April 19, 2011 12:10 PM
  • It is not supported to manually delete the transaction logs.  Are you not performing backups?  If not, then I suggest you enable circular logging.  This can be done on the Database properties - Maintenance tab.

    http://technet.microsoft.com/en-us/library/dd297937.aspx


    Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Lync 2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington
    Tuesday, April 19, 2011 1:13 PM
  • Thanks I was actually looking for the procedure to manually remove the transaction logs in DAG environment. Sorry for being less descriptive in the question.

    In exchange 2003 we have to dismount the databases of the storage group and mount it after moving the logs. In current scenario how can I move the logs manually for the exchange 2010 database? I was able to find the KB for exchange 2003 but not for Exchange 2010.

    Ref : http://support.microsoft.com/kb/240145


    That article still applies if you need to remove logs, though its also best to let backups do the heavy lifting for you.

     

     

    Tuesday, April 19, 2011 6:21 PM
  • I have already run the backup and cleared the files however i am curious to know the procedure to move the logs manually. In case of manual removal do we need to remove the logs for all three data base? (One active and two passive). This information will be handy when we do log sequence reset or if the transaction log files are not purged due to some issue with backup. Thanks for your help and time..

    Tuesday, April 19, 2011 7:50 PM
  • To save you in teh future I always create or dump in some large files (iso's or whatever) that in the event of a full disc can be deleted to create some space quickly to get everything going.

    running out of transaction log sequence with Exchange 2010 or 2007 is very unlikely since the numbers haev increased a lot.

     


    lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com
    • Marked as answer by -Edatha- Tuesday, April 19, 2011 8:24 PM
    Tuesday, April 19, 2011 8:14 PM
  • Well, the criteria for log truncation is here.

    http://technet.microsoft.com/en-us/library/dd335158.aspx

     

    I agree with Tim, if the backup isnt working, I would enable circular logging and let Exchange handle the log truncation with replicated copies. Though in theory you could apply in principle, the same KB to all the copies of the store when manually removing the logs.

    Dont forget you also have the ability to reseed the passive nodes.

    • Marked as answer by -Edatha- Tuesday, April 19, 2011 8:23 PM
    Tuesday, April 19, 2011 8:19 PM