none
Possible to force log file to commit into the database files and delete them?

    Question

  • I'm doing a migration test (simulation) using a VM for the new Exchange 2007 SP1.

    In the old Exchange 2000 server, total database size is about 19GB.
    In the new Exchange 2007 server, the (virtual) hard disk free space is 50GB.  I thought that should be enough for the migration test, but it turns out that I'm running out of free space soon (I've got 9GB left as I'm writing this)!

    I'm pretty sure the problem comes from the log files.  So I immediately change "Storage Groups" to use "circular logging".  However, log files are still there.  Is there a way to force the existent log files to commit to the database and disappear?
    Wednesday, May 06, 2009 11:37 AM

Answers

All replies

  • If you take full backup, that should delete committed transaction logs.

    But you don't have any backup plan im-place then here is the method to delete/move comitted transaction logs with ExTRA and without checking with eseutil and doesn't require to dismount the DB.

    Move Committed Exchange Transaction Logs

    Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
    • Proposed as answer by ismail yilmaz Wednesday, May 06, 2009 12:23 PM
    • Marked as answer by Horinius Wednesday, May 06, 2009 12:32 PM
    Wednesday, May 06, 2009 11:55 AM
  • Yes!  Database Recovery Management is great!  Thanks :D
    Wednesday, May 06, 2009 12:33 PM
  • Yeh! :)

    And make sure that you are taking full backup of Excahnge database regularly in case circuler logging is enabled or deleted committed transaction logs manually, which helps you incase any failuer event occurs....

    Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
    Wednesday, May 06, 2009 12:43 PM
  • It's OK.  It's just a VM (virtual machine).  And it's for a migration simulation.  I'm just running out of space.
    Wednesday, May 06, 2009 12:46 PM
  • Oh kewl...! I thought you are doing this in production :)

    But it is good to do in test as a POC before production....

    Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
    Wednesday, May 06, 2009 12:50 PM
  • My production server will have a "partner" server using DPM to backup data, but I have no idea how to set up DPM for the moment.  So I think I'll also periodically remove log files manually :D
    Wednesday, May 06, 2009 1:21 PM
  • I've just found that there's a file called ExTRA.....xml occupying all the C: disk!!

    I'm trying to recover disk space in D: and now my C: is totally full.  Very ridiculous.  Really wondering how Microsoft's software engineers are doing their job...
    Wednesday, May 06, 2009 3:15 PM
  • Well, the tool is basically for moving log files so you need to give the path of location where you have enough space, you could share the network drive where you have enough space and give that path. This tool is mainly intended for production environment where normally admins move the logs at some place for safety and don't remove immediately. In your case it is test environment so you can move it somewhere and delete those. Microsoft is building tools for ideal situation and it is upto us how we use them based on our situation.... :)
    Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
    Wednesday, May 06, 2009 3:22 PM
  • No no, I didn't point those to-be-removed log files to C:  I pointed them to a network shared folder.  But for some reason, this monster ExTRA xml file (a log file?) is created in
    C:\Users\admin\AppData\Roaming\Microsoft\ExTRA

    Wednesday, May 06, 2009 3:45 PM