Question : circular logging for Exchange 2003 backend servers

I'm in the middle of implementaing a DR site.  I plan to replicate my Exchange DB's offisite.  I'm using VEEAM Backup and Replication software.  It will replicate my changed blocks once a day to my remote site.  What I'm noticing is that my backend Exchange servers are getting 6 GB's a day in changed blocks.  I noticed that the \MDBDATA folder seems to be the problem for it's constantly changing and it's anywhere from 6-10 GB's per day per server.  This is alot of data to replicate per server offsite.  I thought about enabling circular logging for this will reduce the amount of logs files.  Currently I'm backing up my Exchange databases via FULL method every evening.  So, I'm not worried about the limitation of not being able to perform differentials and incrementals.  Now, as I understand if the infostore DB crashes I won't be able to restore emails since the last backup...  This doesn't concern me too much for I have GFI Mail Archiver in place.  Every email received/sent gets sent to a SQL DB.  In the event of disaster emails received during that day users can simply access the email archiver and retrieve from there.  They can even restore back to Outlook from the archiver... So..  With my configuration and my goal to reduce the \MDBDATA folder will this work?  Am I taking too big of a risk?

Answer : circular logging for Exchange 2003 backend servers

You can use a seperate part of maintenace plan functionality to do this - Maintenance Cleanup Task:
http://msdn.microsoft.com/en-us/library/ms177182.aspx

Suggest you include it as a conditional part of the sub plan so old backups only get cleaned up once a new backup has been created.