<div>
You need to run a full backup to flush the logs properly. It is necessary from a restore point of view as well, rather than having large logs on an image.<br />
<br />
You can even run ntbackup for this.
</div>


You need to run a full backup to flush the logs properly. It is necessary from a restore point of view as well, rather than having large logs on an image.

You can even run ntbackup for this.

<div>
Use ntbackup for a differential backup of the log files. Then ntbackup only backups the log files and flushed them. there is no need for a full backup
</div>


Use ntbackup for a differential backup of the log files. Then ntbackup only backups the log files and flushed them. there is no need for a full backup

<div>
<a href="http://support.microsoft.com/kb/182961" rel="ugc nofollow">http://support.microsoft.com/kb/182961</a> will show you what logs have been committed.<br />
you can get rid of log files once they have been committed.<br />

</div>


http://support.microsoft.com/kb/182961 [http://support.microsoft.com/kb/182961] will show you what logs have been committed.
you can get rid of log files once they have been committed.


<div>
The doc is for Exchange 5.5 and 2000. Get the one for 2003 for the correct steps.
</div>


The doc is for Exchange 5.5 and 2000. Get the one for 2003 for the correct steps.

<div>
<div class="content wysiwyg-content">
We would like to use a bare metal backup solution on our exchange servers. Essentially the backup solution will create a full image once a week and incremental's every 4 hours the rest of the week. Since an image of the server is taken it does not mark the store as being backed up and flush the logs. I am trying to avoid using circular logging at all cost and would like to setup some type of script that would run after my image completes.
</div>
</div>


We would like to use a bare metal backup solution on our exchange servers. Essentially the backup solution will create a full image once a week and incremental's every 4 hours the rest of the week. Since an image of the server is taken it does not mark the store as being backed up and flush the logs. I am trying to avoid using circular logging at all cost and would like to setup some type of script that would run after my image completes.

How fo flush Exchange logs manually

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.