System Requirements for Netmail Archive
Minimum Requirements for Netmail Archive 5.2.xUpdated March 19, 2014
This document stipulates the minimum and recommended hardware requirements as well as the relevant system and software requirements for the Netmail Archive solution to operate at its expected performance level.
The term “server” or “node” can be interpreted either as a physical server or as a virtual machine, depending on your deployment scenario. When deployed as virtual machines, each node must nevertheless be allocated the resources described herein, and guidelines provided by Messaging Architects for connectivity to storage must be strictly adhered to.
The tables below list the characteristics of the two types of nodes. Additional information about the various software and system components constituting the environment in which the solution is deployed is included as well.
An Archive Node such as the one described in the first table below has been benchmarked as capable of
handling 1 GB of email data per hour. The same goes for the Index Node described in the second table. The two types of nodes are usually made to run in tandem. Actual performance varies according to the number of items, number of attachments, sizes of attachments, etc. Deviation from the specifications provided herein will affect performance.
Recommended Netmail Deployments
Archiving Email RetentionEmail Retention without Journaling Attachment Management Migration to Exchange 2010+ & Office 365 GroupWise 6.5.1+ & GroupWise 7.0.0 Netmail Archive 5.2 Netmail Archive
5.2 N/A N/A N/A
GroupWise 7.0.1+
Netmail Archive 5.2
Netmail Archive
5.2 N/A N/A Netmail Archive 5.2
GroupWise 8.0.0+
Netmail Archive 5.2
Netmail Archive
5.2 N/A N/A Netmail Archive 5.2
GroupWise 2012 RTM+
Netmail Archive 5.2
Netmail Archive
5.2 N/A N/A Netmail Archive 5.2
Exchange 2003 & 2007 RTM
M+Archive 2010.1
Netmail Archive
5.2 N/A N/A N/A
Exchange 2007 SP1+ Netmail Archive 5.2 Netmail Archive 5.2 N/A Netmail Archive 5.2 & Netmail Store
5.2
Netmail Archive 5.2
Exchange 2010+ Netmail Archive 5.2 Netmail Archive 5.2 Netmail Archive 5.2 Netmail Archive 5.2 & Netmail Store
5.2
Netmail Archive 5.2
Exchange 2013 Netmail Archive 5.2 SP1 Netmail Archive 5.2 SP1 Netmail Archive 5.2 SP1 Netmail Archive 5.2 SP1 & Netmail Store
5.2
N/A
Office 365 Netmail Archive 5.2 Netmail Archive 5.2 Netmail Archive 5.2 Netmail Archive 5.2 N/A
Note: The Netmail versions listed above are recommended for today's new or current deployments. Other deployment scenarios are also possible. Please contact Support for more information.
Supported Email Environments
Netmail Archive 5.2.x
Archiving RIF Archiving Email Retention
Email Retention without Journaling Migration Attachment Management GroupWise 6.5.1+ GroupWise 7.0.0+ GroupWise 8.0.0+ GroupWise 2012 RTM+ Exchange 2007 SP1+ Exchange 2010 RTM+ Exchange 2013* Office 365 E15* Exchange 2010 SP2 Office 365 E15* GroupWise 6.5.1+ GroupWise 7.0.0+ GroupWise 8.0.0+ GroupWise 2012 RTM+ Exchange 2007 SP1+ Exchange 2010 RTM+ Exchange 2013* Office 365 E15* Exchange 2010 RTM+ Exchange 2013* Office 365 E15* GroupWise 7.0.1+ GroupWise 8.0.0+ GroupWise 2012 RTM+ to any of the following: Exchange 2007 SP1+ Exchange 2010 RTM+ Exchange 2013 Office 365 E15* Exchange 2007 SP1 Update Rollup 8+ Exchange 2010 RTM+ Exchange 2013* Office 365 E15*
* Only as of Netmail Archive 5.2 SP1
Netmail Archive 5.1.x
Archiving Migration GroupWise 6.5.1+ GroupWise 7.0.0+ GroupWise 8.0.0+ GroupWise 2012 RTM+ Exchange 2007 SP1+ Exchange 2010 RTM+ GroupWise 7.0.1+ GroupWise 8.0.0+ GroupWise 2012 RTM+ to any of the following: Exchange 2007 SP1+ Exchange 2010 RTM+
M+Archive 2010.1.x
Archiving Migration GroupWise 6.5.1+ GroupWise 7.0.0+ GroupWise 8.0.0+ Exchange 2003 SP2 Exchange 2007 RTM+ Exchange 2010 RTM+ GroupWise 7.0.1+ GroupWise 8.0.0+ to any of the following: Exchange 2003 SP2 Exchange 2007 RTM+ Exchange 2010 RTM+
Note: While older versions of both M+Archive and Netmail Archive software are currently supported, please refer to the Product Lifecycle Calendar for engineering and support information.
Archive Server (Master or Worker Nodes)
The Archive Server is responsible for connecting to the back-end mail server (GroupWise or Exchange), ingesting data, converting it to XML and storing the data.
Server:
Processor: 4 total “cores” or “processors” (e.g., 1 quad-core CPU, 2 dual-core CPUs or 4 processors in a virtual environment)
Memory: 8 GB RAM Network: GB Ethernet
Hard Drive: Up to 5 different spaces can be set up for storage. Smaller organizations might choose to store everything together, while larger organizations may opt to for more granularity.
o Storage #1: 150 GB for OS, applications and swap space (up to 250 GB of space may be required depending on job size)
o Storage #2: Adequate local or attached storage for archived messages
Archives do not change once written, so they can be stored on read/write media or a WORM device.
Archives are stored in XML format and are typically around 4 kB in size, accounting for approximately 20% of the total archive size. Recommended block size of storage device should be 4 kB blocks.
o Storage #3: Adequate local or attached storage for archived attachments
Attachments do not change once written, so they can be stored on read/write media or a WORM device.
Attachments are stored in their native format, accounting for approximately 80% of the total archive size.
o Storage #4: Adequate local or attached storage for audit files
Audit files track all access to archive data and need to be updated, so they cannot be written to a WORM device.
Audit files are very small in size, typically around 1 kB. Recommended block size of storage device should be 2 kB blocks.
Size of audit files requires approximately 15% the amount of archived data (e.g., 1 TB of archives would mean 150 GB of audit files).
Operating System:
Windows Server 2008 R2 SP1 Standard Edition (64-bit), Windows 2008 SP2, or Windows Server 2012 Note: A 64-bit OS is required on the node where the SAN LUNs are attached or archives are stored. Software:
Internet Explorer 8+ or Firefox 6+
PowerShell 2.0+ (included with Windows Server 2008 R2 SP1) (Exchange deployments only) .NET Framework 4.0
Java 6.0 JRE 32-bit (also known as version 1.6)
Note: Java 7.0 (or 1.7) is supported as of Netmail Archive 5.2.3. Version 5.2.2, however, does NOT support Java 7.0.
Database for logging (PostgreSQL 9.1 installed by default) Novell Client 4.91+ (GroupWise installs on 32-bit OS) Novell Client 2 SP1+ (GroupWise installs on 64-bit OS)
GroupWise Client 6.5.6+ or 7.0.1+; 7.0.3+ for OAPI support (GroupWise email systems only)
Outlook Client 2003 SP3+, 2007 SP1+ or 2010 SP0+ 32-bit only (required only for exporting archives to PST format)
Other items to note:
A single IP address or teamed IP ports are required
The Archive and Exchange Servers must be part of trusted domains (Exchange email systems only) Netmail Store is required for Attachment Management features
For PowerShell virtual directory in IIS on CAS servers, enable basic authentication for HTTPS,
Kerberos for HTTP
PowerShell scripting enabled
Index Server
The Index Server is responsible for indexing or cataloging all archives so that the data can be searched by administrators or email users.
Server:
Processor: 8 total “cores” or “processors” (e.g., 1 octa-core CPU, 2 quad-core CPUs or 8 processors in a virtual environment)
Memory: 32 GB RAM Network: GB Ethernet
Hard Drive: Up to 2 different spaces can be set up for storage. Smaller organizations might choose to store everything together, while larger organizations may opt to separate storage for more
granularity.
o Storage #1: 100 GB for OS, applications, and swap space (150 GB recommended for systems with 64 GB RAM)
Fiber Channel (FC) connection to a SAN is recommended.
iSCSI connections are supported, but performance cannot be guaranteed. o Storage #3 option B: Adequate local storage for indexes
6+ 15,000 RPM SCSI or SAS (not Nearline SAS) hard drives in a RAID 5 configuration. Indexes need to be updated, so they cannot be written to a WORM device.
Size of indexes requires approximately 40% the amount of archived data (e.g., 1 TB of archives would mean 400 GB of indexes).
Operating System:
< 5000 users: Windows Server 2008 R2 SP0+ Standard Edition 64-bit (due to RAM being limited to 32 GB); Windows Server 2008 R2 SP0+ Enterprise Edition 64-bit recommended (Windows Server 2003 SP2, 2003 R2 SP2, 2008 SP1+ 64-bit also supported)
> 5000 users: Windows Server 2008 R2 SP0+ Enterprise Edition 64-bit (Windows Server 2008 SP1+ Enterprise Edition 64-bit also supported)
Virtualized Deployment Requirements: ESX 3.5 or greater
VMFS (RDM not required, but suggested for better performance) SAN attached to host via fiber channel
Disk Caching on disk array
Thin provisioning supported, thick is suggested Vmotion supported
Software:
Internet Explorer 8+ or Firefox 6+ .NET Framework 4.0
GroupWise Client Stubbing Access Requirements
GroupWise 8.02+
Email must be archived with SOAP API in order to be stubbed
Outlook Client Requirements for the Add-in for Archive Access
Windows XP, Vista, or Windows 7 (no server class machines) Internet Explorer 8+ or Firefox 6+
Outlook Client 2007 SP3+ or 2010 (Outlook 2003 does not support stubbing) Supported deployment methods: SeeInstall the Netmail Archive Outlook Add-In
Administrative and end-user access to archives in a GroupWise environment can be accomplished through either an ‘Archive’ button in GroupWise WebAccess or through our web-based Netmail Search portal.
Internet Explorer 8+ or Firefox 6+ GroupWise WebAccess 7+
Outlook Web Access / Outlook Web App / Netmail Search Requirements
Administrative and end-user access to archives in an Exchange environment can be accomplished through either an ‘Archive’ button in OWA or through our web-based Netmail Search portal.
Internet Explorer 8+ or Firefox 6+
Outlook Web Access 2003 or 2007, Outlook Web App 2010