QoreStor 7.1.0 - Release Notes

The following is a list of features that are no longer supported starting with QoreStor 7.1.

• Microsoft Internet Explorer browser
• QS Menu

This topic contains important information for users who are upgrading from a previous QoreStor release.

• If the existing installation of QoreStor uses the default passwords for the UI admin login, qsservice user, or qsadmin user, then you must update these passwords before upgrading to QoreStor 7.1
• In version 7.1, auto upgrade is not available from the QoreStor Menu.
• AWS Lambda and IAM permissions are required for an archive tier. After you complete an upgrade, to update the IAM roles and permissions, see the Quest QoreStor Release Notes.
• Existing QoreStor installations can not be upgraded to use Object Direct storage. To use QoreStor in Object Direct mode, you must perform a fresh installation.
• During the upgrade, the QoreStor installation script will verify that the Repository and Metadata filesystems are mounted with the noatime and dirsync mount options. If not, the installation script will prompt the user to allow the script to make the necessary changes in /etc/fstab and prompt you to reboot the system and re-run the QoreStor installation process.

  NOTE: The above process does not occur when installing QoreStor in Demo mode.

• To ensure proper authentication of network shares, after upgrading to QoreStor 7.1, remove the QoreStor server from the domain and re-add it to the domain.
• The metadata volume storage requirement for Object Direct configuration has been extended to 1.5TB, 8TB, and 18TB for cloud-optimized, standard, and large modes. Although it is not mandatory to extend the metadata volume on existing QoreStor instances before upgrade, Quest recommends you extend the volume when it is reaches 90% full.
• QoreStor 7.1 contains VTL support for RHEL, CentOS, and Oracle Linux versions 8.3 and 8.4. To enable VTL support, see the Quest QoreStor Installation Guide.

  When using QoreStor 7.0.1 with VTL on CentOS 8.2, RHEL 8.2, or Oracle Linux 8.2 and want to upgrade to CentOS 8.4, RHEL 8.4, or Oracle Linux 8.4, upgrade QoreStorbefore upgrading the operating system.

Upgrading QoreStor instances on Microsoft Azure

For QoreStor instances running on Microsoft Azure, perform the actions below before upgrading to 7.1.

• At the prompt, run the following commands:

  curl -o azureclient.rpm https://rhui-1.microsoft.com/pulp/repos/microsoft-azure-rhel7/rhui-azure-rhel7-2.2-74.noarch.rpm

  sudo rpm -U azureclient.rpm

  sudo yum clean all

Upgrading a migrated DR Series appliance to QoreStor 7.1.0.248

If you have previously migrated your DR Series system to a version of QoreStor prior to 6.1.0.814, then you must upgrade your QoreStor software to build 6.1.0.814 before upgrading to build 7.1.0.248. The upgrade process in build 6.1.0.814 includes a step that flushes WAM data, and that process must be completed before upgrading to 7.1.0.248.

Upgrading to Rapid CIFS Plug-in 4.0.3.3 with Secure Connect

Secure Connect is comprised of a set of client and server components that create a resilient and secure communication channel for use by WAN-connected clients. The server components are installed and enabled by default during the installation of the QoreStor server. Starting with the Rapid CIFS plug-in version 4.0.3.3, the plug-in installer includes the option to install and enable Secure Connect.

If you have WAN-connected Rapid CIFS clients and choose to install Secure Connect, you can do so by following the steps below:

1. On the media server, map a network share to your CIFS-enabled container.
2. Download the plug-in installer from the website, as detailed previously.
3. Open a command prompt with the “Run as Administrator” option selected. To do this using the Windows Start menu, click Start → All Programs → Accessories. Right-click Command Prompt and selectRun as Administrator.

   This gives all the required privileges to install/copy the driver files to the Windows drivers folder.

4. Run QuestRapidCIFS-4.0.3318.0.exe.
5. When prompted, select Install a Secure Connection to install Secure Connect.

   Secure Connect ensures backups to QoreStor are completed in spite of slow or unreliable WAN connections. When selecting this option, you will be prompted for additional configuration information required to make Secure Connect function correctly.

6. At the Configure Secure Connect page, complete the dialog using the IP or fully qualified domain name (FQDN) of the QoreStor server and appropriate credentials.

   The user account used must have the CIFS role assigned.

   NOTE: The Configure Secure Connect operation is not supported for CIFS containers on DR Series appliances. DR Series appliances do not contain the required Secure Connect server component . This operation is available only for QoreStor instances. For CIFS containers on DR Series appliances, connect using the Rapid CIFS plug-in and the DR Series host name.

   NOTE: The value entered in the Display Name field must not match the hostname of the QoreStor server.

Upgrading to Rapid NFS Plug-in 4.0.3.3

Secure Connect is comprised of a set of client and server components that create a resilient and secure communication channel for use by WAN-connected clients. The server components are installed and enabled by default during the installation of the QoreStor server. Starting with the Rapid NFS plug-in version 4.0.3.3, the plug-in installation script includes the option to install and enable Secure Connect.

If you have WAN-connected Rapid NFS clients and choose to install Secure Connect, you can do so by following the steps below:

1. Download QuestRapidNFS-4.0.3317.0-x86_64.bin.gz from the website.
2. Unzip the package using the following gunzip command:

   gunzip QuestRapidNFS-4.0.3317.0-x86_64.bin.gz

3. Change the permission of the binary package to allow it to run:

   chmod +x QuestRapidNFS-4.0.3317.0-x86_64.bin

4. Install the Rapid NFS package. Before installing, remove the stale NFS entry.

   QuestRapidNFS-4.0.3317.0-x86_64.bin -install

5. Load the file system in user space (FUSE) module, if not already loaded:

   modprobe fuse 
   

6. Create a directory on the client. For example:

   mkdir /mnt/backup

7. Mount Rapid NFS as a file system type using the mount command. For example:

    mount -t rdnfs 10.0.0.1:/containers/backup /mnt/backup 
   

   To enable Secure Connect, mount Rapid NFS using the sc flag, as shown below:

   mount -t rdnfs 10.0.0.1:/containers/backup /mnt/backup sc,user=backup_user,password=<backup_user password>

   If you are using a DMA that supports a marker, set the marker by using -o in the mount command. For example, if you wanted to set the CommVault marker (cv):

   mount -t rdnfs 10.0.0.1:/containers/backup /mnt/backup -o marker=cv

   NOTE: If you want to do a mount on AIX, you must set the nfs_use_reserved_ports and portcheck parameters first. The parameters cannot be set to 0. For example: root@aixhost1 / # nfso -po portcheck=1 root@aixhost1 / # nfso -po nfs_use_reserved_ports=1

The following is a list of issues addressed in this release.

Table 1: Resolved issues in build 7.1.0.248

Known issues

The issues below are known to exist in this release.