<div>
<div class="content wysiwyg-content">
Question regarding Exchange 2010 public folder databases and log truncation. &nbsp;We use to have public folder databases on 2 of our exchange 2010 servers. &nbsp;I've added the public folder databases to the remaining exchange servers in our environment and made them replicas. &nbsp;We are in a completely centralized environment where we have 3 main exchange servers hosting all of exchange databases out of our main datacenter and another 3 exchange servers in our DR site. &nbsp;All servers are a member of the DAG and host copies of all datbases in the environment. &nbsp;I've added public folder databases to all servers to ensure complete redundancy. &nbsp;The original 2 public folder databases are being backed up using of backup software SnapManger for Exchange which will truncate the logs after the backup. &nbsp;Correct me if I'm wrong in 2010 public folder databases are not DAG aware so the logs will not get truncated on the other replicas until I run backup on these databases as well? &nbsp;Unlike DAG member databases where I &nbsp;only need to backup one copy of each database and the logs will truncate on each member node for the databases backed up.
</div>
</div>


Question regarding Exchange 2010 public folder databases and log truncation.  We use to have public folder databases on 2 of our exchange 2010 servers.  I've added the public folder databases to the remaining exchange servers in our environment and made them replicas.  We are in a completely centralized environment where we have 3 main exchange servers hosting all of exchange databases out of our main datacenter and another 3 exchange servers in our DR site.  All servers are a member of the DAG and host copies of all datbases in the environment.  I've added public folder databases to all servers to ensure complete redundancy.  The original 2 public folder databases are being backed up using of backup software SnapManger for Exchange which will truncate the logs after the backup.  Correct me if I'm wrong in 2010 public folder databases are not DAG aware so the logs will not get truncated on the other replicas until I run backup on these databases as well?  Unlike DAG member databases where I  only need to backup one copy of each database and the logs will truncate on each member node for the databases backed up.

Exchange 2010 Public Folder Databases

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.

Exchange

The term "Backup" means the methods and processes involved to copy computer data (system data as well as application data) to media other than the ones where the data originally live (disk, tape, optical, cloud). "Restore" in turn means the methods and processes involved in data recovery, i. e., bringing back copied computer data to their original location. Backup/Restore primarily serves as a means of protection against data loss, be it due to disaster, corruption or sabotage. It can also be used for recovering data from an earlier point in time and even for cloning machines or applications. There is a wide variety of backup/restore software available, from expensive commercial products to free or open source tools.

Storage Software

Disaster Recovery is the planning for and creation of policies and procedures related to the resumption or continuation of an organization's functions following a catastrophic event. The term is most frequently used in relation to failure of networks, but DR preparations also include other business systems and personnel considerations.