Chat now with support
Chat mit Support

MessageStats 7.8 - Deployment Guide

MessageStats Architecture Overview Planning for Deployment Deployment Recommendations and Solutions

Create an Exchange Server List

To scope out your MessageStats deployment, you need information about your Exchange organization topology, and about the network latency between your Exchange servers and the servers that will host the MessageStats data collectors.

Create a list of your Exchange servers, showing the server functions and physical geography. (To determine the location of the Exchange servers, you can use the Microsoft Exchange Administrator.)

Determine Exchange Server Latency

Once you have a list of Exchange servers, collect ping statistics and server connectivity details from your Exchange servers to the following:

•
candidate servers that may host the MessageStats Scheduler Service
•
candidate locations of the MessageStats data collectors (Task Execution Servers).

This information will assist in determining the optimal locations of the MessageStats Scheduler Server and of the Task Execution Servers.

Estimate the Exchange Tracking Log Sizes

For each Exchange server in the list, verify that Exchange tracking is turned on and that the tracking log folder is shared. The default location of the folder is as follows for the various releases:

Exchange 2010
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ MessageTracking
Exchange 2013/2016/2019
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\ MessageTracking
To estimate the average size of each tracking log for each Exchange server
1
View each Exchange server tracking log share.
2
Create a file list from each share.
3
Calculate the average size of the tracking logs per server.

Exchange servers usually keep seven days of tracking logs. A week's amount of log files can provide a reliable average per server.

Use this information to obtain insight about the disk space needed on each Task Execution Server to analyze and process all the tracking logs. This information also helps to decide whether to use the MessageStats tracking log compression utility to reduce network traffic.

Identify Data Collection and Storage Requirements

Data requirements are affected by two considerations:

•
What information is gathered from what Exchange objects?
•
How much historical information must be retained?

This information can assist in estimating the storage requirements. You can use the MessageStats database size estimation tool which is available from the Support portal at https://support.quest.com/.

What information is gathered from what Exchange objects?

MessageStats can collect a number of Microsoft Exchange object characteristics, some of which you can exclude from the gatherings.

In addition to the Exchange core information that is gathered by a Default Gathering task, information that can be gathered includes: distribution group membership, detailed audit information, and public folder information.

How much historical information must be retained?

To estimate the storage capacity that is needed on the SQL Server that hosts the MessageStats database, you need to know how much historical reporting is required. By retaining historical information, you can use MessageStats to view trend and forecast information for your Exchange organization.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen