Chat now with support
Chat with Support

QoreStor 7.4.0 - Installation Guide

Installing QoreStor

Before installing QoreStor, refer to System requirements and Installing QoreStor for additional information. To install QoreStor in Object Direct mode, refer to Installing QoreStor in Object Direct mode.

To install QoreStor

  1. Copy the QoreStor installation files to the server.
  2. Set execution permission on the installation files using chmod. For example,

    $ chmod a+x qs_inst_7.4.0.222.bin

  3. With elevated privileges (either as root or with the sudo command), run the installation script according to one of the two options below
    • qs_inst_7.4.0.222.bin -- -f –p <repository_path> -m <metadata_path> --mode=<cloud-optimized|standard|large> --accept-eula --install-deps [--install-vtl]

      where the following parameter definitions are true:

    • -f specifies that the installer should automatically apply firewall rules to open the necessary ports
    • -p <repository_path> specifies the repository path
    • -m <metadata_path> specifies where the dictionary and journals should be stored.If not specified, the repository path will be used.
    • --mode=<cloud-optimized|standard|enterprise|enterprise-plus> specifies the installation mode. Refer to QoreStor installation modes for more information.
      • cloud-optimized: 43TB max storage, 64 GB dictionary
      • standard: 150 TB max. storage, 256 GB dictionary
      • enterprise: 360 TB max storage, 256 GB dictionary
      • enterprise plus : 512TB max storage, 384GB dictionary, 64GB cloud-tier dictionary
    • --accept-eula: implicitly accepts the EULA and bypasses the prompt to accept the terms and conditions of the EULA
    • --install-deps: implicit permission to download and install the nfs-utils and policycoreutils packages if they are not already installed
    • --install-vtl: [Optional] installs components required for VTL support.

    OR

    • $ sudo ./qs_inst_7.4.0.222.bin

      and follow the prompts to :

      • provide a path for the storage directory
      • [Optional] provide a separate path for metadata storage
      • select an installation mode. Refer to QoreStor installation modes for more information
      • [Optional] install VTL support
      • [Optional] add firewall exceptions

      NOTE: To install VTL support, it is recommended to boot the QoreStor system with secure boot disabled..

Installing Qorestor with Protocols of Choice

For QoreStor fresh installation, the RDS protocol support is mandatory while NFS, CIFS, VTL, and Object Container protocol support is optional. QoreStor installer will not add the missing protocol package/s at the time of upgrading software to a newer version. However, the user can choose to install the missing protocol support at a later stage using following options:
qs_installer.bin --[--install-nfs|--install-cifs |--install-vtl |--install-object-container] option.
After the installation of selected protocol, QoreStor enables the support for respective container types.
QoreStor installation with protocols of choice is done with one of the following methods.

Interactive mode standard QoreStor installation with protocols of choice

To perform interactive mode installation of QoreStor with protocols of choice, execute the following command and continue with supported navigation

# ./qs_inst_7.4.0.222.bin

NOTE:User is advised to accept the EULA. Continue with the further navigation.

      Following is the CLI output displayed while installation.

      [root@ol8_small_qs1 ~]# ./qs_inst_7.4.0.222.bin
      Verifying archive integrity... 100% MD5 checksums are OK. All good.
      Uncompressing QoreStor Server 7.4.0.222 100%


      === Checking server version ...
      Install/Upgrade Version: 7.4.0.222
      Getting object direct parameters...
      Object Direct Storage is available for storing data in the cloud.
      If you choose this option, you would be expected to enter a valid cloud connection string at a later stage.

      NOTE: VTL is not supported with Object Direct Storage. If you choose this option, VTL support will not be installed.

      Would you like to configure Object Direct Storage for storing data? yes/no: no
      Getting path information...
      Please provide the path for the storage repository: [/]
      /QSdata
      Optionally, please provide a path for metadata storage: [/QSdata]
      /QSmetadata
      Please select a storage configuration:
      Enterprise-Plus: 512TB maximum storage capacity, 384GB dictionary
      Enterprise: 360TB maximum storage capacity, 256GB dictionary
      Standard: 150TB maximum storage capacity, 256GB dictionary
      Small (Cloud-Optimized): 43TB maximum storage capacity, 256GB dictionary
      1) Enterprise-Plus 3) Standard
      2) Enterprise 4) Small (Cloud-Optimized)
      #? 4
      Small (Cloud-Optimized) configuration selected

      === Configuration Mode: cloud-optimized ===
      iSCSI and NDMP VTL support is available for this kernel.

      Note: Installing support for iSCSI and NDMP VTL will consume additional memory and introduce a kernel dependency.
      As a result, kernel upgrades will be limited while QoreStor is present.
      Choose this option only if you require iSCSI and NDMP VTL.
      Do you wish to install support for VTL? yes/no: no
      VTL support will not be installed.
      CIFS support is available.
      Do you wish to install CIFS support? yes/no: yes
      CIFS support will be installed.
      NFS support is available.

      NOTE: Please note that NFS support is required for Instant Restore of
      CDP backups written to RDS containers.
      Do you wish to install NFS support? yes/no: yes
      NFS support will be installed.
      Object Container support is available.
      Do you wish to install Object Container support? yes/no: yes
      Object Container support will be installed.

      Checking dependencies:
      ...Checking nfs-utils... yes
      ...Checking policycoreutils... yes
      ...Checking glibmm24... yes
      ...Checking krb5-libs >= 1.15.1.18... yes
      ...Checking libsemanage >= 2.5.8... yes
      ...Checking libaio... yes
      ...Checking perl... yes
      ...Checking mutt... yes
      ...Checking yum-utils... yes
      ...Checking bind-utils... yes
      ...Checking libnsl... yes
      ...Checking boost... yes
      ...Checking xmlrpc-c... yes
      ...Checking xmlrpc-c-client... yes
      ...Checking bzip2-devel... yes
      ...Checking rpcbind... yes
      ...Checking libidn... yes
      ...Checking attr... yes
      ...Checking sqlite... yes
      ...Checking libxml2... yes
      ...Checking rsyslog... yes
      ...Checking openssl... yes
      ...Checking lsof... yes
      ...Checking python36... yes
      ...Checking lsscsi... yes
      ...Checking audit-libs... yes
      ...Checking jq... yes
      ...Checking libxslt-devel... yes
      ...Checking libxml2-devel... yes
      ...Checking python36-devel... yes
      ...Checking gcc... yes

      === Evaluating System...
      --
      Supported Linux Distributions: centos rhel ol rocky almalinux
      Found Linux Distribution: ol
      OS Test: PASS
      --
      Supported Kernel Versions: 4.18.0-477 4.18.0-513
      Found Kernel: 4.18.0-513
      Kernel Test: PASS
      --
      Min. Required # of CPU Cores: 4
      Actual # of CPU Cores: 4
      CPU Test: PASS
      --
      Min. Required System Memory (GB): 32
      Actual System Memory (GB): 32
      Memory Test: PASS
      --
      Min. Required Available Space in /QSdata (GB): 500
      Actual Available Space in /QSdata (GB): 989
      Available Space Test: PASS

      === Running IOPS tests...
      Min. Required Seq. Write IOPS for /QSdata: 450
      Actual Seq. Write IOPS for /QSdata: 42005
      Seq. IOPS Test: PASS
      Min. Required Random Write IOPS for /QSdata: 450
      Actual Random Write IOPS for /QSdata: 34472
      Random IOPS Test: PASS
      Min. Required Available Space in /QSmetadata (GB): 1024
      Actual Available Space in /QSmetadata (GB): 1025
      Available Space Test: PASS

      === Running IOPS tests...
      Min. Required Seq. Write IOPS for /QSmetadata: 450
      Actual Seq. Write IOPS for /QSmetadata: 41404
      Seq. IOPS Test: PASS
      Min. Required Random Write IOPS for /QSmetadata: 6000
      Actual Random Write IOPS for /QSmetadata: 15623
      Random IOPS Test: PASS
      --
      ... Done ===

      Required Mount Options for /QSdata: noatime
      Found Options for /QSdata: noatime
      Required Mount Options for /QSmetadata: noatime
      Found Options for /QSmetadata: noatime
      === Preparing components for install/upgrade...
      === Installing Version 7.4.0.222...
      Stopping service: ...

      Installing component: samba
      Installing component: PBIS-OPE
      Installing component: oca-libs
      Installing component: choam-prod-1
      Installing component: storage-server-el
      Installing component: qs-libfuse3-3
      Installing component: objstor-minio-20230320201618
      Installing component: qorestor-ui
      ... Done.

      === Configuring system...
      Repository Path: /QSdata
      Metadata Path: /QSmetadata
      [Mon Apr 15 10:50:01 PDT 2024] Configuring time-series database...[Done]
      Would you like to automatically add firewall exceptions for ports used by storage-server? yes/no: yes

      [Mon Apr 15 10:50:18 PDT 2024] Initializing configuration files... [Done]
      [Mon Apr 15 10:50:18 PDT 2024] Creating and initializing ingest buffer...[Done][Mon Apr 15 10:51:32 PDT 2024] Creating and initializing de-duplication dictionary... [Done]
      [Mon Apr 15 10:51:32 PDT 2024] Checking for and generating self-signed certificate...
      [Done]
      [Mon Apr 15 10:51:32 PDT 2024] Checking for and generating SAML SP certificate...[Done]
      [Mon Apr 15 10:51:32 PDT 2024] Installing services... [Done]
      [Mon Apr 15 10:51:32 PDT 2024] Initializing services... [Done]
      [Mon Apr 15 10:51:35 PDT 2024] Adding firewall exceptions... [Done]
      ... Done.

      Checking for and installing required python packages...... Done.
      === Server installed/upgraded 7.4.0.222 successfully.
      === Starting services ===
      Starting service: choam ...
      Stopping service: ...
      Starting service: ocards ...
      ... Done.
      === Management interface: https://ol8_small_qs1.ocarina.local:5233 ===

      Silent mode installation with protocols of choice

      Silent mode installation with protocols of choice executes QoreStor installation in cloud optimized mode with support for CIFS and NIS protocols along with mandatory RDS protocol installation. To choose correct mode, size of installation, and required protocol support, refer to Installing QoreStor in Object Direct mode, table number 5.
      The following example shows the above mentioned installation process.

      # ./qs_inst_7.4.0.222.bin -- -f -p /Qorestor -m /QSmetadata --accept-eula --install-deps --fix-mount-opts --no-vtl --no-object-container --no-object-direct --mode=cloud-optimized --install-cifs --install-nfs

      Adding protocol support post QoreStor installation

      You can add the missing protocol support to the installation by passing the appropriate arguments to the installer from the following options
      [--install-nfs|--install-cifs |--install-vtl |--install-object-container]

      Example:-

      For installing VTL support
      # ./qs_inst_7.4.0.222.bin -- --install-vtl

      For installing the CIFS protocol
      # ./qs_inst_7.4.0.222.bin -- --install-cifs

Logging in to QoreStor

To access the QoreStor UI, you must connect via a supported browser.

To access the QoreStor UI

  1. In a supported browser, navigate to https://<hostname:5233>

    NOTE: You can use either the host IP or hostname.

  2. Log in with the default credentials:
    • username: admin
    • password: St0r@ge!

NOTE: Change the default password when you first log in to QoreStor.

To access the QoreStor command line interface

  1. Using the terminal emulation application of your choice, connect to your QoreStor server.
  2. Starting with version 7.1, the qsadmin and qsservice users are not created on a fresh installation of QoreStor. Create a new user or employ an existing account to dedicate a user for QoreStor administration with the following command:

    /opt/qorestor/bin/setup_qs_user.sh <provide-user-namehere>

    For QoreStor instances created with OVAs or from Azure Marketplace, refer to the respective guides.

  3. At the system prompt, enter the username for an account with super user privileges.
  4. For a list of QoreStor CLI commands, refer to the Quest QoreStor Command Line Reference Guide.

Upgrading QoreStor

This section is applicable to all QoreStor instances, including Virtual Machine instances (ESX and Hyper-V), AWS and Azure Marketplace instances, and DR Series migrated systems.

Depending on your environment and your comfort level with working in the Linux command line, you can upgrade using one of the following methods:

  • The Linux shell - Through the Linux shell you can manually upload the binaries, verify and change file permissions, and run the installer with additional parameters. Refer to Upgrading your QoreStor software using Linux shell
  • The QoreStor UI - In circumstances where access to the QoreStor server is restricted (or for those that choose not to upload the QoreStor binaries via the Linux shell), you may use the QoreStor UI to upload the QoreStor binary and signature files from your workstation. After uploading the files, you must run the upgrade from the Linux shell.  Refer to Upgrading QoreStor Software using the QoreStor UI.

Both upgrade methods require that you download the new binaries from the Quest website and run them on the QoreStor server.

Prior to upgrading, review the best practices and recommendations in Before you upgrade.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating