How to use Eseutil.exe to perform actions while databases are online

Some new tricks I learned today on good old Esetuil.exe tool in Exchange 2010 SP3 and Exchange 2013.

We all know, when database is online and mounted, you won’t be able to perform any actions with Eseutil.exe.
For example,

Get-MailboxDatabaseCopyStatus returns

Database e15db3 is mounted on Exchange 2013 server mbx1.

If you try to run eseutil /mh or eseutil /y, you would receive following error,

Now, with new Eseutil switches introduced in Exchange 2010 sp3 and Exchange 2013, you can perform actions while database is online and mounted.

/vss switches utilize Windows VSS engine and snapshot to perform the tasks that you traditionally have to dismount database first.

If you run eseutil /mh /vss, it will dump database info with “Dirty Shutdown” status, because it did not play the missing logs into the snapshot.
So, you want to run eseutil /mh /vss /vssrec eNN “logpath” for optimal result.


If you want to perform quick database backup, you can now run eseutil /y /d /vss /vssrec to achieve that, without using any type of backup software. This is my favorite, and the most useful action!


You can verify the backup file with eseutil /mh


You now, have an up to date database backup!


19 thoughts on “How to use Eseutil.exe to perform actions while databases are online

  1. Haven’t tried it yet, but by chance does it remove/truncate TLOGs too? If so this would be a great backup solution for small shops. Otherwise Windows Backup will still be required 😦

    Surprised I hadn’t heard about this, seems worth MS calling out in their EHLO blog on SP3!

  2. Pingback: NeWay Technologies – Weekly Newsletter #41 – May 2, 2013NeWay | NeWay

  3. Hi Ron,
    Thanks a lot for such a highly informative post. But I fear to share that Eseutil.exe fails to provide expected result in severe troublesome situations and in this situation, no log truncation is done.

  4. Hi everybody,

    I followed this procedure without having read the comments…
    I expected that the logs could be truncated, so how could I truncate the logs please?

  5. After this command, i moved manually all the logs to another folder, but all the logs are being rebuilt since i resume the database in production! How could i solve that?

  6. The goal of my initiative was to reduce the space disk used by the logs. That’s why i started to try to clean my database “dirty shutdown” state, and after to make a backup, in order to have the logs truncated.
    I don’t know if the command i used has truncated anything, but i didn’t earn any Mb on the drive.
    I have a 470GB database, and a logs folder of 603GB! Could you help me how could i deal with that?

  7. Hi everybody,
    I launched a full backup of my server with Windows server backup, but the logs are still as big as before the backup! didn’t earn space on my hard disks.
    How could i manage to purge these huge logs?
    Many thanks…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s