System Requirements for Netmail Archive

Transcription

1 System Requirements for Minimum Requirements for.x Updated March 19, 2014 This document stipulates the minimum and recommended hardware requirements as well as the relevant system and software requirements for the 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 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.

2 Recommended Netmail Deployments GroupWise & GroupWise GroupWise GroupWise GroupWise 2012 Exchange 2003 & 2007 RTM Exchange 2007 SP1+ Exchange Exchange 2013 Office 365 Archiving M+Archive SP1 Retention SP1 Retention without Journaling Attachment Management Migration to Exchange & Office 365 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A SP1 & Netmail Store & Netmail Store SP1 & Netmail Store N/A 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.

3 Supported Environments.x Archiving RIF Archiving Retention SP * 2010 SP2 * Only as of SP SP * Retention without Journaling * Migration to any of the following: 2007 SP Attachment Management 2007 SP1 Update Rollup * 5.1.x Archiving SP Migration to any of the following: 2007 SP

4 M+Archive x Archiving SP Migration to any of the following: 2003 SP Note: While older versions of both M+Archive and 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).

5 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: 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.3. Version.2, however, does NOT support Java 7.0. Database for logging (PostgreSQL 9.1 installed by default) Novell Client (GroupWise installs on 32-bit OS) Novell Client 2 SP1+ (GroupWise installs on 64-bit OS) Client or ; for OAPI support (GroupWise 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 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 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) o Storage #2 option A: Adequate attached storage for indexes

6 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:.NET Framework 4.0 GroupWise Client Stubbing Access Requirements 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) Outlook Client 2007 SP3+ or 2010 (Outlook 2003 does not support stubbing) Supported deployment methods: See Install the Outlook Add-In GroupWise WebAccess / WebViewer / Netmail Search Requirements

7 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. 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. Outlook Web Access 2003 or 2007, Outlook Web App 2010