vRanger 7.8 - Integration Guide for Quest QoreStor

Logging in to QoreStor

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

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!

Configuring your QoreStor server

The information below is summarized for ease of use. For detailed configuration information, see the QoreStor User Guide.

The information presented in Managing storage groups and containers is specific to the integration with vRanger. For more information on integrating vRanger with a Quest Rapid Data Access (RDA) repository, see the Quest vRanger User Guide.

Installing a License

You can add a license to QoreStor through either the QoreStor GUI or the command line interface.

To install a license:

1	In the navigation menu click System Configuration.

2	Scroll to the License Information section at the bottom of the page.

3	Click Upload License.

4	Click Choose File and select the license file. Click Open.

5	Click Apply.

 

NOTE: You may also install a QoreStor license from the command line interface using the command: system --license [--show] [--verbose] [--validate] [--file <path>] [--add] [--file <path>] Refer to the QoreStor Command Line Reference Guide for more information.

Managing storage groups and containers

To organize your data, you can easily create storage groups and create containers within those storage groups on your QoreStor system. A storage group allows you to create separate storage policies for different data groups and the different capacities utilized on a single QoreStor. After initialization, QoreStor contains a single default storage groupe named DefaultGroup.

In QoreStor, data is stored in containers, which are stored in storage groups. Some containers function like a shared file system. These types of containers can be assigned a specific connection type, for example, NFS/CIFS or RDA (including both OST and RDS clients). Containers can then be accessed using NFS, CIFS, or RDA.

 

IMPORTANT: For the most beneficial integration with vRanger, an RDA connection should be used.

Creating a storage container

NOTE: QoreStor does not support creating container names that begin with a 0 (zero).

Containers function like a shared file system that can be accessed using the following connection types:

•

NFS/CIFS

•

NFS

•

CIFS

•

RDA

•

RDS

Creating an RDS connection type container

To create an OST or RDS connection type container, follow these steps:

1	On the navigation menu, click Storage Groups, and then select the storage group for which you want to create a container. (If you are only using the DefaultGroup storage group on your QoreStor system, you do not need to select a group.)

2	In the storage group list, click the storage group to which you want to add a container. Click Add Container.

3	For the container Name, type the name of the container, and then click Next.

Container names cannot exceed 32 characters in length, must start with a letter, and can be composed of any combination of the following characters: l

▪	A-Z (uppercase letters)

▪	a-z (lowercase letters) l

▪	0-9 (numbers). Do not start a container name with a number. l

▪	dash (-) or underscore (_) special characters

IMPORTANT: QoreStor does not support creating container names that begin with a 0 (zero) or that include the following special characters /, #, or @.

4	For Protocol, select Quest Rapid Data Storage (RDS).

5	Click Next.

6	Leave LSU Capacity as Unlimited.

7	Click Finish.

Installing vRanger

vRanger system requirements

Before installing vRanger and QoreStor, ensure that you read and understand the requirements and operation of both products. The following topics summarize the system requirements for vRanger. The information is a summary only. Before implementing vRanger, review the Quest vRanger Installation/Upgrade Guide.

 

IMPORTANT: You must use a supported version of vRanger and QoreStor. For more information, see Product requirements for integration.