You can use execute diskshadow (which is built into server 2008) before 
the backup to make a shadow copy of the drive. Once the backup is 
complete and shadow is deleted the logs will truncate.

http://theessentialexchange.com/blogs/michael/archive/2009/01/23/exchange-2007-and-windows-2008-using-diskshadow-for-online-exchange-backup-part-5-of-7.aspx

David


On 03/20/2012 02:02 PM, Conrad Lawes wrote:
> I am presently running Bacula 5.26 in production for a weeks now.   I 
> recently noticed that the bacula agent (v5.1) running on the Exchange server 
> does not truncate the Exchange transaction log after a full backup is 
> completed. As a result, the partition containing the transaction log is 
> filling up.
>
>
> The Exchange server is running on Windows 2008 SP2 64-bit.
> Is there a way to configure Bacula to truncate the exchange transaction log 
> are a successful full backup?
>
> Thanks.
>
> Conrad
>
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users