Announcement

Collapse
No announcement yet.

log drive full

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • log drive full

    Hi,


    My log drive is full now I have to clean some log files which is not require, I forget the eseutil command which will show you which logs files are commited to the database and rest we can delete..

    or wht should be the process if log files drive is full....


    Thanks in advance.

    Rgds

  • #2
    Re: log drive full

    The recommendation would be to do a full backup of the information store using ntbackup or another exchange-aware backup program that will flush the logs after the backup completes.

    Comment


    • #3
      Re: log drive full

      Hi,


      Thanks for the reply..

      Eseutil /mh <database path> this command line help me to see which logs file commited into the databse.

      I have copied all log file into the safe place and delete log file which was not require<basically commited log files>

      By checkpoint file also you can resolve this kind of problem.....

      Rgds

      Comment


      • #4
        Re: log drive full

        Yes, but that is not the recommended way of doing it. Nobody running Exchange in a production environment would ever do this except in an extreme emergency. The recommended solution is to backup the information store using ntbackup or another exchange-aware backup program that will flush the logs after the backup completes. Are you not backing up the information store?

        Comment


        • #5
          Re: log drive full

          Hi,

          Thanks for the reply...


          Yes we do full backup everyday using ntbackup(scheduled) but due to some reason its not happening for last 5 days and due to which log drive gets full ,,

          When I tried to monunt the DB it gives me error and in offline mode log files will not get flush..

          & I had tagle this kind of problem before using eseutil but dint remember the parameter..

          Putting this kind of oprion in forum will guide others too.

          is there any other option except full backup (when your DB is not mounting and you can not perform the backup)

          correct me if I am wrong...

          Rgds

          Comment


          • #6
            Re: log drive full

            If you have an Exchange-aware backup program you could try backing up the transaction logs only, which may work because the database doesn't need to be online for that (if I'm not mistaken) then the logs will be flushed and you can then mount the database. The other thing to try would be to temporarily turn on circular logging and then mount the database. This might let Exchange flush the logs and mount the database. Afterwards you can turn circular logging back off.

            Comment


            • #7
              Re: log drive full

              Hi,

              Thanks for your valuble input, I have added it...

              Comment


              • #8
                Re: log drive full

                Even in an emergency there is no reason to remove logs or enable circular logging. Simply compress the log files and then run a backup manually through NTBACKUP to flush the logs. Basically what you have at the moment is the situation where if you had server failure you would lose 5 days of email.

                Simon.
                --
                Simon Butler
                Exchange MVP

                Blog: http://blog.sembee.co.uk/
                More Exchange Content: http://exchange.sembee.info/
                Exchange Resources List: http://exbpa.com/
                In the UK? Hire me: http://www.sembee.co.uk/

                Sembee is a registered trademark, used here with permission.

                Comment

                Working...
                X