Several different deployment options are available for Archive Manager, depending on organization size and type. The following information can be used to determine a basic specification for an Archive Manager solution, although each organization must be assessed for its own unique qualities and needs.
Sizing is also affected by the Archive Manager message policies applied to Exchange after Archive Manager is implemented. Specifically, hardware requirements will increase if messages are kept on the mail server for only short periods (for example, <15 days), since users will access the Archive Manager system far more extensively than if messages are kept 30 or 60 days.
NOTE: Large organizations and sites with comprehensive disaster recovery (DR) requirements need to consider clustering Microsoft SQL Server and Internet Information Services (IIS) if the archived information is deemed critical to the organization. The information within Archive Manager is a copy of current information and possibly all email information outside of the configured retention policy period; this may affect the requirements.
If the remote sites already have email servers, the servers should be set up to journal locally in order to minimize bandwidth usage of the journaling process. In these cases, the Archive Manager Dataloader can be configured to retrieve the journaled messages from those sites overnight, thereby spreading network traffic over 24 hours instead of eight working hours.
Archive Manager provides the option of installing the Organizational form for ‘Stubbed’ messages. By not installing the form for Microsoft Outlook, the bandwidth requirements of Archive Manager are reduced further as email is not retrieved from the Archive Manager database when browsed via Microsoft Outlook; the email is retrieved only when a link in the message is selected.