Exchange Log Drive - No Space Left ?

So, you have Exchange 2007/2010 - and you run out of space on your log drive, you will need this guide, and good luck

When this happens you cannot mount the database as it needs space on the log folder to write to......so when this happens it usually a sign that the backups have not been running, as this is the reason that the log folder is not cleared down.....

When the happens, you need to act quickly but perform the steps correctly to restore service.......the examples below use CMD2SG6 as an example...

  1. Start a command prompt as an Administrator
  2. Ensure you have started the command prompt as an administrator
  3. No, really ensure you window says “Administrator : Command Prompt” ( if it says “Command Prompt” guess what you have not run it as an administrator)
  4. Change directory to : G:\DB\CMS2SG6DB1
  5. Run the command on the dismounted mailbox: eseutil /mh CMS2SG6DB1.edb
  6. You will get this back :

    Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.03
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...
         Database: CMS2SG6DB1.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,12
Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
     DB Signature: Create time:03/31/2013 00:10:08 Rand:947036789 Computer:
         cbDbPage: 8192
           dbtime: 1521114077 (0x5aaa5bdd)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
    Log Committed: 0-0 (0x0-0x0)
   Streaming File: No
         Shadowed: Yes
       Last Objid: 934232
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
Old Repair Count: 0
  Last Consistent: (0x1BEC95,50,97)  09/16/2013 10:43:01
      Last Attach: (0x1BEC80,9,86)  09/16/2013 10:39:31
      Last Detach: (0x1BEC95,50,97)  09/16/2013 10:43:01
             Dbid: 1
    Log Signature: Create time:06/05/2010 19:04:14 Rand:178481818 Computer:
       OS Version: (6.0.6002 SP 2 NLS 500100.50100)

Previous Full Backup:
        Log Gen: 1794347-1794350 (0x1b612b-0x1b612e) - OSSnapshot
           Mark: (0x1B612F,8,16)
           Mark: 09/02/2013 10:06:28

Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Copy Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Differential Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0

       ECC Fix Success Count: none
   Old ECC Fix Success Count: none
         ECC Fix Error Count: none
     Old ECC Fix Error Count: none
    Bad Checksum Error Count: none
Old bad Checksum Error Count: none

  1. You are looking for the state, this will be one of two values.....
    1. Clean Shutdown – start at sep 8
    2. Dirty Shutdown – start at step 14
  2. If you get a clean shutdown then you need to navigate to the log directory which is : G:\TL\CMS2TL6
  3. Once here you can move the oldest log files, I suggest starting at the oldest version and moving about 3 days which is about 8.9GB of space
  4. Move the files locally to the C: or D: on the server
  5. Once the move is complete re-mount the database
  6. All is good – until the space runs out again
  7. STOP HERE FOR A CLEAN SHUTDOWN
  8. If you get a dirty shutdown then there is slightly a few more steps in fixing the issues
  9. If you get a dirty shutdown you will need to get the Log Required entry from the eseutil utility
  10. Run the command : : eseutil /mh CMS2SG6DB1.edb
  11. You will see one of the entry’s that state “Log Required” this will be in a range like 1831600-1832900
  12. Browse to : G:\TL\CMS2TL6
  13. You will notice the logs are in the format of : E05001BF2C7.log
  14. You need to know if this file or files are in the log required range.....
  15. You need to covert the values from Hex to Decimal
  16. So start-up calculator on the server and put it in scientific mode, like this :
  1. Click on the Hex button
  2. Now if you remember the file was called E05001BF2C7, we need the last 6 digits, there are the Hex values, the crap before the this is the log format
  3. So enter 1BF2C7 into the calculator
  1. Then click the Dec button, and you will get a value that is relevent to the log required index, in this case we have 1831623 – this is within the range in step 17 – DO NOT DELETE THIS FILE, as this is required for the database mount.
  1. Find a file that is not in this range, and then move it to the local C: or D:
  2. Once the move is complete, mo

  1. Mount the database