|
QS-437
QS-438 |
When using multiple NetVault Servers to access the same QoreStor Server, use storage group, container, and user names unique to each NetVault server to avoid accidental deletions. |
|
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-1666 |
When NetVault is installed on a Linux server, the RDA Client version is not displayed correctly.
Workaround:
To view the build number of the plugin, run the command
strings /usr/netvault/dynlib/librofsoca.so | grep "(EAR-4.1.0) Build:" |
| 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-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 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-5072 |
When authenticated to a domain, connecting to CIFS shares with a localhost account is not successful. |
| 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-6291 |
When using the latest version of the Rapid CIFS plug-in with Veeam Backup and Recovery, the configurations below are required:
- For the Backup Repository, change the Gateway Server option to The following server and enter the IP or hostname of the local machine.
- For VMware Backup, the Gateway server should be changed from the Automatic selection to the Use the selected backup proxy servers only.
|
| 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-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-6808 |
When configuring Backup Exec with CIFS shares using the display name, the steps below must be followed:
- In the command prompt, change directpries to the path C:\Program Files\Quest\Rapid CIFS.
- Run rdcifsctl.exe sc -d for disable a secure connection.
- Configure storage in Backup Exec by specifying \\displayname\container as network share. During this configuration all connections from Backup Exec to QoreStor are secured.
- Run rdcifsctl.exe sc -e to enable a secure connection.
|
| QS-6860 |
During upgrade, the SMB config file is overwritten. Any manual changes to this file will be lost on upgrade. |
| QS-8945 |
When QoreStor is installed on Linux versions 7.3 - 7.7, configuring an archive tier may result in a memory leak. This is due to an issue with the curl package installed on those versions of Linux.
Workaround
Either upgrade the Linux version on the QoreStor server to 7.8, or update the curl package to curl 7.29.0-57.el7. DR Series systems migrated to QoreStor which are on Oracle Linux 7.3 should update the curl package to 7.29.0-57.el7 |
| QS-9056 |
On DR Series Systems migrated to QoreStor, the maximum inode limit for an object container is set to 1 million. In some cases, this may result in a "maximum allowable File(s) and Directories limit" error.
Workaround:
To increase that, the environmental variable MDS_OT_INODES_ALLOWED in /etc/oca/customer.env has to be set to a higher value. Please contact Quest Support for assistance making this change. |
| QS-9021 |
During object direct installation, if the message "Failed to validate object direct connection string! "may be received if the certificate has been changed or is expired on the QoreStor server.
Workaround
Purge the certificate with the command below
cloud_tier --purge-ssl-certificate |
| QS-9177 |
When configuring the Rapid NFS client with Secure Connect, You may mount the plug-in with either the IP address or the fully qualified domain name (FQDN). If you use the FQDN, you must also add an entry in the /etct/hosts file on the QoreStor system and verify that the hostname is resolvable. |
| QS-10018 |
When writing to an NFS container on a system with 24GB or less of memory, some customers may receive "out of memory" errors.
Workaround:
On the QoreStor system, run the command sysctl -a | grep tcp_mem.
This will return your tcp memory consumption, like the example value below. The return indicates your minimum, average, and maximum values.
net.ipv4.tcp_mem = 285198 380264 570396
Using the command below, set the tcp_mem maximum value to the average value (380264, in the example above). Note that your values will be different. The value in the center is the average.
sysctl -w "net.ipv4.tcp_mem=285198 380264 380264" |
| QS-10042 |
When attempting to delete a bucket containing a large amount of data, QoreStor will appear to freeze. This is due to an AWS S3 limitation that requires the objects within a bucket to be deleted before the bucket can be deleted. During the bucket delete operation, the objects are enumerated and deleted one at a time.
Workaround:
Before deleting the bucket, delete the objects within the bucket using the AWS S3 console. |
| QS-10117 |
System stops while upgrading from the user interface terminal. |
| QS-10772 |
Replication update fails with replication between QoreStor 7.1.2 and the DR appliance.
Workaround:
For DR-to-QoreStor replication, update replication by way of the QoreStor user interface or command line interface. |
| QS-11329 |
During replication, crash may occur on a target if the replication source has archive tier configured. |
| QS-11588 |
When there is not enough space under "/opt" to install or upgrade QoreStor, an error message occurs.
Workaround:
Free space under the "/opt" partition. |
| QS-11613` |
During replication, QoreStor is unable to locate a specific blockmap entry.
Workaround:
If a replication source already has archive tier replication, do not configure archive tier replication on the replication target. |
| QS-11818 |
New backups jobs fail with Backup Exec 20.x after stubbing the existing data.
Workaround:
Delete the Changer.cfg meta file in the CIFS container, which triggers the start of a new backup job. |
| QS-11819 |
Received the following error: RDA SRVR RDA_OPEN_FILE : failed to add open image to hash map for LSU 9 scid 1152921504606847079 (Bad file descriptor). |
| QS-11851 |
The directory uploading using AWS CLI to Object Tier may become unresponsive if the directory has large files. |
| QS-11936 |
Netvault Backup Jobs may stall if cloud upload on QoreStor is not happening because of cloud provider experiencing high request rate. |
| QS-11972 |
Adding replication between DR 4.0.4 and QoreStor 7.1 fails.
Workaround:
Run the replication commands on QoreStor. |
| QS-12017 |
QoreStor cannot add replication in a situation when there are two Secure Connect server processes and one is in unknown state after upgrade.
Workaround:
Stop the old Secure Connect server in the unknown process. |
| QS-12113 |
Alert generated for OFSCK scan is still present after QoreStor becomes operational. |
| QS-12117 |
During replication, the error "Failed to set ns txlog csn on scid" occurs.
Workaround:
You can ignore these messages. Replication eventually succeeds. |
| QS-12154 |
QoreStor is not opertional after Disaster Recovery from cloud tier. |
| QS-12228 |
Storage group encryption once disabled cannot be enabled. |
| QS-12240 |
Replication add from migrated QS between RDA containers may fail. |
| QS-12260 |
VTL tape export is successful even without cloud replication configured. |
