>Currently I am managing an environment that holds all its mailboxes in one database using exchange 2003 the database is almost 1TB in size with the average mailbox being above 10GB having said this the recommended max size for each mailbox is 2GB so you can imagine it has been quite a hassle managing this exchange environment.
The backup solution is Symantec Backupexec which was managing well at the start however the database then became corrupt causing the daily online defrag to report with checksum error and causing backups to fail. Effectively I am unable to restore the database should a DR be required.
Anyhow since then two new mailbox stores have been created and now I am moving mailboxes from the original database to the newly created ones. Problem now is that excess logs are being created and so with limited storage space I am running out of disk space and the move is aborted.
This is where circular logging proves useful in that it recycles the logs where it creates log1, log2, log3, log4 and then going back to overwrite log1. This is not recommended but in my case where I have limited disk space I need to enable this option in storage group settings and then move the mailboxes quickly and swiftly.
This article here explains this in detail nicely
In the meantime I have also addressed my problem on the trustly msexchange forums and so far have received good replies here