How to increase overall performance of Archive Manager
1) Ensure hardware meets required specifications
2) Disk Queue Lengths and Disk Fragmentation
3) Archive Manager SQL Database indexes, Quest Capacity Manager and Spotlight on SQL Server Enterprise and Basic Checks
4) Full Text Index Settings
5) File locations
6) Reduce number of Enabled Mailboxes
7) Disable stub repair
8) Remove un-necessary mailboxes assigned to you.
1) Ensure hardware meets required specifications
See Page 19 of the Archive Manager 4.4 Planning and Installation Guide for GroupWise or Planning and Installation Guide for Exchange for more information.
On Windows 2003 32bit servers with 3+ GB RAM, ensure the /3GB switch is in the C:\boot.ini file. For more information see: Large memory support is available in Windows Server 2003 and in Windows 2000
2) Disk Queue Lengths and Disk Fragmentation
Monitoring Disk Usage
High average disk queue lengths on any of the drives utilised by Archive Manager will have a negative impact on performance. Particular attention should be paid to the Average Disk Queue for the drive where the Archive Manager Database .mdf file resides. High Average Disk Queue on this drive will result in poor performance of the entire AM system.
See the following articles for more information:
Disk Fragmentation
Please be aware of the "Disk Defragmenter Limitations in Windows 2000, Windows XP, and Windows Server 2003"
Contig is a single-file defragmenter that attempts to make files contiguous on disk. Contig can be used to defragment your AM SQL DB .MDF file. Either stop all AM services and the SQL server before running contig on the .MDF file, or in the case of multiple databases on the same server, stop all AM services and detatch the AM database and run contig, then attach the database again.
Example: contig -v "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ArchiveManager.mdf"
Note: contig will only work if there is free space available.
Third party tools that can defrag SQL databases in real-time include:
3)Archive Manager SQL Database indexes, Quest Capacity Manager and Spotlight on SQL Server Enterprise and Basic Checks
AM DB Table Indexes
Missing indexes on the Archive Manager Database tables can have a negative impact on performance. Run the attached "index_rework_complete.sql" script to ensure that any missing indexes are replaced.
Quest Capacity Manager and Spotlight on SQL Server Enterprise
Quest Capacity Manager for SQL can be used to defragment the Archive Manager database table indexes on the SQL server. The following SQL query will show index fragmentation levels in an Archive Manager database:
select a.index_id, a.object_id, name, avg_fragmentation_in_percent from sys.dm_db_index_physical_stats (DB_ID(N'ArchiveManager'), OBJECT_ID(NULL), NULL, NULL , 'DETAILED') AS a
JOIN sys.indexes AS b ON a.object_id = b.object_id AND a.index_id = b.index_id;
GO
See the attached "Setting up Capacity Manager for Archive Manager" for more information on configuring Capacity Manager with Archive Manager.
Spotlight on SQL Server Enterprise can be used for Operational Monitoring, Diagnostics, Administration and Automated Tuning for SQL Server.
Other basic checks for SQL performance:
When running SQL on 32bit Windows 2003 servers, Enabling AWE Memory for SQL Server will allow SQL to use additional memory.
4) Full Text Index Settings
Optimise the Full Text Index daily if using a version of Archive Manager prior to 4.6.
For versions prior to 4.6 add or edit the following settings in the Archive Manager Configuration Editor to increase performance of message indexing:
Full Text Index Max Message Workers | 1
Full Text Index Merge Factor | 100
Full Text Index Ram Buffer Size MB | 250
Full Text Index Min Merge Docs | 50000
Full Text Index Message Batch Size | 1000
Full Text Index Attachment Batch Size | 100
If using version 4.6 the following configuration settings have been replaced due to enhancements to the Full Text Index:
Full Text Index Max Message Workers | Replaced by FTI Max Worker Count
Full Text Index Timer Interval | Replaced by FTI Worker Idle Poll Msec
Full Text Index Message Batch Size | Replaced by FTI Work Item Max Count
Full Text Index Attachment Batch Size | Replaced by FTI Work Item Max Count
Also with version 4.6 the following configuration settings have been reset with new defaults, it is recommended that you use the default settings:
Full Text Index Min Merge Docs | Sets the minimum size for the lowest level segments. This setting defaults to the number of messages set in the Full Text Index Message Batch Size setting.
Full Text Index Merge Factor | This setting can be used to merge same-sized index files, increasing search performance. The default is 10 files.
Full Text Index RAM Buffer Size MB | Determines the amount of RAM that may be used when buffering added documents and deletions before they are flushed to the Directory. This setting corresponds directly to Lucene's SetRAMBufferSizeMB method. The default is disabled.
Full Text Index Include Recipients | Controls whether or not recipients are added to the Lucene index. The default is False. This setting has historically defaulted to false as the recipients are not searchable in Lucene, but are instead pulled from the Archive Manager database. This setting should remain false.
Also, if you have upgrade to version 4.6 the following configuration settings are no longer used due to enhancements to the Full Text Index and can be removed.
Full Text Index Service Restart Error Count
Full Text Index Service Max Memory
Full Text Index Reset Timeout
Full Text Index Optimize Message Index Location
Full Text Index Optimize Attachment Index Location
Full Text Index Auto Optimize
Full Text Index Optimize Time
Full Text Index Attachment Thread Timeout Minutes
5) File locations
Exchange Store Manager Log Path and Data Loader Log Path - these working directories have little disk overhead.
Full Text Index Location - should be located on fast dedicated disk.
Attachment store - should be located on fast dedicated disk.
SQL Database (.mdf file) and SQL Transaction Logs (.ldf file) - The data file is read/write intensive and the log file is write intensive. These files should be located on different drives to increase performance.
6) Reduce number of Enabled Mailboxes
Uncheck 'Enable Store Management' for disabled and deleted users.
7) Disable stub repair
After upgrading to Archive Manager 4.1.2 or above, Archive Manager will begin attempting to "repair" older stubbed messages which may cause a significant degredation of the speed of processing mailboxes.
Use the following SQL query to disable stub repair:
UPDATE Folder
SET State = ISNULL(State, 0) | 1
WHERE ISNULL(State, 0) & 1 = 0
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center