Upgrade notes
This topic contains important information for users who are upgrading from a previous QoreStor release.
- 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 6.0, remove the QoreStor server from the domain and re-add it to the domain.
- QoreStor 6.0 contains support for VTL protocols. To enable VTL support, you must perform the following sequence of operations:
- Upgrade your existing installation to QoreStor 6.0. Do not select the option to install VTL support at this point.
- Using the steps documented in "Uninstalling QoreStor while maintaining configuration data" in the QoreStor Installation Guide, uninstall the newly updated QoreStor installation.
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.
- Reinstall QoreStor 6.0 with VTL support by either using the --install-vtl option or answering “yes” to the prompt for adding VTL support.
- When using QoreStor with VTL, upgrades to the operating system of the QoreStor server require additional configuration. Refer to "Upgrading the QoreStor Operating System" in the QoreStor Installation Guide.
Upgrading QoreStor instances on Microsoft Azure
For QoreStor instances running on Microsoft Azure, perform the actions below before upgrading to 6.0.
- At the prompt, execute 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
Resolved issues
The following is a list of issues addressed in this release. For convenience, defects resolved in build 6.0.0.589 and 6.0.0.585 are also listed.
Table 1: Resolved issues in build 6.0.0.670
| Issue ID | Resolved Issue |
|---|---|
| QS-5835 | CIFS user password does not support "." and other special characters. |
| QS-5975 | Domain usernames with "!" are not able to be used for logins to CLI or UI |
|
QS-3767 1234567 |
Updated RDCIFS certificate. |
Table 2: Resolved issues in build 6.0.0.589
| Issue ID | Resolved Issue |
|---|---|
| QS-3282 | Improved display of Fibre Channel information in QoreStor UI. |
| QS-5752 | NVRAM configuration setting not being retained during DR Series to QoreStor migration. |
| QS-5833 | Custom logos are not displaying correctly. |
| QS-5842 | Updated error message if modification to cloud-uploaded file is attempted |
| QS-5846 | QoreStor UI displays error "Throughput: Error when getting data for graph" after DR Series to QoreStor migration. |
| QS-5847 | Customer.env is not loading exports immediately on ocafds start. |
| QS-5849 | Improved performance of data migration during DR Series to QoreStor migration. |
| QS-5854 | After upgrading to QoreStor 6.0, graphs may not properly parse dates causing no data to be displayed. |
|
QS-5858 1234567 |
When upgrading QoreStor, if no previous database is found the upgrade will process continually, making the UI inaccessible. |
Table 3: Resolved issues in build 6.0.0.585
| Issue ID | Resolved Issue |
|---|---|
|
QS-4641 QS-5573 |
UI improvements related to displaying graphs and statistical data. |
| QS-5180 | For OST container, bytes restored field under client stats are being shown as N/A |
| QS-5215 | During vRanger backups to QoreStor, cleanup of open images which were open at the time of connection resets caused segfault in ocafsd |
| QS-5393 | Stats command usage failing intermittently with error "libcurl failed to execute the HTTP POST transaction" |
| QS-5580 | Added QoreStor Menu configuration option for proxy servers |
| QS-5585 | QoreStor will not display UI references to components not installed |
|
QS-5586 QS-5592 QS-5636 QS-5710 QS-5750 QS-5751 |
Improvements to the Cloud Tier and Edit Cloud Policy pages. |
| QS-5658 | For some containers, logical size was not being displayed. |
| QS-5660 | Resolved issue where diagnostics cannot be generated from UI when in maintenance mode. |
| QS-5689 | DR to QoreStor migration may fail with "Out of memory" error. |
| QS-5727 | When creating NAS containers in the UI, the default marker has been changed to AUTO. |
| QS-5733 | The "Logical Throughput To The Cloud" graph is not showing the data for reads. |
| QS-5737 | System is going to maintenance mode when replication is configured on selinux machine. |
| QS-5747 | With a proxy configured the UI is unable to configure a cloud tier |
| QS-5766 | The IOPS test for Add Enclosure function does not match requirements for a Large installation. |
Open issues
Known issues
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-1343 |
The Byte Ingested value for a container does not get reduced after space reclamation. This is by design as Bytes Ingested is a cumulative value |
|
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-2617 |
Due to corrections in the way that CPU and memory usage is captured and charted, CPU and memory usage will appear to increase after an upgrade to QoreStor 5.0.1. Actual resource usage is unaffected. |
| 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-2699 |
The QoreStor installation process requires that the Repository and Metadata file systems are mounted with noatime and dirsync mount options. If necessary, the QoreStor installer will make the required changes to /etc/fstab and reboot the QoreStor server. |
| QS-3766 |
Customers using Fibre Channel VTL on QoreStor 5.1.0 who then upgrade to QoreStor 5.1.0.670 will need to reconfigure FC VTL connections with the new target WWPN shown in the output of the fc --show command. |
| 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-4218 |
In situations where the QoreStor system time and the time on your cloud provider platform are out of sync, cloud authentication may fail with correct credentials. Workaround Ensure that QoreStor system time is not out of sync with your cloud provider. |
| 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-5781 | The DR to QoreStor migration is only possible for DR Series appliances that contain 63 or less containers in any storage Group. Storage Groups with 64 containers cannot be migrated. |
| 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. |
Product Licensing
QoreStor offers a backend capacity licensing model to allow for simple integration with other Quest Data Protection products.
- Standalone license - QoreStor is licensed by the amount of backend capacity required. Standalone licenses are available as either perpetual licenses (with no expiration), or term licenses, which expire after a specified period of time.
-
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" |
Evaluating QoreStor
QoreStor offers two methods for evaluation:
- Default installation - If no license is installed, QoreStor defaults to a no-cost, 1TB capacity installation supported by the QoreStor Community. This option requires no license and does not expire.
- If a license is applied to a server running in this mode, the free 1TB is not added to the purchased license capacity.
- When installed in Demo mode, the capacity is limited to 100GB.
- Full capacity trial - available on the Quest Software Trial site, which provides a 30-day evaluation license for up to 360TB and access to Quest Support. After the evaluation period has expired, the QoreStor server will operate in Manual Intervention mode until a license is applied. To use QoreStor beyond that time frame, you will need to purchase a perpetual standalone license.
- If installed in Demo mode, the capacity is limited to 100GB
- If a longer trial period is required, please contact Quest Sales.
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" |