Help Center


Knowledge Base


[Netmail Documentation]

This documentation is for Netmail 5.4. Documentation for [Netmail Archive 5.3] and [earlier versions of Netmail] is also available.

Skip to end of metadata
Go to start of metadata

Requirements and Recommendations for Netmail Store 5.4.x

This page provides a selection of hardware shown to be adequate for the Netmail Store part of the platform to operate up to its expected performance level.

Before installing Netmail Store, it is advisable that your hardware complies with the following requirements and recommendations.

Minimum Requirements for Netmail Store

Netmail Store installs and runs on enterprise-class x86 commodity hardware. At least three Netmail Store nodes are required in a cluster to ensure adequate resiliency to failures.

Netmail Store nodes are designed to run using lights-out management (or out-of-band management) and do not require a keyboard, monitor, and mouse (KVM) to operate.

The following table lists the minimum (and recommended) hardware requirements for a Netmail Store cluster.

Hardware:

  • Node: x86 with Pentium-class CPUs; x86 with Intel Xeon or AMD Athlon64 (or equivalent) CPUs recommended
  • Number of nodes: 3+ (to ensure adequate recovery targets in the event of a failure)
  • Switch: Nodes must connect to switches configured compatible with L2 multicasting (IGMP snooping must be turned off)
  • Log server: Recommended for accepting tracing from the nodes (included in the CSN server, below)
  • Node boot capability: USB flash drive or network drive
  • Network interfaces: Minimum 100Mbps Ethernet NIC with one RJ-45 port, recommended 1Gbps or more
  • Hard Drives: One hard drive minimum; more recommended (RAID configuration not supported)
  • Memory: 2 GB RAM minimum; 4 GB recommended
  • NTP server: Required to synchronizing clocks across nodes (included in the CSN server, below)

Notes:

  • All nodes in a cluster must use the same speed network interface to remain compatible. Variable network speeds for different nodes are not a supported configuration. For example, a node with a 100Mbps network interface card must not be in the same cluster with a node that has a 1Gbps card.
  • Although Netmail Store runs on a variety of x86 hardware, the figures above list the recommended base characteristics for a Netmail Store cluster.

  • Netmail Store cluster performance improves exponentially by adding additional systems with more intensive CPU hardware and additional memory. The number of recommended systems varies depending on your storage and performance requirements.

h

 Expand for more detailed information about hardware requirements

Memory Sizing Requirements

Review the following sections for factors that will influence how you size memory and erasure coding, as well as how you configure Netmail Store.

How RAM Affects Storage

The storage cluster is capable of holding the sum of the maximum object counts from all nodes in the cluster. The number of individual objects that can be stored on a Netmail Store node depends both on its drive capacity and the amount of its system RAM.

The following table shows estimates of the maximum possible number of replicated objects (regardless of size) that you can store on a node, based on the amount of RAM in the node, with the default 2 replicas being store. Each replica takes one slot in the in-memory index maintained on the node.

Amount of RAMMaximum number of immutable unnamed streamsMaximum number of unnamed streams or named streams
4BG33 million16 million
8GB66 million33 million
12GB132 million66 million

How the Overlay Index Affects RAM

Larger clusters (those above 32 nodes by default) need additional RAM resources to take advantage of the Overlay Index.

To store the same number of reps=2 object counts above and utilize the Overlay Index, increase RAM as follows:

  • Immutable unnamed objects: 50% additional RAM
  • Aliased or named objects: 25% additional RAM

Smaller clusters and larger clusters where the Overlay Index is disabled do not need this additional RAM.

How Erasure Coding Affects RAM

The number of erasure-coded objects that can be stored on a node per GB of RAM is dependent on the size of the object and the configured encoding. The erasure-coding manifest takes two index slots per object, regardless of the type of object (named, unnamed immutable, or unnamed anchor). Each erasure-coded segment in an erasure set takes one index slot. Larger objects can have multiple erasure sets, so you would have multiple sets of segments.

In k:p encoding (integers for the data (k) and parity (p) segment counts), there are p+1 manifests (up to the ec.maxManifests maximum). For 5:2 encoding, that would mean 3 manifests.

For example, with the default segment size of 200 MB and a configured encoding of 5:2,

  • 1-GB object: (5+2) slots for segments and (2+1) for manifests = 10 index slots
  • 3-GB object: 3 sets of segments @ 10 slots each = 30 index slots

Additional RAM: Larger clusters (above 32 nodes by default) need additional RAM resources to take advantage of the Overlay Index. For erasure-coded objects, allocate 10% additional RAM to enable the Overlay Index.

In summary, Erasure coding users about half the space of replication, but it requires more RAM.

How to Configure for Small Objects

Netmail Store allows you to store objects up to a maximum of 4 TB. However, if you store mostly small files, configure your storage cluster accordingly.

By default, Netmail Store allocates a small amount of disk space to store, write, and delete the disk's file change logs (journals). In typical deployments, this default amount is plenty because the remainder of the disk will be filled by objects before the log space is consumed.

However, for installations writing mostly small objects (1 MB and under), the file log space can fill up before the disk space. If your cluster usage focuses on small objects, be sure to increase the configurable amount of log space allocated on the disk before you boot Netmail Store on the node for the first time.

The parameters used to change this allocation differ depending on the software version in use.

By default, Netmail Store is configured to allocate a small amount of disk space to store write and delete journals.

Supporting High-Performance Clusters

For the demands of high-performance clusters, Netmail Store benefits from fast CPUs and processor technologies, such as large caches, 64-bit computing, and fast Front Side Bus (FSB) architectures.

To design a storage cluster for peak performance, maximize these variables:

  • Add nodes to increase cluster throughput – like adding lanes to a highway
  • Fast or 64-bit CPU with large L1 and L2 caches

Important: If the cluster node CPU supports hyper-threading, be sure to disable this feature within the BIOS setup to prevent single-CPU degradation in Netmail Store.

  • Fast RAM BUS (front-side BUS) configuration
  • Multiple, independent, fast disk channels, such as:
    • Hard disks with large, on-board buffer caches and Native Command Queuing (NCQ) capability
    • Gigabit (or faster) network topology between all Netmail Store cluster nodes
    • Gigabit (or faster) network topology between the client nodes and the Netmail Store cluster

Balancing Resources

For best performance, try to balance resources across your nodes as evenly as possible. For example, in a cluster of nodes with 7 GB of RAM, adding several new nodes with 70 GB of RAM could overwhelm those nodes and have a negative impact on the cluster.

Because Netmail Store is highly scalable, creating a large cluster and spreading the user request load across multiple storage nodes significantly improves data throughput, and this improvement increases as you add nodes to the cluster.

Tip: Using multiple replicas when storing objects in the cluster is an excellent way to get the most out of Netmail Store, because each copy provides redundancy and improves performance.

Selecting Hard Drives

Selecting appropriate hard drives for the Netmail Store nodes improves both performance and recovery, in the event of a node or disk failure. When selecting drives, these are the key criteria, which are detailed below:

  • Drive type: enterprise-level drives rated for continuous, 24x7 duty cycles and having time-constrained error recovery logic
  • Drive performance: buffer cache size and bus type/speed
  • Drive capacity: trade off of high capacity versus recovery time
  • Disk controller compatibility: matching what you have in your existing nodes

Drive Type

The critical factor is whether the hard drive is designed for the demands of a cluster. Enterprise-level hard drives are rated for 24x7 continuous-duty cycles and have time-constrained error recovery logic that is suitable for server deployments where error recovery is handled at a higher level than its on-board controller.

In contrast, consumer-level hard drives are rated for desktop use only; they have limited-duty cycles and incorporate error recovery logic that can pause all I/O operations for minutes at a time. These extended error recovery periods and non-continuous duty cycles are not suitable or supported for Netmail Store deployments.

Reliability

The reliability of hard drives from the same manufacturer will vary, because the drive models target different intended use and duty cycles:

  • Consumer models targeted for the home user typically assume that the drive will not be used continuously. As a result, these drives do not include the more advanced vibration and misalignment detection and handling features.
  • Enterprise models targeted for server applications tend to be rated for continuous use (24x7) and include predictable error recovery times, as well as more sophisticated vibration compensation and misalignment detection.

Drive Performance

You can optimize the performance and data throughput of the storage sub-system in a node by selecting drives with these characteristics:

  • Large buffer cache — Larger, on-board caches improve disk performance
  • Independent disk controller channels — Reduces storage bus contention
  • High disk RPM — Faster-spinning disks improve performance
  • Fast storage bus speed — Faster data transfer rates between storage components, a feature incorporated in these types:
    • SATA-300
    • Serial Attached SCSI (SAS)
    • Fibre Channel hard drives

Use of independent disk controllers is often driven by the storage bus type in the computer system and hard drives.

  • PATA — Older ATA-100 and ATA-133 (or Parallel Advanced Technology Attachment [PATA]) storage buses allow two devices on the same controller/cable. As a result, bus contention occurs when both devices are in active use. Motherboards with PATA buses typically only have two controllers. If more than two drives are used, some bus sharing must occur.

  • SATA — Unlike PATA controllers, Serial ATA (SATA) controllers and disks include only one device on each bus to overcome the previous bus contention problems. Motherboards with SATA controllers typically have four or more controllers. Recent improvements in Serial ATA controllers and hard drives (commonly called SATA-300) have doubled the bus speed of the original SATA devices.

Drive Capacity and Recovery

You can improve the failure and recovery characteristics of a node when a drive fails by selecting drives with server-class features yet that are not the highest capacity.

  • Higher capacity means slower replication. When choosing the drive capacity in a node, consider the trade-off between the benefits of high-capacity drives versus the time required to replicate the contents of a failed drive. Larger drives take longer to replicate than smaller ones, and that delay increases the business exposure when a drive fails.
  • Delayed errors mean erroneous recovery. Unlike consumer-oriented devices, for which it is acceptable for a drive to spend several minutes attempting to retry and recover from a read/write failure, redundant storage designs such as Netmail Store need the device to emit an error quickly so the operating system can initiate recovery. If the drive in a node requires a long delay before returning an error, the entire node may appear to be down, causing the cluster to initiate recovery actions for all drives in the node — not just the failed drive.
  • Short command timeouts mean less impact. The short command timeout value inherent in most enterprise-class drives allows recovery efforts to occur while other system drives continue to support system drive access requests by Netmail Store.

Drive Controller Compatibility

The best practice is to check with Netmail before investing in new equipment, both for initial deployment and for future expansion of your cluster. Netmail can help you avoid problems not only with drive controller options but also with network card choices.

  • Evaluate controller compatibility before each purchasing decision.
  • Buy controller-compatible hardware. As a rule, the more types of controllers in a cluster, the more restrictions you face on how volumes can be moved. Study these restrictions, and keep this information with your hardware inventory.
  • Avoid RAID controllers. RAID controllers are problematic, for two reasons:
    • Incompatibilities in RAID volume formatting
    • Inability of many to hot plug

Mixing Hardware

Netmail Store greatly simplifies hardware maintenance by making drives independent of their chassis and their drive slots. As long as your drive controllers are compatible, you are free to move drives as you need.

Netmail Store supports a variety of hardware, and clusters can blend hardware as older equipment fails or is decommissioned and replaced. The largest issue with mixing hardware is incompatibility among the drive controllers.

Track types of drive controllers

When you administer the cluster, monitor your hardware inventory with special attention to the drive controllers. Some RAID controllers, for example, reserve part of the drive for controller-specific information (DDF). Once a volume is formatted for use by Netmail Store, it must be used with a chassis having that specific controller and controller configuration.

To save time and data movement, many maintenance tasks involve physically relocating volumes between chassis. Use the inventory of your drive controller types to easily spot when movement of formatted volumes is prohibited due to drive controller incompatibility.

Disable volume autoformatting

For additional safety in a cluster with incompatible controllers, set this option:

disk.automaticFormat=False

This configuration setting prevents volume reformatting if you accidentally move a volume between incompatible controllers.

With automatic drive formatting disabled, you will need to format your new volumes outside the cluster, which you can do using a spare chassis running Netmail Store with the desired controller.

Test compatibility outside cluster

To determine controller compatibility safely, test outside of your production cluster, do the following:

1. Set up two spare chassis, each with the controller being compared.

2. In the first chassis, format a new volume in Netmail Store.

3. Move the volume to the second chassis and watch the log for error messages during mount or for any attempt to reformat the volume.

4. Retire the volume in the second chassis and move it back to the first.

5. Again, watch for errors or attempts to reformat the volume.

6. If all goes well, erase the drive using dd and repeat the procedure in reverse, where the volume is formatted on the second chassis.

If no problems occur during this test, you can confidently swap volumes between these chassis within your cluster. If this test runs into trouble, do not swap volumes between these controllers.

Minimum requirements for the CSN

Hardware:

  • Node: x86 with 64-bit Intel® Xeon® or AMD® Opteron™ (or equivalent) CPUs
  • Memory: 6GB RAM minimum; 12GB recommended
  • Supported Operating systems:
    • Red Hat® Enterprise Linux® (RHEL) 6.2 Server 64-bit (English version)
    • CentOS 6.2 64-bit Server Edition (English version)
  • Disk Storage:
    • Content Router requires 200 GB of disk space for every 100 million unique objects in the associated Netmail Store cluster

    • The data and graphs for the Netmail Store graphical reports require approximately 6MB of space in /var per Netmail Store node

    • RAID configuration for redundancy is recommended

    • A separate partition with at least 16GB of available space configured for /var/log to prevent logging from over-running other critical processes in /var

  • Network: Two Gigabit Ethernet NICs required; Four Gigabit Ethernet NICs recommended
    • A single network configuration requires a dedicated subnet that the CSN can control to allocate storage node IP addresses

    • A dual-network configuration requires:

      • Dedicated switch or VLAN for the internal storage network
      • Managed switch (recommended)
      • Disabled switch spanning tree when using a secondary CSN

 

 Expand for more detailed information about hardware requirements

Operating System

The Netmail Store CSN has been developed and tested with the U.S. English versions of RHEL 6.2 Server 64-bit and CentOS 6.2 64-bit Server Edition. Other versions/languages or Linux distributions are not currently supported. Subsequent installation instructions will assume a pre-installed RHEL Linux environment with either internet connectivity or an alternately configured yum repository for use in installing required third party packages. The CSN installation process is dependent on additional rpm packages that are not installed on the system by default. These packages are available on the RHEL distribution media included with the system.

Important: To ensure a package upgrade does not impact CSN networking, yum updates are disabled after installation by locking all software packages to the version installed during initial configuration. Please contact your support resource if you need to enable yum updates for security updates.

Networking

The CSN provides two options for network configuration:

  • Dual-network. This option was available in prior CSN releases and can continue to be used with no network reconfiguration or interface recabling in later releases. It should be used if the Netmail Store cluster should be isolated on a dedicated network so that the external network is isolated from both the PXE network boot server (including DHCP) and cluster multicast traffic. The CSN itself with a dual-network configuration is 'dual-homed' with half its network interfaces cabled to the external network and the other half cabled to the internal network. The storage nodes the CSN manages are cabled to the internal network only. This internal private network ensures the Netmail Store cluster traffic is protected from unauthorized access. In this network configuration, the CSN owns network interface detection and configuration and assumes there will not be any external manipulation of networking files or services. This configuration is ideal for both installations without a lot of networking expertise and those where cluster isolation is desirable.
  • Single-network. This option is new and should be used if the Netmail Store nodes need to be directly addressable on the same network as the CSN without requiring the SCSP Proxy to proxy requests. Both the CSN and the storage nodes it manages are cabled to the same network with single-network. In single network configurations, the CSN assumes a network administrator familiar with the environment in which the CSN runs will configure and maintain the CSN's network interfaces as well as basic network configuration, like configuring a static IP identity for the CSN. A single-network configuration is ideal for installations that have some networking expertise and want the CSN and Netmail Store nodes' IP addresses to reside in a larger subnet range.

Both network options allow definition of what servers the CSN will network boot as Netmail Store nodes. Single-network enables netboot protection by default to prevent accidental format of servers not intended as storage nodes on a larger network. Dual-network does not require netboot protection by default but it can be enabled. Please reference “Adding Netmail Store Nodes” for more information on netboot protection.

The CSN does not support migration from one type of network configuration to another without reinstalling the CSN.

The following table summarizes the pros and cons of each networking option:

FeatureSingle-NetworkDual-Network

Isolate cluster multicast traffic on a separate internal network, using SCSP Proxy to proxy requests to and from the external network

 X

Allow storage nodes to be directly addressable on a larger network without a proxy

X 

Requires a dedicated switch or VLAN for internal storage network

 X

Requires a dedicated subnet that the CSN can control for allocation of storage node IP Addresses

X 

Automate detection and configuration of network interfaces and bonding

 X

Allow manual configuration of CSN networking and bonding by an experienced Linux administrator

X 

Enable netboot protection to only allow network boot of Netmail Store nodes for explicitly defined servers

X (by default)

X (after enabling in the CSN console)

The following sections discuss additional details about each type of configuration to aid you in deciding which is more appropriate for your environment.

Dual-network

A dual-network CSN requires access to both the external network as well as a dedicated internal network. Allocation of the address space in the internal network is broken down as follows, depending on the network size selected during initial configuration (small or large):

Network SizeCSNExternal ApplicationsDHCPNetmail Store Netboot
small (/24)x.y.0.0-16x.y.z.17-32x.y.z.33-83x.y.255.254
large (/16)x.y.0.0-254x.y.1.0-254x.y.2.0-254x.y.3.0-x.y.255.254

The CSN range provides IP Addresses for the various services on the Primary and Secondary CSNs.

The third-party range is provided for third party applications that need to run on the internal network to interface with the Netmail Store cluster. All IP addresses in the third-party range must be static. If you are using CFS with Netmail Store, the IP Address should be assigned in the third-party range. Best practice is to keep a list of all IP Addresses that have been allocated to different applications in the third-party range to prevent IP collisions.

The DHCP range provides an initial, temporary IP Address to Netmail Store nodes during their initial boot until permanent addresses can be assigned to each Netmail Store process by the CSN. Other applications that used the CSN's DHCP server on the internal network would reduce the number of Netmail Store nodes that could be booted at the same time, which is why a separate third-party range has been provided. For a small network, the maximum number of Netmail Store nodes that can be booted at one time is 50, assuming those nodes support a maximum of 3 multi-server processes per node. Netmail Store nodes that support higher multi-server process counts require additional IP Addresses in the Netboot range, decreasing the number of nodes that can be simultaneously booted. In a large network, the maximum number of Netmail Store nodes that can be booted at one time is 254.

The Netboot range is used to provide the IP Addresses seen in the Admin Console for all Netmail Store processes.

Cabling Dual-network Interfaces

A dual-network CSN requires at least one network interface each for the Internal and External networks. Additional available NICs would ideally be split between the two networks, alternating each NIC port's cabled connection across all network cards for redundancy (External, Internal, External, Internal, etc). The CSN's initial configuration script will detect how all NICs are cabled based on whether or not the specified external gateway is reachable from each NIC. The configuration script will print what it detects to allow you to verify correct cabling; see “Dual-network Primary Configuration” for complete details. Once confirmed during initial configuration, the CSN will bond all NICs assigned to each interface into a single bonded interface with balance-alb bonding.

Single-network

A single network CSN requires access to a dedicated subnet within an overall larger network. The subnet must be at least a Class C range with 256 IP addresses and may be as large as a full Class B network. The CSN itself must be configured with a static IP Address, subnet mask and gateway prior to CSN installation. The CSN's IP Address should be within the x.x.x.1 - x.x.x.17 range for the configured subnet. The gateway configured for a single-network CSN will also be used for the Netmail Store nodes when they are configured.

Please reference the RHEL/CentOS documentation for complete instructions on configuring networking. As an example, the following demonstrates what the manually configured em3 interface with a static 172.20.20.11 IP Address, 255.255.255.0 subnet mask and 172.20.20.1 gateway would look like in /etc/sysconfig/network-scripts/ifcfg-em3:

# CSN interface
DEVICE=em3
IPADDR=172.20.20.11
NETMASK=255.255.255.0
GATEWAY=172.20.20.1
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
MTU=1500
NM_CONTROLLED=no

Be sure to restart the network after configuring the IP Address (/etc/init.d/network restart).

Similar to a dual-network configuration, a single-network CSN will divide up the allocated address space into ranges for the CSN, DHCP and Netboot. The allocated ranges will vary depending on the size of the dedicated subnet and will be printed for confirmation during single-network installation. Since a single-network CSN is directly addressable by external clients, there are no IP Addresses reserved for a third-party range in the CSN's subnet.

Cabling Single-network Interfaces

All network interfaces on a single network CSN should be cabled to the same broadcast domain (VLAN) on one or more network switches. A minimum of two cabled network interfaces is still recommended for redundancy. In addition to configuring the CSN's static IP address, any desired bonding configuration (for either redundancy or throughput) should be completed by the administrator prior to starting single-network CSN installation. Please reference the RHEL/CentOS documentation for complete instructions on configuring network bonding.

Pre-Installation Checklist

Before you install CSN, confirm all of the following:

  • You have a valid IP addresses for your DNS and NTP servers.
  • For dual-network configurations: You must have two available external IP addresses: one to access the Primary CSN and another to access the CSN "cluster" (that is, the Primary CSN (required) and Secondary CSN (optional)). If you set up a Primary and Secondary CSN, you access the CSN console using the CSN cluster IP address in the event the Primary CSN is not available. For more information, see Primary vs. Secondary.

   Before you continue, make sure these IP addresses are not already in use.

  • For single-network configurations: You must have statically configured the IP address for the CSN as described in previous sections.
  • All network interface adapters are connected properly. At least one network interface must be enabled during RHEL/CentOS installation so that it is available for use during CSN installation.
  • No labels