vRanger 7.8 - Integration Guide for Quest QoreStor

Getting started

vRanger integration quick start for Quest® QoreStor™

Integrating vRanger with QoreStor is achieved by adding the QoreStor instance to vRanger as a Quest Rapid Data Access (RDA) repository. The following steps describe the integration process at a high level, and provide links to the remaining topics for more exploration. Before implementing this solution in a production environment, read this information thoroughly.

1	Confirm integration requirements: Before starting the integration, confirm that you are using supported versions of vRanger and QoreStor. For more information, see Product requirements for integration.

2	Install and configure QoreStor: To install QoreStor and integrate with vRanger, perform the following operations:

▪	Install the QoreStor software: Download and install the QoreStor software onto a designated, properly configured server.

▪

Create a storage container: Containers function like a shared file system, which can be assigned a connection type of None (to be defined later), NFS/CIFS, or RDA (includes Rapid Data Storage [RDS] clients). Containers can then be accessed using Network File System (NFS), Common Internet File System (CIFS), or RDA.

 

IMPORTANT: For integration with vRanger, create an RDA container, with the RDA Type setting as RDS.

3	Install vRanger: Using the vRanger installer, install vRanger on a machine meeting the vRanger system requirements. For a high-level overview of the vRanger installation process, see Installing vRanger. For more information, see the Quest vRanger Installation/Upgrade Guide.

4	Create a Quest RDA repository: After vRanger is installed, add the QoreStor server to vRanger as a Quest RDA repository. Any backup written to this repository is deduplicated according to your QoreStor configuration.

vRanger integration quick start for Quest® QoreStor™

Getting started

vRanger integration quick start for Quest® QoreStor™

Integrating vRanger with QoreStor is achieved by adding the QoreStor instance to vRanger as a Quest Rapid Data Access (RDA) repository. The following steps describe the integration process at a high level, and provide links to the remaining topics for more exploration. Before implementing this solution in a production environment, read this information thoroughly.

1	Confirm integration requirements: Before starting the integration, confirm that you are using supported versions of vRanger and QoreStor. For more information, see Product requirements for integration.

2	Install and configure QoreStor: To install QoreStor and integrate with vRanger, perform the following operations:

▪	Install the QoreStor software: Download and install the QoreStor software onto a designated, properly configured server.

▪

Create a storage container: Containers function like a shared file system, which can be assigned a connection type of None (to be defined later), NFS/CIFS, or RDA (includes Rapid Data Storage [RDS] clients). Containers can then be accessed using Network File System (NFS), Common Internet File System (CIFS), or RDA.

 

IMPORTANT: For integration with vRanger, create an RDA container, with the RDA Type setting as RDS.

3	Install vRanger: Using the vRanger installer, install vRanger on a machine meeting the vRanger system requirements. For a high-level overview of the vRanger installation process, see Installing vRanger. For more information, see the Quest vRanger Installation/Upgrade Guide.

4	Create a Quest RDA repository: After vRanger is installed, add the QoreStor server to vRanger as a Quest RDA repository. Any backup written to this repository is deduplicated according to your QoreStor configuration.

Product requirements for integration

To integrate vRanger with QoreStor, you must be using one of the following supported product versions:

•

vRanger:

▪	7.7 or later — for RDA, CIFS, and NFS integration

•

QoreStor

▪	Refer to the QoreStor Interoperability Guide.

Product overviews

The following topics provide an overview of vRanger and QoreStor, and important information about the licensing required to integrate the two products.