Loading...

Prerequisites for Manually Setting Up the ScaleOut Storage Pool

Ensure that the server on which you plan to manually install the MediaAgent and the ScaleOut Storage Pool adheres to the following:

  • System Requirements with the required RPM dependencies:
    Linux Red Hat Enterprise Linux/CentOS Processors RPM Dependencies
      CentOS 7.2 with glibc 2.17.x x64 or compatible processors

    userspace-rcu
    psmisc

      Red Hat Enterprise Linux 7.2 with glibc 2.17.x x64 or compatible processors

    python-argparse
    userspace-rcu
    psmisc

      Red Hat Enterprise Linux 6.6 with a minimum of glibc 2.12-1.25.x x64 or compatible processors

    pyxattr
    python-argparse
    userspace-rcu
    python-gluster
    libuuid-devel
    urwid

     

      Red Hat Enterprise Linux 6.8 with a minimum of glibc 2.12-1.25.x x64 or compatible processors

    pyxattr
    python-argparse
    userspace-rcu
    python-gluster
    libuuid-devel
    urwid

     

      Red Hat Gluster Storage 3.x  x64 or compatible processors

    urwid

     

  • To achieve disk level redundancy and for better performance, we recommend to have “Non-RAID” on spindle disks for storage. However, if there is already a hardware RAID card in the server, you must bypass the RAID card and configure them as independent physical disks.
  • Ensure that 10 GigE network card must be used for ScaleOut Storage Pool communication.
  • For creating or scaling out the ScaleOut Storage Pool, we recommend to use the same size disk.
  • Disable the firewall service.
  • Ensure that the underscore "_" special character is not used in any MediaAgent or ScaleOut Storage Pool name.
  • Each MediaAgent node must have two NIC cards.
    • One NIC card is used for SnapProtect's communication and the IP address associated with the NIC card must resolve to the host name used for SnapProtect communication.
    • The other NIC card is used for storage pool communication and the IP address associated with the NIC card must resolve to the host name used for SnapProtect communication with sds suffix. Also, the host name used for the storage pool communication must resolve to the loopback IP (127.0.0.1) locally.

    For example: If the IP address associated with NIC used for  SnapProtect  communication resolves to hostname scaleout1, the IP address associated with NIC used for storage pool communication will resolve to scaleout1sds.

    In your setup, you have three MediaAgents with hostnames scaleout1, scaleout2 and scaleout3.

    After successfully adding the loopback IP, scaleout1 should resolve to loopback IP address 127.0.0.1 locally with sds as the host name suffix.

    Important: If you are adding additional MediaAgent nodes to an existing ScaleOut Storage Pool blocks, then ensure that the newly added MediaAgent node's host name and the hostname with sds suffix should resolve with the existing MediaAgent notes.

    The images below are examples for three MediaAgent nodes:

    Scaleout1

    Scaleout2

    Scaleout3

  • Format the disk / logical volume to be used for deduplication database (DDB) with XFS File System. Mount the disk or the logical volume under /ws/ddb directory.

    Tip: For better performance, use the solid state drive (ssd) for ddb. For more information about the hardware specifications see, Hardware Specifications for Deduplication Partitioned Mode.

  • You must format and mount the disk on the MediaAgent node by running the following command from the command prompt on each MediaAgent node:
    1. Log in to the MediaAgent computer and on the command prompt navigate to the following directory:

      /opt/commvault/Base

    2. Run the following:

      ./CVSDS -d

    3. The command will detect the newly added disk, which is not already a part of the ScaleOut Storage Pool blocks and will display the following information together with the newly added disk:

      Detected unused disk devices which can be initialized to become part of StoragePool. All the existing data on the disk device will be destroyed during initialization. Please select which of the following disk device should be initialized.

    4. Select OK to format and mount the disk on the MediaAgent node.

    What to do Next

    After you have arranged for the prerequisites, see Manual Configuration Method to setup an existing Linux server with the Storage Pool feature.