This topic contains important information for users who are upgrading from a previous QoreStor release.
|
NOTE: The above process does not occur when installing QoreStor in Demo mode. |
|
IMPORTANT: Uninstalling your existing QoreStor with the command below will preserve your data and application configurations. /opt/qorestor/bin/qs_uninst When running this command, you will receive the prompt: To completely remove the application, user data, and configuration files, answer 'no' below, and rerun the uninstaller with the '-a' option. Do you wish to continue? yes\no [no]: Enter Yes to continue without removing your data. |
For QoreStor instances running on Microsoft Azure, perform the actions below before upgrading to 6.1.
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
If you have previously migrated your DR Series system to QoreStor, you must upgrade your QoreStor software to build 6.1.0.814 before upgrading to this build (6.1.0.840). 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 6.1.0.840.
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.2, the plug-in installer includes the option to install and enable Secure Connect.
|
IMPORTANT: Refer to the Known Issues section of this document for Rapid CIFS issues known to be present at the time of release. |
If you have WAN-connected Rapid CIFS clients and choose to install Secure Connect, you can do so by following the steps below:
This gives all the required privileges to install/copy the driver files to the Windows drivers folder.
QuestRapidCIFS-4.0.3233.1.exe.
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.
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. |
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.
|
IMPORTANT: This new plug-in supports:
|
If you have WAN-connected Rapid NFS clients and choose to install Secure Connect, you can do so by following the steps below:
QuestRapidNFS-4.03310.0-x86_64.bin.gz
from the website.
unzip QuestRapidNFS-4.03310.0-x86_64.bin.gz
chmod +x QuestRapidNFS-4.03310.0-x86_64.bin
QuestRapidNFS-4.03310.0-x86_64.bin -install
modprobe fuse
mkdir /mnt/backup
mount -t rdnfs 10.0.0.1:/containers/backup/mnt/backup -o sc,user=backup_user,password=<backup_user password>
If you do not wish to type the password in plan text do not include the “password” option and you will be prompted:
mount -t rdnfs 10.0.0.1:/containers/backup /mnt/backup -o sc,user=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
It is also possible to use fstab entriest without the password option, this will prompt for the password the first time but will use the password hash for future mounts. With this it is possible to mount on boot without interrupting boot or prompting for a password:
10.0.0.1:/containers/backup /mnt/backup rdnfs sc,user=backup_user,marker=cv,defaults,soft,netdev,intr 0 0
|
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: |
/opt/qorestor/bin/connection --update --name nfs1 --type NFS --options rw,insecure
The following is a list of issues addressed in this release. For convenience, defects resolved in previous QoreStor 6.1 builds are also listed.
Table 1: Resolved issues in build 6.1.0.840
Issue ID | Resolved Issue |
---|---|
QS-8164 | Updated OST plug-in to install correctly on newer versions of Veritas Backup Exec |
QS-8332 | Status polling is occuring too frequently, causing RDA connections on DR Series Systems and QoreStor devices to appear to be alternating between offline and online states |
QS-8342 | Increase maxium number of CIFS clients to 128 in large mode |
QS-8343 | Copying files from one CIFS container to another CIFS container causes smbd to crash |
QS-8360 | Added installer support for Red Hat Enterprise Linux, CentOS, and Oracle Linux 7.8 |
QS-8441 12345678 |
sc_clinet crashed during a NetVault Plug-in for Oracle backup to QoreStor with Secure Connect enabled |
Table 2: Resolved issues in build 6.1.0.838
Issue ID | Resolved Issue |
---|---|
QS-6977 | Fix memory leak during replication on migrated DR Series systems which could result in ocafsd crash. |
QS-7709 | Fix memory leak during replication which could result in ocafsd crash. |
QS-7119 | Replication from QoreStor to DR Series appliance fails with mismatch error. |
QS-7121 | When joining a domain via the QoreStor UI, the option to add a login group does not function. |
QS-7462 12345678 |
QoreStor is unable to write files on NFS shares on Windows server. |
Table 3: Resolved issues in build 6.1.0.833
Issue ID | Resolved Issue |
---|---|
QS-6742 | Replication stopped because of an error due to race with cleaner. |
QS-6759 | After migrating a DR Series system to QoreStor, the Capacity Used value is displayed as 0. |
QS-6803 | Added documentation to address requirements for upgrading a previous DR Series appliance to QoreStor build 6.1.0.833. Refer to Upgrade notes for more information. |
QS-6859 | Updated cipher support to deprecate TLS v1.0 and v 1.1 |
QS-6861 | Added QoreStor Menu options for managing qsservice and qsadmin user accounts. |
QS-6960 12345678 |
qsservice and qsadmin commands have been modified to use system defaults when creating home directories. |
Table 4: Resolved issues in build 6.1.0.814
Issue ID | Resolved Issue |
---|---|
QS-5220 | Request: Add more detail to Network Interfaces page. |
QS-5370 | Fix core on aborting NDMP backups in case of socket error |
QS-5879 | Port DR fix for Fiber connection race condition in ocafsd |
QS-6044 | Removed http option for AWS connection |
QS-6045 | Implemented full avoid_dup option for QoreStor |
QS-6206 | Corrected formatting on Container Details page |
QS-6207 | Updated Cloud Tier "Need Help?" content to include additional cloud providers. |
QS-6209 | Improve visibility on graphs when viewing multiple variables with some colors repeating |
QS-6266 | Correct password reset in some special corner cases using qorestor admin password |
QS-6403 | When using the OST plug-in with Backup Exec, intermittent plvsvr.exe crash as a result of error recovery in queue manipulation |
QS-6410 | When reading data with robocopy, memory consumption steadily increases and never comes back. |
QS-6485 | Updated cloud tier documentation to to reflect inability to edit a file once stubbed. |
QS-6538 | QoreStor generating core dump when using policy manager |
QS-6587 QS-6589 |
Cleaner Core during migration as a result of deleting cleaner stat file |
QS-6612 | QoreStor becoming stuck in loop during optimized file system check. |
QS-6682 QS-6714 12345678 |
Corrected core in secure connect code due to double free during error recovery |
The issues below are known to exist in this release.
ID | Issue |
---|---|
QS-437 QS-438 |
When using multiple NetVault Backup Servers to access the same QoreStor Server, use storage group, container, and user names unique to each NetVault Backup server to avoid accidental deletions. |
QS-627 12345678 |
After deleting a container and storage group, immediately creating a new container with the same name may fail. Workaround: This failure occurs because the old container is still in a delete_pending stage. To proceed with creating a new container, wait until the old container has been completely deleted via the QoreStor Cleaner run. |
QS-1420 |
When executing the QoreStor uninstallation script, the script will report and continue if illegal options are entered. |
QS-1446 |
If the QoreStor partition is not set to automount, and the QoreStor server is rebooted, the system appears to be operational but shows 0 physical capacity. |
QS-1588 | When running Optimized Duplication jobs in Backup Exec, the container quota is not enforced as it is for backup jobs. |
QS-1670 | For Linux clients, the full version number of RDA plug-ins is not displayed. |
QS-1823 |
In some situations, the deduplication savings for a storage group shows as 100% before a backup has occurred. Once a backup has occurred, the deduplication savings will be displayed accurately. |
QS-1980 |
When deleting a storage group, the Storage Group page will display timestamp data where the storage group entry used to appear. This occurs because the storage group is still in a delete_pending stage. Once the delete is completed and the UI refreshes, the timestamp will not longer appear. |
QS-2236 |
When installing QoreStor, if a required port is unavailable the installation will continue and be considered successful, yet QoreStor will start in Maintenance Mode. Workaround: Ensure that all required ports are available to QoreStor. |
QS-2242 |
When installing QoreStor, the filesystem selected for the QoreStor repository should not contain data from other application or users. QoreStor must have exclusive access to the repository filesystem. |
QS-2604 |
If unregistered clients access QoreStor CIFS shares by mounting the share, the /var/log/messages will contain numerous host name/mismatch errors. Workaround: Unregistered clients need to be updated in DNS server manually. |
QS-2694 |
When the system time on the QoreStor server is synchronized with the domain time, this may cause the system time to adjust backwards. If this occurs, system statistics (like read/write throughput statistics) will appear to be hung for an amount of time equal to the time adjustment. |
QS-3779 |
When using Secure Connect with NetVault Backup in a multiple-machine configuration (NetVault server, NetVault client, QoreStor server), Secure Connect can respond to errors only for connections between the NetVault server and QoreStor or the NetVault client and QoreStor. Secure Connect does not address connections between the NetVault server and NetVault client. |
QS-4169 |
When using the Linux exports http_proxy or https_proxy, no_proxy is also required for the watcher service to function correctly. Refer to "Accessing QoreStor" in the QoreStor User Guide. |
QS-5105 | Changes to a Cloud Tier Policy for inclusions or exclusions will not take effect until the QoreStor service has been restarted. |
QS-5438 | After performing a DR to QoreStor migration, network settings are reset to default. |
QS-5627 | The current error output of "rda --limit" without any argument incorrect suggests limits are enforced via Mbps (megabits per second) when the limit is actually in MBps (megabytes per second). |
QS-5629 |
When configuring a custom graph, if you select a period for which there is no data, the graph will be blank and display "No Data Available" |
QS-5826 | When performing a DR to QoreStor migration, bonding modes and MTU settings are not |
QS-5891 | Rapid CIFS is not supported on Windows Server 2016 with secure boot enabled. |
QS-6291 |
When using the latest version of the Rapid CIFS plug-in with Veeam Backup and Recovery, the configurations below are required:
|
QS-6653 |
OST MSI plugin reports a new version is already installed when installing an updated driver Workaround: Uninstall the OST driver before installing the newer driver |
QS-6662 |
Replication add for AIR should fail if replication_traffic and encryption options used in the --add CLI. Both replication_traffic and encryption options are irrelevant to AIR and user should not be allowed to use them while adding AIR replication. Above parameters are restricted in --update CLI so similarly should be blocked in add CLI. |
QS-6782 | When installing Rapid CIFS on Windows 2008 R2, the installation deploys driver version 4.0.3207.1 , causing the version displayed by rcifsctl.exe driver -q to be different from the version in the Windows Programs and Features dialog. The functionality of Secure Connect is not changed. |
QS-6803 | Customers running QoreStor on a DR Series appliance must perform an intermediate upgrade to 6.1.0.814 before upgrading to 6.1.0.840. |
QS-6808 |
When configuring Backup Exec with CIFS shares using the display name, the steps below must be followed:
|
QS-6860 | During upgrade, the SMB config file is overwritten. Any manual changes to this file will be lost on upgrade. |
QS-7029 | When using Rapid NFS with Secure Connect, the NFS container must have insecure option set. This must be done via the command line. Refer to Upgrade notesfor more information. |
QoreStor offers a backend capacity licensing model to allow for simple integration with other Quest Data Protection products.
|
NOTE: Term licenses are intended for specific customer use cases, i.e., licensing according to yearly billing cycles. A perpetual license is appropriate for most customers. |
QoreStor licenses are additive, meaning that if you purchase a 5TB license now, and a 10TB license in the future, you will have 15TB total capacity.
|
NOTE: Licenses for QoreStor are specific to the QoreStor server. When installing a license, the System ID for your QoreStor server is required. You can obtain the System ID with the command system --show | grep "System ID" |
QoreStor offers two methods for evaluation:
If you have purchased a standalone license, you can install it using the system --license command, as described in the QoreStor Command Line Reference Guide.
|
NOTE: When ordering a license, the System ID for your QoreStor server is required. You can obtain the System ID with the command system --show | grep "System ID" |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center