Chat now with support
Chat mit Support

Archive Manager 5.9.5 - Administration Guide

Administration menu Authentication modes Data loaders Download tools Federated Search Instances Groups Index management Logins Security roles Storage location Message tags Proxy credentials Alert Service Policies Exclusion rules Mail servers Mailbox assignment Mailboxes Lync servers Lync user assignment Lync users Reports Message policies Message policy assignments Retention policies Tenants System maintenance Log Viewer Exchange Utility Administering in a hosted Exchange environment Appendix A: Moving database or attachment store Appendix B: Enabling generating publisher evidence

About system maintenance

Some Archive Manager features and components require occasional maintenance to function efficiently. For example, some components generate data that eventually becomes obsolete and should be deleted from the disk so it does not burden disk-access functions. This chapter explains how to maintain your Archive Manager system for optimal performance.

Cleaning up "scratch" tables

Archive Manager includes a script that, when invoked, will delete all of the old temporary "scratch" tables that the program generates for searches and other functions. This CleanUp script is configured in the Archive Manager Configuration Console.

You can schedule the script to run at the same time every day (for example, 2:30am local time), by entering the run time as the CleanUpTime setting in the Configuration Console. Since the Retention Engine also uses temporary tables, the CleanUp script should not be run at the same time as the Retention Engine. Most admins choose to run the CleanUp script before the Retention Engine, which may occasionally run for prolonged time periods.

The CleanUp script is a SQL server job that stores its scheduled execution time in its own SQL Job Properties, and the script will delete old tables only if the SQL job time matches the CleanUpTime setting in the Configuration Console. If, for example, someone changes the CleanUpTime setting, then it will be different from the last-saved SQL job time, and the script will not delete old tables at the next CleanUpTime occurrence. Instead, when the script finds such a discrepancy, it will simply reset the SQL job time to match the CleanUpTime, and the script will then delete the old tables at the next occurrence of the CleanUpTime.

Cleaning up the AfterMail_Temp database

The ClearSearchCache SQL job, which is used to clean up the AfterMail_Temp database, may inadvertently delete the tables that are created for retention, rendering the Retention Engine inoperable until scripts are re-run to recreate the tables. The ClearSearchCache SQL Job may also mistakenly leave behind some temporary search tables that should be deleted: files with names prepended with DOMAIN\SERVICE_NAME and then the table names.

If you run the ClearSearchCache program subroutine, you may need to run the CleanTempTable script to clean up the AfterMail_Temp database.

Log Viewer

•
About the Log Viewer
•
Log Viewer menus and toolbar
•
How to ...
•
Configuring logs
•
EventLogAppender
•
TraceAppender
•
RollingFileAppender
•
ColoredConsoleAppender
•
Additional information
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen