System Requirements

To run StorNext, the Metadata Controller must meet all operating system, hardware, and LAN requirements.

Note: The performance of the storage holding the Storage Manager database and metadata archives has an impact on overall StorNext file system performance. Quantum recommends that the Storage Manager database and metadata archives are stored on high performance storage devices, such as a RAID array. Storing the Storage Manager database on slower storage devices, including local disks, can result in poor performance or time-outs.

Note: The UIDs for the quantumdb and tdlm users and the adic group must be identical on both nodes of an HA pair. If the UIDs are not identical, the MySQL database will not start (due to file permission errors), which in turn prevents storage manager from fully starting up. Quantum recommends creating the UIDs for the quantumdb and tdlm users along with the adic group on both nodes prior to running install.stornext.

The operating systems, kernel versions, rpm package dependencies, and hardware platforms supported by StorNext File System are listed in the StorNext Compatibility Guide.

Make sure the system meets the operating system and platform requirements outlined in the guide, and, if necessary, update to a supported release or kernel version before installing StorNext.

Note: For Linux clients, you must be disable C-States through kernel boot parameters. See Modify the grub.conf File to Disable the Intel Sleep State.

Newer versions of Linux include a driver that controls CPU C-states. It is strongly recommended that this driver be adjusted so that deep sleep states are disabled. Making this change may result in increased power consumption but improves stability and performance. This change should be applied to systems running RHEL 6.x and newer, SLES11 and newer, and all supported versions of Debian and Ubuntu:

  1. Prior to installation, append the following text to the kernel line in the boot loader configuration file:

    intel_idle.max_cstate=0 processor.max_cstate=1

    Note: Consult your distribution's documentation on how to modify the kernel boot loader.

    • For RHEL 6.x and Debian systems, update:

      /boot/grub/grub.conf

    • For RHEL 7.x systems, update:

      /boot/grub2/grub.cfg
    • For SLES systems use /sbin/yast to change the boot loader options under System > Boot Loader. Save the configuration and verify that /boot/grub/menu.lst was updated.

    • For Debian and Ubuntu systems update the GRUB_CMDLINE_LINUX_DEFAULT string in /etc/default/grub to include the above text, and then execute update-grub. Verify that the /boot/grub/grub.cfg file was updated.

  2. Reboot the system for the change to take effect.

Note: Disabling C-States in the system BIOS has no effect on Linux.

In some cases, performance can also be improved by adjusting the idle kernel parameter. However, care should be taken when using certain values. For example, idle=poll maximizes performance but is incompatible with hyperthreading (HT) and will lead to very high power consumption. For additional information, refer to the documentation for your version of Linux.

Installation and upgrade media is shipped on DVDs. Both software and documentation are now stored on a single DVD, eliminating multiple discs for different operating systems. If you plan to install from media, you must have a DVD ROM drive to perform the installation or upgrade.

Refer to the following procedures:

  1. Install the StorNext Client Software on Linux
  2. Install the StorNext Client Software on Windows

Another way to obtain a StorNext media kit is by downloading the software. This process consists of obtaining a download authorization certificate, creating a download account (or signing on if you already have an account), downloading a software ISO image onto DVD, and then installing the software as described in the following procedures.

Refer to the following procedures:

If you have problems or questions with this process, contact your Quantum StorNext support representative.

A third StorNext delivery method is downloading from the Web. With this method you will download an executable program that will require you to accept the StorNext end user license agreement and will then extract the StorNext installer.

As part of the installation from a Web download, the software files are extracted into the /tmp/stornext directory by default. The software, when extracted, requires approximately 400 MB of space. Make sure there is enough free space in the default directory to extract the files. If there is not sufficient space, you may need to specify an alternative directory with the -d option.

To specify an alternate location before beginning the installation, enter the following command:

# ./<installation file> -d <dir>

where <installation file> is the name of the installation file, and <dir> is the directory into which you want to extract the installation files.

Refer to the following procedures:

RAM and hard disk space requirements to run the StorNext File System are listed in the StorNext Compatibility Guide.

Make sure the MDC meets the hardware requirements outlined in the guide, and, if necessary, update the MDC before installing StorNext.

For improved performance and stability, it is strongly recommended that CPU C-States be disabled in the BIOS if they are supported by your system. Refer to system vendor documentation for additional information.

Note: Gateway servers may require additional RAM depending on the number of file systems, LAN clients, and NICs used. See Gateway Server/Client Network and Memory Tuning for Gateway server/client memory tuning guidelines.

StorNext can be installed on any local file system (including the root file system) on the MDC. However, for optimal performance, as well as to aid disaster recovery, follow these recommendations:

  • Avoid installing StorNext on the root file system.

  • Partition local hard disks so that the MDC has four available local file systems (other than the root file system) located on four separate hard drives. This is so you can install the support directories in four separate locations (for more information, see Run the Pre-Installation Script).

    Note: You can run the pre-installation script to help determine the estimated size of and optimal location for StorNext support directories. For more information, see Run the Pre-Installation Script.

StorNext LAN requirements are listed in the StorNext Client RAM, Disk and CPU Requirements section of the StorNext Compatibility Guide. For additional information, see Special Considerations for StorNext LAN Clients.

Note: Make sure the MDC meets the network requirements outlined in the guide, and, if necessary, update the MDC before installing StorNext.

Additional requirements that must be met for the StorNext system are listed in the StorNext Compatibility Guide.

Note: Make sure the system meets the additional requirements outlined in the guide, and, if necessary, update the system before installing StorNext.

Quantum recommends that system clocks are synchronized using NTP for easier debugging. For HA installations, the system clocks must be synchronized for proper operation.

The default UID/GID values for the Nobody user differ across platforms. Please ensure that your environment is set up with a common value for the Nobody user and group to ensure proper file access. Also note the default values for Nobody when files are generate by Windows clients, as defined in each file system's configuration.

If you are using the StorNext client software with Windows Server 2003, Windows Server 2008, Windows XP, Windows Vista, Windows 7, or Windows 10 disable the Recycle Bin in the StorNext file systems mapped on the Windows machine.

You must disable the Recycle Bin for the drive on which a StorNext file system is mounted. Also, each occurrence of file system remapping (unmounting/mounting) will require disabling the Recycle Bin. For example, if you mount a file system on E: (and disable the Recycle Bin for that drive) and then remap the file system to F:, you must then disable the Recycle Bin on the F: drive.

StorNext supports mounting file systems to a directory. For Windows Server 2003 and Windows XP you must disable the Recycle Bin for the root drive letter of the directory-mounted file system. For example: for C:\MOUNT\File_System you would disable the Recycle Bin for the C: drive.

  1. On the Windows client machine, right-click the Recycle Bin icon on the desktop and then click Properties.
  2. Click Global.
  3. Click Configure drives independently.
  4. Click the Local Disk tab that corresponds to the mapped or directory-mounted file system.
  5. Click the checkbox Do not move files to the Recycle Bin. Remove files immediately when deleted.
  6. Click Apply, and then click OK.
Windows Vista and Windows 7 Systems

You must disable the Recycle Bin on C: and the File system name.

  1. On the Windows client machine, right-click the Recycle Bin icon on the desktop and then click Properties.
  2. Click the General tab.
  3. Select the mapped drive that corresponds to the StorNext mapped file system. For directory-mounted file systems, select the file system from the list.
  4. Choose the option Do not move files to the Recycle Bin. Remove files immediately when deleted.
  5. Click Apply.
  6. Repeat Step 3 through Step 5 for each remaining directory-mounted file system.

  7. When finished, click OK.