Page tree
Skip to end of metadata
Go to start of metadata

Minimum Requirements for Netmail Archive 5.4

On this page you will find the minimum and recommended hardware requirements, as well as the relevant system and software requirements, for the Netmail Archive Server to operate at its expected performance level. 

Netmail Archive 5.4 is delivered as a VMware virtual appliance (compatible with ESXi 5.1, 5.2, and 5.5) as well as a Microsoft Hyper-V virtual appliance. You are responsible to provide licensing for third party software such as Exchange, Groupwise, Windows Server and VM Ware. This also applies to pre-installed software on the appliances.

 Recommended Netmail Deployments
 ArchivingEmail RetentionEmail Retention
without Journaling
Attachment
Management

Migration to Exchange 2010+, 2013
& Office 365

GroupWise 7.0.1+yesyesN/AN/Ayes
GroupWise 8.0.0+
yesyesN/AN/Ayes
GroupWise 2012+yesyesN/AN/Ayes
GroupWise 2014yesyesN/AN/Ayes
Exchange 2007 SP1+yesyesN/A

yes

yes
Exchange 2010+yesyesyesyesyes
Exchange 2013+yesyesyesyesN/A
Office 365yesyesyesyesN/A
 Supported Email Environments

Netmail Archive 5.4 x

ArchivingRIF ArchivingEmail RetentionEmail Retention
without Journaling
Migration

Attachment
Management

  • GroupWise 7.0.1+
  • GroupWise 8.0.0+
  • GroupWise 2012+
  • GroupWise 2014*
  • Exchange 2007 SP1+
  • Exchange 2010+
  • Exchange 2013+
  • Office 365
  • Exchange 2010 SP2+
  • Exchange 2013+
  • Office 365
  • GroupWise 7.0.1+
  • GroupWise 8.0.0+
  • GroupWise 2012+
  • GroupWise 2014+
  • Exchange 2007 SP1+
  • Exchange 2010+
  • Exchange 2013+
  • Office 365
  • Exchange 2010+
  • Exchange 2013+
  • Office 365
  • GroupWise 7.0.1+
  • GroupWise 8.0.0+
  • GroupWise 2012+
  • GroupWise 2014+

to any of the following:

  • Exchange 2010+
  • Exchange 2013+
  • Office 365
  • Exchange 2007 SP1 Update Rollup 8+
  • Exchange 2010+
  • Exchange 2013+
  • Office 365

 

 

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.

Hardware:

  • Processor: 4 total cores minimum
  • Memory: 8 GB RAM (4 GB for worker nodes)
  • Network: GB Ethernet
  • Storage: Up to 4 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.
    • Storage #1: Operating System
      • 250 GB for OS, applications, temp and swap space. VM is delivered with this volume, thin-provisioned.
    • Storage #2: Archives
      • Adequate local or attached storage for archived messages is required.
      • Messages are stored in XML format, accounting for approximately 20% of the total mailbox size.
      • Archives have a read/write profile of 5/95, an expected performance of 500 IOPS for both random read and write, with a recommend block size of 4K.
      • Archives do not change once written, so they can be stored on read/write media or a WORM device.
    • Storage #3: Attachments
      • Adequate local or attached storage for archived attachments is required.
      • Attachments are stored in their native format, accounting for approximately 80% of the total mailbox size.
      • Attachments do not change once written, so they can be stored on read/write media or a WORM device.
    • Storage #4: Audit Files
      • Adequate local or attached storage for audit files is required.
      • 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).
      • Audit files are very small in size. Recommended block size of storage device is 2K.
      • Audit files track all operation on archive data and need to be updated, so they cannot be written to a WORM device.

Operating System (pre-installed on VM):

  • Microsoft Windows Server 2012 R2 Standard

Software (pre-installed on VM):

  • Internet Explorer 11, Firefox 25
  • Microsoft Visual C++ Redistributables
  • PowerShell 2.0 and 4.0 (required for Exchange deployments only)
  • .NET Framework 3.5 and 4.5
  • Java JRE 8u45 32-bit

  • PostgreSQL 9.3 for logging (separate DB can be used)
  • GroupWise 2014 client for OAPI support (required for GroupWise deployments only)
  • Strawberry Perl 5.18.1.1
  • OpenOffice 3.4.1

Virtual Environment:

VMware

  • ESX 3.5 or greater
  • vSphere 5.1 or greater
  • Vmotion supported
  • VMFS (RDM not required, but suggested for better performance)           
  • Disk Caching on disk array

Hyper-V

  • Hyper-V Server 2008 R2 SP1 and higher (Hyper-V 2012 R2 recommended)
  • Disk Caching on disk array
End-user Access
GroupWise Client Stubbing Access Requirements:
  • GroupWise 8.0.1+
  • Email must be archived with SOAP API in order to be stubbed

GroupWise WebAccess Requirements: 

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+, Firefox 25+ or Chrome 32+
  • GroupWise WebAccess 7+

Outlook Client Add-in Requirements:

  • Windows XP, Vista, 7, 8 or 8.1 (no server class machines)
  • Internet Explorer 9+, Firefox 25+ or Chrome 32+
  • Outlook Client 2007 SP3+, 2010 SP1+ or 2013 (Outlook 2003 does not support stubbing)
  • For supported deployment methods see: Installing the Netmail Archive Outlook Add-In

Outlook Web Access / Outlook Web App Requirements:

Administrative and end-user access to archives in an Exchange environment can be accomplished through either a ‘Netmail’ button in OWA or through our web-based Netmail Search portal.

  • Internet Explorer 9+, Firefox 25+ or Chrome 32+
  • Outlook Web Access 2007, Outlook Web App 2010 or 2013