<div>
Thanks for the comments, I had a feeling that I would not be able to do this without a 3rd party product.
</div>


<div>
<div class="content wysiwyg-content">
We are going to be replacing our single Exchange 2003 server with a single Exchange 2010 server and I am trying to come up with a backup strategy. We currently have 70 users and a 60 GB database. After we upgrade to 2010, I plan to create archive mailboxes for everyone in a second database, which I'm expecting to be 200GB in size. I plan to continue backing up the server and main mailbox database nightly, but I'd only like to do quarterly backups of the archive database. With the default retention policy (archive everything older than 2 years) running continuously, the archives are going to be updating daily. I would like to be in control of the archiving; to not allow users to archive themselves, and to only have auto-archiving done right before I know I'm going to run a backup. Is this possible? 
</div>
</div>


We are going to be replacing our single Exchange 2003 server with a single Exchange 2010 server and I am trying to come up with a backup strategy. We currently have 70 users and a 60 GB database. After we upgrade to 2010, I plan to create archive mailboxes for everyone in a second database, which I'm expecting to be 200GB in size. I plan to continue backing up the server and main mailbox database nightly, but I'd only like to do quarterly backups of the archive database. With the default retention policy (archive everything older than 2 years) running continuously, the archives are going to be updating daily. I would like to be in control of the archiving; to not allow users to archive themselves, and to only have auto-archiving done right before I know I'm going to run a backup. Is this possible? 

Thanks for the comments, I had a feeling that I would not be able to do this without a 3rd party product.

Exchange 2010 Personal Archive Database Backup Strategy

We are going to be replacing our single Exchange 2003 server with a single Exchange 2010 server and I am trying to come up with a backup strategy. We currently have 70 users and a 60 GB database. After we upgrade to 2010, I plan to create archive mailboxes for everyone in a second database, which I&#39;m expecting to be 200GB in size. I plan to continue backing up the server and main mailbox database nightly, but I&#39;d only like to do quarterly backups of the archive database. With the default retention policy (archive everything older than 2 years) running continuously, the archives are going to be updating daily. I would like to be in control of the archiving; to not allow users to archive themselves, and to only have auto-archiving done right before I know I&#39;m going to run a backup. Is this possible? 

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.