Export (0) Print
Expand All
Expand Minimize

Public folder store has not had a full backup in more than 60 days

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2007-01-08

The Microsoft® Exchange Server Analyzer Tool queries the public folder store to determine the date and time of the last full backup. If the Exchange Server Analyzer finds that the number of days since the last full backup for a public folder store is greater than 60, the Exchange Server Analyzer displays an error.

The public folder store holds information that is associated with a particular public folder tree, such as how the tree is structured and what folders the tree contains. The public folder store also holds public folder content. A public folder store is made up of a rich-text .edb file, and a streaming native Internet content .stm file.

The mailbox store data and public folder store data in your Exchange Server databases and transaction log files are the most important data to back up in your Exchange Server organization. You can use an Exchange Server database backup to restore a damaged public folder store to a functioning server that is running Exchange Server. You can also use Exchange Server database backups to restore your Exchange Server databases to a different server.

As a best practice, you should perform a full backup of your database files and transaction logs every day. After you complete a full backup of a storage group, the committed transaction log files on the Exchange Server databases are deleted from the server. A full backup provides the advantage of speed in a recovery scenario, because you need only one tape set to restore all data.

noteNote:
It is a best practice to keep transaction log files on a dedicated disk separate from the database files. Not only does this best practice improve database performance, but it also provides fault tolerance in case the database disk is destroyed.
importantImportant:
You must have the required permissions or rights assigned to the user account that you are logged into when you try to back up or restore files and folders. To create Exchange Server backups, you must have domain level backup operator rights. To create backups of your Microsoft Windows Server™ 2003 operating system, you must have at least local backup operator rights.

The backup strategy that you choose for your Exchange Server data will depend on the size of the stores, the speed of backup software and hardware, hardware capacity, and time requirements.

For more information about backup strategies as well as disaster recovery operations, see:

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft