vRanger 7.8.6 - Integration Guide for Quest QoreStor

Review the QoreStor Installation Guide and QoreStor Interoperability Guide for information on system requirements and supported platforms. Ensure that the server on which you are installing QoreStor meets the installation requirements.

•

You must use a supported version of vRanger and QoreStor. For more information, see the QoreStor Interoperability Guide.

•

Review the QoreStor Installation Guide and QoreStor Interoperability Guide for networking and port requirements.

Installing QoreStor

To install QoreStor:

Download QoreStor from the Quest website.

Copy the QoreStor installation files to the QoreStor server.

Set execution permissions on the installation files using chmod. For example:

$ chmod a+x qs_inst_6.0.0.589.bin

With elevated privileges (either as root or with the sudo command), execute the installation script according to one of the two options below :

qs_inst_6.0.0.589.bin -- -f –p <repository_path> -m <metadata_path> --mode=<demo|cloud-optimized|standard|large> --accept-eula --install deps

where

-f specifies that the installer should automatically apply firewall rules to open the necessary ports l

-p <repository_path> specifies the repository path l

-m <metadata_path> specifies where the dictionary and journals should be stored.If not specified, the repository path will be used. l

--mode=<demo|cloud-optimized|standard|large> specifies the installation mode. Refer to the QoreStor Installation Guide for more information on installation modes.

demo: 100GB max storage, 1GB dictionary l

cloud-optimized: 43TB max storage, 64GB dictionary l

standard: 150TB max. storage, 256GB dictionary l

Large: 360TB max storage; 256GB dictionary l

–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

$ sudo ./qs_inst_6.0.0.589.bin

and follow the prompts to:

•

provide a path for the storage directory

•

[Optional] provide a separate path for metadata storage