|
ID |
Issue |
Description |
Workaround/Solution |
|
20870 |
RPC replication errors may be seen during replication from source DR Series system to target DR Series system. |
|
The primary and secondary replication target should have the same MTU setting. Replication proceeds once the MTU is set to the same as the replica target. This recommendation has been added to the Dell DR Series System Administrator’s Guide in release 3.2.0.1. |
|
27074 |
iSCSI VTL configuration with IBM Tivoli Storage Manager 7.1.1 fails at audit tape library. |
|
Corrected in release 3.2.0.1. |
|
27074 |
Symantec Backup Exec inventory issue. |
|
Corrected in release 3.2.0.1. |
|
27013 |
Issue with an ofsck refcount record boundary calculation. |
|
Corrected in release 3.2.0.1. |
|
26721 |
NDMP VTL device offline issue. |
|
Corrected in release 3.2.0.1. |
|
26548 |
Kernel panic fix for VTL running in parallel with other protocol heavy replication. |
|
Addressed in release 3.2.0.1. |
|
26493 |
Option added to increase RDA retry capability in registry working with Tech Support. |
|
Addressed in release 3.2.0.1. |
|
26282 |
Support for RDA for Sparc. |
|
Addressed in release 3.2.0.1. |
|
26265 |
DR plugin DellDRLogSvc service does not always stop when uninstalling NetVault. |
|
Corrected in release 3.2.0.1. |
|
26190 |
Various VTL updates for release 3.2.6 ported to 3.2.0.1 code. |
|
Addressed in release 3.2.0.1. |
|
26128 |
RFE: OFSCK: re-organized refcnt record structure to optimize disk space. |
|
Addressed in release 3.2.0.1. |
|
26113 |
NFS fix for moujnt during stats call. |
|
Corrected in release 3.2.0.1. |
|
25958 |
Veeam ingest and replication issue for large file overwrite corner case. |
|
Corrected in release 3.2.0.1. |
|
25860 |
NetVault Backup stats file takes a long time in closing. |
|
Corrected in release 3.2.0.1. |
|
25675 |
ocafsd crashed on cleaner code due to corner case. |
|
Corrected in release 3.2.0.1. |
|
25591 |
Space handling improvements related to global space thresholds and per enclosure thresholds for Rapid NFS and Rapid CIFS. |
|
Addressed in release 3.2.0.1. |
|
25584 |
Improved seeding for CIFS on slow networks |
|
Addressed in release 3.2.0.1. |
|
25393 |
Cleaner is now set to run during idle time even when not in schedule. Since the machine is idle cleaning will occur; it will be stopped if I/O is started. |
|
Addressed in release 3.2.0.1. |
|
25135 |
Let cleaner finish if it is in runonce mode even if there is a cleaner schedule stop. |
|
Addressed in release 3.2.0.1. |
|
25091 |
cifs_iobuf_alloc fix for iSCSI. |
|
Addressed in release 3.2.0.1. |
|
24998 |
Fixed complex replication deadlock scenario involving overwrites and aborts. |
|
Addressed in release 3.2.0.1. |
|
24855 |
VTL subsystem starts if container name contains "ISCSI" or "NDMP" even though the container type is not 'vtl'. |
|
Corrected in release 3.2.0.1. |
|
24809 |
Corner case fix for cascaded replication. |
|
Addressed in release 3.2.0.1. |
|
24738 |
Validate the timestamps in mds supplied by user. |
|
Addressed in release 3.2.0.1. |
|
24701 |
DR VTL was showing support for hardware encryption, which is not accurate. Removed this option as Symantec was allowing encryption setting. (SPIN, SPOUT and publishing in MODE SENSE) |
|
Corrected in release 3.2.0.1. |
|
24689 |
Some of the documentation PDF links were not working in the DR Series system GUI. |
|
Corrected in release 3.2.0.1. |
|
24579 |
Unable to log in using domain user starting with letter "j". |
|
Corrected in release 3.2.0.1. |
|
24571 |
Enclosure showing as “Not Configured” when another enclosure is added, which changed ID numbers. |
|
Corrected in release 3.2.0.1. |
|
23887 |
Corner case where cleaner schedule will not stop cleaner from running, nor does the cleaner stop command. |
|
Corrected in release 3.2.0.1. |
|
23797 |
NDMP user name must be changed to ndmp_user in GUI. |
|
Addressed in release 3.2.0.1. |
|
24312 |
Certain hypervisor host NICs will perform poorly and may require a driver update to fully support VMQ feature. |
|
Note that this works as designed. To resolve this issue you should check on your Hypervisor host NIC feature list and update the driver to the latest version.
For example, Broadcom NetXtreme I and NetXtreme II Ethernet adapter needs to get driver update to 17.6.0 or above to add VMQ support, otherwise you may experience performance degradation during normal operations.
Driver for NetXtreme I and NetXtreme II Ethernet adapter: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=CYKKJ&osCode=MWS80&fileId=3197327398&languageCode=EN&categoryId=NI
Firmware for NetXtreme I and NetXtreme II Ethernet adapter: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=P32M4&osCode=MWS80&fileId=3197328666&languageCode=EN&categoryId=NI |
|
20539 |
After installing Rapid CIFS Filter Driver, an incorrect driver version is displayed. |
|
If at the end of successful installation, the version of the driver loaded (which can be checked using rdcifsctl.exe driver -q) is lower than the version of the installed package (listed under Control Panel > Installed products), then you should restart the machine. This issue can occur if the system fails to rename/delete driver files under the system folder. |
|
20456 |
Installation of SSL Certificate file in the GUI failed on Internet Explorer (IE) when using Remote Desktop. |
|
When uploading the certificate file, the GUI uses the file name with the whole path, which works when uploading on a local system. When using RDP, in the IE browser settings, you need to disable the "Include local directory path .." setting, as follows.
|
3. |
Click OK and the refresh the browser. | |
|
20424 |
The following message may appear on the console: “vx_nospace...” even if the system still has space. |
|
This message is a result of trying to allocate a large contiguous block. The allocation of the contiguous block might fail, in which case, allocation continues without trying to keep the file contiguous. The vx_nospace error may appear, and this message can be safely ignored. |
|
20188 |
When using cascaded replication for a large number of files (1M+), it may appear to take some time to see the actual files on the secondary target. |
|
Namespace resync has to complete on the source and primary target and then data transfer has to start on both before transferring to the secondary target. Once the namespace resync completes on the first replication pair, resync then starts on the second replication pair. Until the namespace resync completes on the second pair, no data is transferred. This ensures the namespace resync completes faster and the snapshot can be deleted faster. |
|
20009 |
User is able to create/write a file/directory in the share/container even though the user has only read permissions (file-level/security-level) on the share. |
|
You can block write/create operations for a particular domain user by adding an extra ‘Deny’ ‘write’ acl for that user. (This issue occurs on the Windows 2008 client.) |
|
19552 |
When there is no data to replicate (for example, replication state is INSYNC), replication statistics might indicate a target is running out of disk space even though the target has enough space. |
|
This occurs because the replication process detected target space full condition when there is pending data to be replicated, but, at a later time, that pending data was removed and replication was insync. We do not query target disk state when replication is idle. On a similar note, we might not indicate target space full condition when there is no data to replicate as well. An error state in the replication statistics makes sense only when replication is not in sync. |
|
19485 |
Adding a host name does not work if you use a FQDN and the host name has letters in it. |
|
You can add names as long as the name is made only of numbers and it is not a FQDN where a period is used in the name string. |
|
19186 |
If you change the hostname or the domain name after setting up the DR Rapid plug-in, then you may get the wrong backup mode pass-through or de-dupe. |
|
Uninstall and then reinstall the DR Rapid plug-in for this information to be set correctly. |
|
18848 |
In the Internet Explorer 9 and 10 browsers, when you navigate to a DR Series system from within Global View, and then log out of that system and return to Global View, you are logged out of the machine running the Global View. |
|
This issue does not occur with any other supported browser. For browser information, see the Dell DR Series System Interoperability Guide. |
|
18178 |
The AIO-Stress tool fails when using Rapid NFS. |
|
Rapid NFS, which uses FUSE, does not support AIO. |
|
18501 |
Rapid NFS performance drops significantly with parallel NFS ingest from same client. |
|
When using Rapid NFS on your client, it is suggested that you do not run NFS from the same client to the DR Series system in parallel as this will affect your overall performance. |
|
18144 |
A File name too long error is displayed after trying to create a directory structure that exceeded 522 directories. |
|
The limit on a path within a mount point is 4096 bytes. |
|
18022 |
Windows 2008 and newer servers cannot assign local users (other than administrator) to Access Control Lists (ACLs). Windows 2008 and later does not query the local users on the DR Series platform. |
|
Assign ACLs to the built-in Administrator user on the DR Series platform if using Windows 2008 and later. |
|
17661 |
If the cable is removed from a network interface and the network is restarted, the interface does not get an IP. If you then reinsert the cable, you must restart the network to get an IP. |
|
Ensure that the interfaces that you want to add or modify are connected when making Advanced Networking changes. To restart the network, type network --restart at the CLI command line. |
|
17193 |
DR Rapid critical message Alert RDS Restore failed reported on DR4x00 system. In addition to the error, an event is generated internally in the DR Rapid plug-in when the read operation fails |
|
The DR Rapid plug-in generates events for any kind of read failures. |
|
16745, 17621 |
If you have the same client for OST and RDS operations and you manually update the client connections, unexpected messages are displayed as: [root@swsys-49 ~]# stats -- clients --type RDA RDA Client(s) Type plug-in OS Backup Software Last Access Connection(s) Mode r310-sys-39 RDS -- -- -- -- 0 Default
[root@swsys-49 ~]# ost -- update_client --name r310- sys-39 --mode auto Client is connected with default values. Please update to non-default values.
In Linux systems, the RDS plug-in installation fails if the OST plug-in is already installed in the system |
|
To work around the issue, use a different client for OST and RDS rather than sharing the same machine for both protocols. |
|
16660 |
When BE has an issue connecting to the server, it may not return detailed errors to the OST plug-in. |
|
See the client log files for the detailed information on the connection failure. |
|
16427 |
When upgrading your system using the iDRAC, if the upgrade package also contains new iDRAC firmware, the upgrade fails to complete. |
|
Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC. |
|
16053 |
After you install the Rapid CIFS plugin and replication operations are performed, you receive a blue screen and the following error: STOP 0x00000027 (parameter1, parameter2, parameter3, parameter4) RDR_FILE_SYSTEM |
|
This is a Microsoft bug that occurs on shared network resources on a computer that is running Windows Server 2008 R2 or Windows 7. To fix, see Microsoft Knowledge Base article 2584874. |
|
9433 |
Global hot spare is not automatically configured after replacing the GHS drive in slot 0. |
|
If the global hot spare is replaced, run maintenance by using the --make_standby command to make the drive a global hot spare. Contact Dell Technical Support for this action. |
|
24416 |
RM recovery errors when expansion enclosures are attached. |
|
Corrected in version 3.2. |
|
24134 |
Server signing reporting errors. |
|
Corrected in version 3.2. |
|
24081, 24080, 24079, 24047, 23676, 23252, 23229, 23067, 23016, 22710, 21455 |
Various RDCIFS stability improvements under heavy load. |
|
Addressed in version 3.2. |
|
23876, 21453 |
Eth speed may show value on unused interfaces. “N/A” is now shown for speed and duplex setting on unused interfaces. |
|
Corrected in version 3.2. |
|
23702 |
WAM2 fan improvements. |
|
Addressed in version 3.2. |
|
22581, 22478 |
DR2000v evaluation license errors in GUI. |
|
Corrected in version 3.2. |
|
22531 |
GUI refresh error “An error occurred while trying to retrieve Graph.” |
|
Corrected in version 3.2. |
|
22104 |
Likewise failed to start due to setname resolution issue. |
|
In this case, use the IP to avoid the error in code. |
|
22004 |
RDA improvements for OpDup handling. |
|
Addressed in version 3.2. |
|
21733, 19476, 18558 |
Improvements made in replication overwrite logic for large file workflows that append the file while being replicated. |
|
Addressed in version 3.2. |
|
21514 |
Issues with Global View when alternating between administrator and domain user. |
|
Corrected in version 3.2. |
|
20928, 21980 |
Cleaner error occurs on upgrading 1.X to 3.X. |
|
In version 3.2, the Cleaner now handles this condition without technical support intervention. |
|
20585, 20584, 20581,20466, 20465, 19200 |
Various security improvements. |
|
Addressed in version 3.2. |
|
20296 |
GUI would not accept CIFS password. |
|
Addition of special characters is now allowed in the user password field for CIFS in version 3.2. |
|
19849 |
Advanced networking shows gateways that are invalid |
|
Corrected in version 3.2. |
|
19214, 17141 |
Special characters may be accepted that prevent e-mail or fields in content dialog boxes from working. |
|
In version 3.2, these special characters are no longer allowed. |
|
14855 |
Option to hide or unhide a CIFS share |
|
Addressed in version 3.2. |
|
14700 |
VTL support for NDMP and iSCSI protocols. |
|
Addressed in version 3.2. |
|
14695 |
UPS power down details are now documented in the Dell DR Series Administrator’s Guide |
|
Addressed in version 3.2. |
|
22168 |
RDCIFS was listed as supported on Windows 2003 in the Dell DR Series System Interoperability Guide, but this is inaccurate. Windows 2003 does not support the command set required to support RDCIFS. |
|
Updated the Dell DR Series System Interoperability Guide for 3.1.2 to reflect the correct support of RDCIFS. |
|
22145 |
RDS OpDup was failing across the firewall as the TCP connection timed out during extended idle times. In this release, we have added keep alive on the RDS OpDup path connection. |
|
Corrected in version 3.1.2. |
|
21748 |
DR2000v FS was failing during boot on some legacy Intel and AMD processors. |
|
Corrected in version 3.1.2. |
|
20766 |
DR Series deployment using a static IP may come up in maintenance mode during initial boot as default IP is not being assigned. |
|
Corrected in version 3.1.2. |
|
21893 |
Bash Security Fix - BASH Remote Code Execution Vulnerability (ShellShock). |
|
Corrected in version 3.1.1. |
|
21873 |
During an upgrade from 2.x to 3.x under some unusual corner cases, the latest configuration database did not get backed up and tech support had to correct the database. |
|
Corrected in version 3.1.1. |
|
21765 |
System with in-sync replication would show pending bytes. |
|
Corrected in version 3.1.1. |
|
21690 |
During seeding, a network interruption caused failure of seeding. When deleting a container and attempting to reboot the system, the system entered Maintenance Mode. |
|
Corrected in version 3.1.1. |
|
21667, 21079, 21000 |
Slow performance occurred on noisy networks. |
|
Additional TCP options were enabled in the 3.1.1 release for more effective TCP error recovery. |
|
21601 |
A Perc issue occurred if the drive greater than 2TB sent a UnitAttention check condition to the Perc in descriptor format. This could cause the drive to be taken offline. |
|
Corrected in version 3.1.1 with new Perc firmware (21.3.0-0009). |
|
21538 |
Packet retransmissions may occur with replication packets. |
|
Customers should turn off Deep Packet Inspection on replication packets (especially port 9916), including GAV(gateway antivirus), IPS (Intrusion Prevention Service), Anti-Spyware, etc.
To deal with TCP retransmission issues, the following is a check list for troubleshooting packet retransmission on the Sonicwall side:
|
|
21468 |
If the IP address changed you could not modify a broken replication connection in the GUI. |
|
Corrected in version 3.1.1. |
|
21405 |
A Solaris client running made an invalid request to UDP which caused the DR to go into Maintenance Mode. |
|
Corrected in version 3.1.1. |
|
21382 |
Adding a machine to Global View did not work under some rare conditions due to invalid characters getting persisted into the config file. |
|
Corrected in version 3.1.1. |
|
21349 |
Replication Disconnect Alerts could occur during replication on slower LAN connections or noisy networks. A tunable parameter has been added (for tech support) that can be increased to remove the alert for transient failures. |
|
Corrected in version 3.1.1. |
|
21314, 21277, 21204 |
Replication race condition that could result in a core file on DR when using Veeam or SQL. |
|
Corrected in version 3.1.1. |
|
21181 |
In the GUI, after a successful registration, license registration details do not appear to be updated when you to try to edit and save registration details. |
|
Corrected in version 3.1.1. |
|
21075 |
After running advanced networking commands, the --show output displays incorrect MAC. |
|
Corrected in version 3.1. |
|
20177 |
Global View does not work if a group name contains the “$” character. |
|
Corrected in version 3.1. |
|
20832 |
The RDA plugin details tab displays as a plugin for Symantec OST. It should be updated to show as a plugin for NetVault. |
|
Corrected in version 3.1. |
|
20767, 18176 |
When a DR Series system is part of the Global View database and you change the DR Series system’s name by using the system --setname command (and not from the GUI), the new name is not reflected. |
|
Corrected in version 3.1. |
|
20763 |
System configuration screen displays DHCP although it is set to static. |
|
Corrected in version 3.1. |
|
20762, 20626 |
While performing recovery using USB, it is not possible to recover with the payload on the DR Series system. The payload on the USB is used; and, if the version on the USB is higher, the recovery process upgrades the DR Series system. The recovery process should use the payload on the DR Series system such that system is restored to the same version. |
|
Corrected in version 3.1.
Now, the recovery operation will only use the payload on the DR Series system. The reset operation will pick up the payload on the USB. |
|
20755 |
Extra entries are displayed in Global View after a hostname is changed for a managed unit. |
|
Corrected in version 3.1. |
|
20705 |
Need to enable DR2000v as replication target. |
|
Corrected in version 3.1. |
|
20689 |
Need to handle overwrites of old format blockmaps remaining after an upgrade to 3.x. |
|
Corrected in version 3.1. |
|
20627 |
Under certain conditions, “replication is disconnected” error occurs when running replication between two systems with no scheduling. |
|
Corrected in version 3.1. |
|
20565 |
After direct upgrade from 1.1.0.x or lower to 3.0.x, replication does not work if the upgrade occurred before the containers were in sync. |
|
Corrected in version 3.1. |
|
20284 |
Dell OpenManage Server Administrator contains a cross-site scripting vulnerability. |
|
Corrected in version 3.1.
Now, port 1311 used by Dell Open Manager is blocked. |
|
20067, 20036 |
DR Series system upgrade process may fail due to an error condition on the server LifeCycle Controller - Unified Server Configurator. |
|
These packages are optional in version 3.1, so if they fail to load it will not stop the unit from operating. |
|
20064 |
Incorrect or out of date statistics may be displayed when replication is stopped or a connection is disconnected in a cascaded replication. |
|
Corrected in version 3.1. |
|
19851 |
CIFS container paths display incorrectly with advanced networking. |
|
Corrected in version 3.1. |
|
19848 |
OST installer does not work with NBU 7.6 |
|
Corrected in version 3.1. |
|
19791, 19775 |
The incorrect IP address displays on the system configuration screen in the GUI. |
|
Corrected in version 3.1. |
|
19762 |
Add the ability to mount subdirectories. |
|
Added in version 3.1. |
|
19756 |
CLI Online Help shows “RDA” in a few places where it should show “RDS” |
|
Corrected in version 3.1. |
|
19655 |
smbd fix for unique corner case that causes a core |
|
Corrected in version 3.1. |
|
19614 |
Need to remove error reporting on the following errors: OST images not found and vRanger errors |
|
Corrected in version 3.1. |
|
19576 |
If you set up two bond interfaces with two different subnets but use the same static IP address, the configuration service fails. |
|
Corrected in version 3.1. |
|
19233 |
Need to clear the error, "file system is corrupt and please run consistency checker," after a system --init |
|
Corrected in version 3.1. |
|
19184 |
During container delete, cleaner does not start. |
|
Corrected in version 3.1. |
|
19091 |
Cannot collect diagnostics if an upgrade fails. |
|
Corrected in version 3.1.
Using the "diagnostics --start --service" command can start the diagnostic service if it is down after upgrade failure. Once the service is up, diagnostics can be collected. |
|
18833 |
The Reboot link is enabled after a DR Series system software upgrade. |
|
Corrected in version 3.1. The Reboot link is enabled during upgrade and has now been disabled during upgrade. It can be selected once the upgrade is complete. |
|
18742, 18629 |
With CIFS, backups are failing, with error "The specified network name is no longer available..." after upgrade. |
|
Corrected in version 3.1. |
|
18664 |
On the DR Series system log on page, if you enter an invalid user name, the Your password was not correct error displays. |
|
Corrected in version 3.1. The correct error message is now displayed. |
|
18661 |
If you power on a new MD1200 expansion enclosure (that is cabled in) while the base DR Series system is operational, the machine may go into maintenance mode with the following reason error code: One of the storage enclosure has become offline, please power-off the appliance, fix the connectivity issues and power-on the appliance. |
|
Corrected in version 3.1. |
|
18154 |
Include racadm in DR image so that the DRAC settings can be managed from inside of the OS instead of lifecycle controller. |
|
Corrected in version 3.1. |
|
18124 |
Ability to get encryption on OST replication op-dup traffic. |
|
Added in version 3.1. |
|
17586 |
After the DR Rapid device is created, you cannot change the number of streams supported for the device. |
|
Corrected in NVBU 10.0. |
|
17437 |
During a DR Rapid datacopy operation if optimized duplication-replication fails, a non-optimized replication is performed when the devices are available again. |
|
Corrected in version 3.1.1. |
|
17355 |
The Dell PowerVault MD1200 Expansion Shelf Setup Guide displays incorrect configurations for the DR Series system. |
|
Corrected in version 3.1. |
|
17076 |
The NetVault GUI crashes if the datacopy operation fails due to a network error. |
|
Corrected in NVBU 10.0. |
|
15573 |
Need to address potential vulnerability prone to cross-site scripting attacks. |
|
Corrected in version 3.1. |
|
15570 |
Need to disable SSLv2 on port 443. |
|
Corrected in version 3.1. |
|
13271 |
Ability to provide observable data on cleaner production |
|
Added in version 3.1. |
|
20111 |
Intermittent timeouts on OST backup, OST OPDUP replication and native DR replication. |
|
Corrected in the 3.0.0.2 release. |
|
19984, 19979 |
After upgrade to 3.0.0.1 some replication disconnection errors are seen. |
|
Corrected in the 3.0.0.2 release. |
|
19773 |
If you install the 3.0.0.1 RDA plugin from the DR Series system and then try to uninstall in Windows 2008 R2, you get an error. |
|
Corrected in the 3.0.0.2 release. |
|
19759 |
After creating or deleting a container, the CLI command stats --system and the GUI are not responding. |
|
Corrected in the 3.0.0.2 release. |
|
19491 |
Error occurs when replicating a large file (1 TB+) along with 10 million+ small files. Scatter_repl_io error under a very specific ingest pattern mixing very large and very small write operations. |
|
Corrected in the 3.0.0.2 release. |
|
19528, 8049 |
Cannot create a container starting with a number. |
|
Container names must start with a letter. Container names starting with a number are not supported. |
|
19250 |
When using the CLI to create a container, this container is created with a marker setting of none. |
|
If you are using a backup application that requires a marker, set the appropriate marker using the CLI command. If this is not done, then the savings level will not be optimal. You can set the marker in the GUI at the same time you are creating the container. |
|
19087 |
In daily statistics, we report that the compression savings is 0 percent. This is simply a reporting issue. |
|
This is correct behavior, as option has been removed from daily report. Use the following workaround to get the deduplication and compression percentage: Use stats --system or use Global View Savings (mouse over the Savings column). |
|
18857 |
When replicating between a large number of containers using a many to one relationship, some replication machines are displayed as Disconnected in the Peer Status screen. |
|
This is simply a display issue and the replications eventually go into an Online or Replicating status. |
|
18865 |
In some rare instances, changing the time and timezone at the same time caused the system to go into maintenance mode. |
|
Corrected in the 3.0.0.1 release. |
|
18833 |
The Reboot link is enabled after a DR Series system software upgrade. |
|
Corrected in the 3.1 release. The Reboot link is enabled during upgrade and has now been disabled during upgrade. It can be selected once the upgrade is complete. |
|
18664 |
On the DR Series system log on page, if you enter an invalid user name, the Your password was not correct error displays. |
|
Corrected in the 3.1 release. The correct error message is now displayed. |
|
18712 |
OST plug-in failure occurred using BE2010 and BE2012. |
|
Corrected in the 3.0.0.1 release. |
|
18706 |
Improve ingest performance during the cleaner compaction phase for situations in which ingest and cleaner are running at the same time. |
|
Corrected in the 3.0.0.1 release |
|
18540 |
The OST plug-in was not seen in the Windows Media server Add-Remove Programs. |
|
When you had multiple users for a Backup Exec server, they were able to run jobs while logged in as a different user. However, the only person that could see if the OST plug- ins were installed and what version was running, or were able to uninstall the plug-in, was the original user who was logged on when the plug-in was installed.
Corrected in the 3.0.0.1 release |
|
18453 |
The error message that resulted from executing the container -- delete --name [container_name] command when the container was not empty needed more information. |
|
Corrected in the 3.0.0.1 release |
|
18452 |
Update the GUI help menu to include other DR Series system documents in addition to the DR Series Admininistrator Guide. |
|
Corrected in the 3.0.0.1 release. |
|
18451 |
A wrong message displayed when you entered the wrong container name in the connection -- disable command. When you issued a connection -- disable --name [name of container that does not exist on the DR] --type OST the following message appeared: Failed to update connection entry - Container "use a container name that is not a container on the DR" is not configured with OST connection type. |
|
Corrected in the 3.0.0.1 release. The message more accurately describes the error condition. |
|
18393 |
When the machine was down or rebooted, the usage graph information was not collected and you saw a blank in the usage graphs upon reboot. |
|
Corrected in the 3.0.0.1 release. |
|
18375 |
When you widen the scope to over ten hours or more, the maximum CIFS connections reduced, and the usage graph statistical output was not accurate. |
|
Corrected in the 3.0.0.1 release. The graph now uses MAX aggregate instead of AVERAGE to calculate max values. This change was implemented for all graphs (not only for CIFS connections). |
|
18338 |
After naming a DR and successfully joining the domain, a Windows server within the domain using domain credentials could not access DR containers. DR containers are configured to allow access to that client; however, you could only access the container by using DR local administrator credentials. This was caused by you renaming the DR during configuration or changing the name in the GUI or CLI by issuing the #system --setname --name <with a name exceeding 15 characters>. |
|
When changing the DR host name, the GUI will display a message that no more than 15 characters are allowed as a host name. |
|
18325 |
When using Advanced Networking and configuring 2 bonds it showed the same host name for both IP addresses. |
|
Corrected in the 3.0.0.1 release. |
|
18275 |
After upgrading your system, backup jobs failed and containers became inaccessible due to the DR Series system leaving the domain. |
|
Corrected in the 3.0.0.1 release. |
|
18215 |
If you created a CIFS user named root or service, you could not delete it. |
|
Corrected in the 3.0.0.1 release. |
|
18151, 17997, 14534 |
Addition of additional DMA markers and changes to marker code for the DMAs that need marker detection.
The BridgeHead, Networker and Unix_Dump markers must be set explicitly on a container and are not part of the Auto marker option. |
|
Corrected in the 3.0.0.1 release. The Auto setting (default) will recognize markers for the 2.X supported DMACommVault|TSM| ARCserve|HP_DataProtector.
Newer Markers must be explicitly set using the appropriate selection BridgeHead, Networker or Unix_Dump. |
|
18070 |
The command -system – -- show --hardware | grep -i NIC does not list 1 Gb NICs if you have 10 Gb in the system. |
|
Corrected in the 3.0.0.1 release. |
|
18001 |
The - .bashrc is missing rda from the complete -F line. |
|
Corrected in the 3.0.0.1 release. |
|
17999 |
During a system upgrade, the software upgrade stopped because it exited the CLI shell. |
|
A message has been added instructing you to not interrupt the upgrade process. |
|
17863 |
After upgrading your system, you are prompted to reboot. The GUI will indicate that the reboot takes up to 10 minutes, which is the best case scenario. It can actually take up to 30 minutes, during which time your user interface can appear frozen. |
|
Corrected in the 3.0.0.1 release. |
|
17796 |
When the total number of Domain Controllers is very large, issues can occur when you try to add the machine to the domain. |
|
Corrected in the 3.0.0.1 release. |
|
17702 |
The RDS plug-in download page does not list the hybrid installer for the Windows operating system. It only lists the individual installers for the 32- bit and 64-bit platforms. |
|
Corrected in the 3.0.0.1 release. |
|
17672 |
You are unable to change default NetVault RDA password from the GUI when you use the system for the first time and no clients are connected. |
|
Corrected in the 3.0.0.1 release. |
|
17660 |
You get a platform not supported error when you upgrade the SUSE 11 NVBU plug-in from 32–bit to 64–bit on the same system. |
|
Corrected in the 3.0.0.1 release. |
|
17637 |
Ability to move the Integrated Dell Remote Access Controller (iDRAC) from the built-in device to the LOM devices. |
|
Use the command maintenance – remote_access –enable – device lomX. |
|
17586 |
After the RDA device is created, you cannot change the number of streams supported for the device. |
|
In release 3.1, for NVBU 10.0, this issue has been corrected. For NVBU 9.2, Tech Support has a process to change the streams. |
|
17622 |
In Linux systems, the RDS standalone plug-in uninstalled and removed shared libraries under oca-libs making RDA devices unusable on the NetVault Backup server.
If the RDS standalone package is uninstalled, NetVault Backup will stop working unless you install another RDA standalone package of different version or upgrade NVBU again (if new NVBU version is not present, upgrade to the same NVBU version already installed on the machine). |
|
Corrected in the 3.0.0.1 release. |
|
17440, 16835, 14516 |
Various browser issues.
You were unable to select a row properly in Chrome.
IE10 with Document Mode IE7 Standards did not display the Capacity chart.
Chrome displayed a Request unsuccessful message when you tried to fix a password issue in the wizard. |
|
Corrected in the 3.0.0.1 release. |
|
15609, 17349, 18558 |
Improvements on savings between SRC and TGT for some specific backup workflows. |
|
Corrected in the 3.0.0.1 release. |
|
15492 |
Would like the GUI to show savings factor on the dashboard in addition to just showing percentage savings. |
|
Corrected in the 3.0.0.1 release. |
|
15267 |
Improvements to the file system consistency checker for some rare corner case scenarios. |
|
Corrected in the 3.0.0.1 release. |
|
14727 |
Compression in the Best savings mode has been improved. |
|
Corrected in the 3.0.0.1 release. The Compression option has been removed from the GUI and is now modified by using the command line interface only. |
|
12362 |
If the unit was booted with only one PS and then a second PS was plugged in, the state was not shown as being changed. |
|
Corrected in the 3.0.0.1 release. |
|
8520 |
Make other documentation available by using the GUI Help menu. |
|
Additional documentation, such as the CLI and Interop guides, are now available in Help. |
|
8490 |
The usage graph legends were long and had similar colors, which could be confusing. |
|
Corrected in the 3.0.0.1 release. Filters have been added to allow you to choose one or more options to be shown. |
|
7041 |
You could not complete an NFS mount on a Solaris client. |
|
Corrected in the 3.0.0.1 release. |
|
18218 |
Under certain failure scenarios, the DR Series system entered maintenance mode every few minutes when using Auto markers. |
|
Corrected in the 2.1.0.2 release. |
|
18189 |
Intermittently during upgrade, certain firmware components reported the firmware version improperly. This caused the upgrade code to report a failure. |
|
Corrected in the 2.1.0.2 release. |
|
17821 |
Cannot configure an individual interface in the GUI. |
|
This is expected behavior; the CLI must be used for advanced networking operations. In release 2.1.0.1, the GUI was updated to prevent usage of Edit Interface when an interface is disabled. Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC. |
|
17820 |
ARCserve 16 support not documented in Dell DR Series System Interoperability Guide. |
|
Corrected in the 2.1.0.1 release. |
|
17791 |
“Warning: No loadable sections found in added symbol-file system-supplied DSO” error occurs when data deletion and the cleaner are running simultaneously. |
|
Corrected in the 2.1.0.1 release. Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC. |
|
17790 |
“Warning: No loadable sections found in added symbol-file system-supplied DSO” error occurs during deduplication. |
|
Corrected in the 2.1.0.1 release. Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC. |
|
17788 |
Restore Manager fails during init mode if Mac address changed. |
|
Corrected in the 2.1.0.1 release. Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC. |
|
17772 |
Backup Exec 2010 crashes in libstspidell.dll. |
|
Corrected in the 2.1.0.1 release. Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC. |
|
17766 |
“Program terminated with signal 6, Aborted” error occurs during replication. |
|
Corrected in the 2.1.0.1 release. Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC. |
|
17765 |
The alerts --email commands fail to write to the database. |
|
Corrected in the 2.1.0.1 release. Upgrade the DR code using the CLI or GUI using the normal network interface and not the iDRAC. |
|
17515 |
The command stats --clients --type does not work in the CLI. |
|
Corrected in the 2.1.0.1 release. |
|
17329 |
Correct the race condition in monitoring the subsystem that can place the unit in maintenance mode. |
|
Corrected in the 2.1 release. Race condition is identified. |
|
17371 |
There is an error with the web server response code under a special condition. |
|
Corrected in the 2.1 release. |
|
14751 |
The UI can sometimes show all the interfaces at 10 G or 1 G specification depending on the network ports that are connected and active. |
|
Corrected in the 2.1 release. This interface is redesigned. |
|
17315 |
SMBD core in security inheritance handling on upgraded container. |
|
Corrected in the 2.1 release. |
|
17226 |
The GUI wizard displays an error when configuring static IP. |
|
Corrected in the 2.1 release. |
|
17216 |
Security SSL is updated. |
|
Corrected in the 2.1 release. |
|
17070 |
HP Data Protector Marker support is added. |
|
Corrected in the 2.1 release. |
|
10552 |
The GUI and CLI must allow the user to see the files that are getting replicated. |
|
Corrected in the 1.1 release. Added active files tables to the statistics container pages. |
|
15758 |
Ability to edit the hosts file using the CLI. |
|
Corrected in the 2.1 release. Provided a method to update the hosts file via the CLI using the network --host --add command. |
|
15908 |
All 6 interfaces for 1G option on the DR4100 system are not shown in GUI. |
|
Corrected in the 2.1 release. All interfaces are now displayed in the GUI for various configuration options. |
|
15943 |
The contact information does not display in the GUI after the submit button is clicked if mail relay host is not configured. |
|
Corrected in the 2.1 release. Corrected the logic to not send the notification if the email relay host is not set. |
|
15947 |
The wrong error message is displayed when removing all the NTP servers from the GUI. |
|
Corrected in the 2.1 release. |
|
16262 |
A wrong command syntax is seen for the ost --limit command |
|
Corrected in the 2.1 release. |
|
16322 |
For better support capability, ocafsd dumps on diagnostics must be allowed. |
|
Corrected in the 2.1 release. |
|
16515 |
Pending bytes for replication must be displayed. |
|
Corrected in the 2.1 release. Provided pending bytes in the stats --replication output. |
|
16516 |
Extracting stack trace in the diagnostics bundle functionality must be added for better support diagnostics. |
|
Corrected in the 2.1 release. The functionality has been added to the diagnostic gathering routine. |
|
16916 |
Replication fails due to the firewall packet inspection and modification. |
|
Corrected in the 2.1 release. Added replication checksum to all packets. The firewall vendor can be engaged if necessary to modify inspection parameters for replication traffic. |
|
16963 |
Functionality required to change the behavior on update to disable the root user if it is enabled. |
|
During any upgrade, the root user login is disabled (if it is enabled) which is an interface only Technical Support uses. |
|
17167 |
The title in a few of the disk usage graphs must be made consistent with the others. |
|
Corrected in the 2.1 release. |
|
17184 |
Cannot install the BUE 32–bit plugin. |
|
Corrected in the 2.1 release. |
|
10849, 11520, 11636, 7752, 14892, 15297, 15667, 15945 |
Required support for Advanced Networking feature to allow configuration of multiple networks on a single unit. |
|
Corrected in the 2.1 release. |
|
14228, 16165 |
Service mode ocafsck reports only the first error in that stream. |
|
Corrected in the 2.1 release. Improved the ocadsck logic to report all errors that occur in a stream. |
|
15058, 15956 |
FS cache modifications and improvements are required. |
|
Corrected in the 2.1 release. |
|
15967, 16005 |
The core directories are not cleaned up after the diagnostic cleanup routine. |
|
Corrected in the 2.1 release. |
|
16441, 17067 |
On a specific container, replication appears to stop at 99 percent and then restarts. |
|
Corrected in the 2.1 release. Corrected the race condition in the code that caused the issue. |
|
16707, 13296 |
Unable to add a domain name that contains an underscore. |
|
Corrected in the 2.1 release. |
|
16937, 16904, 16806 |
Replication fails in a specific scenario when trying to decompress a file created in 1.x and replicated in 2.x. |
|
Corrected in the 2.1 release. Resolved the issue in the decompression logic that caused the issue. |
|
7752, 14697, 15925 |
Advanced Networking support replication over other interfaces required. |
|
Corrected in the 2.1 release. Support for Advanced Networking feature to allow configuration of multiple networks on a single unit. |
|
16144 |
Critical event shows "Datacheck detected potential namespace inconsistency. Run file system scan as soon as possible." |
Maintenance mode alarm falsely triggered due to code returning enoent instead of ebusy. |
Corrected in the 2.1 release. |
|
16679 |
File system stat call consumes more cycles than expected. |
Performance enhancement for file system stat call. |
Corrected in the 2.1 release. |
|
16670 |
Deduplication failure in a specific ingest workflow. |
Failure during inline deduplication when accessing many offsets. This results in a system core. |
Corrected in the 2.0.1.1 release. |
|
16655/16486 |
Relay server does not work when using an IP instead of a name. |
When setting the relay server you were limited to using only its name. |
Corrected in the 2.0.1.1 and 2.1 releases, respectively. You can now use a name, IP or FQDN. |
|
16498 |
32-bit OST plugin for NBU is missing from 2.0.1.0 build. GUI URL pointing to 64-bit plugin. |
When using release 2.0.1.0, the 32-bit OST plugin is missing. The URL for this plugin points to the 64-bit version. |
Corrected in the 2.1 release. You now have access to both plugins. |
|
16425 |
GUI incorrectly displaying DNS suffix as none. |
GUI incorrectly displaying DNS suffix as none. In the CLI this is displayed correctly. |
Corrected the issue in the script file that was parsing this information. |
|
16420 |
Unable to install plugin on specific 32-bit Windows2013 NBU server. |
Was unable to install a new driver over the top of an existing driver in some cases. |
Corrected in the 2.1 release with updates to the package installer. |
|
16381 |
Cleanup of log file messages referencing sdb5. |
In some situations, lots of messages were added to the log files. |
Corrected in the 2.1 release. |
|
16247 |
scatter_repl_io time out experienced during replication. |
During replication, the system showed a scatter_repl_io error. |
Corrected the issue in the replication code. |
|
16426 |
After upgrade from 1.x to 2.x, the GUI prompted for reboot but reboot did not occur on the first try. |
When upgrading from 1.x to 2.x from the UI, the reboot does not appear to reboot the system. |
Before clicking the reboot button in the UI, refresh the browser and to resolve the issue.
You can also do the upgrade from the CLI if you wish to work around this issue. |
|
16083 |
Dell DR4100 system comes up in an error state due to additional power supply sensors that are discovered with newer iDRAC firmware. |
This was caused by a new version of the iDRAC firmware which discovered additional sensors. |
Corrected the issue in the Hardware Monitor code. |
|
15795 |
There is no message instructing user to upgrade the Client OST plugin when DR4X00 FW is upgraded. |
Added messaging to the UI so that during the upgrade the user is told to also upgrade the OST plugin if OST is being used. |
Added messaging to inform the user to upgrade the plug also. |
|
15695 |
GUI "Usage" page doesn't show any stats graphs in a special case. |
If the client machine and the DR are not in the same time zone, then the usage graphs may not show the stats for some period. |
We now use the time zone of the server rather than the client running the browser. |
|
15275 |
Windows OST plug-in install fails on a DC. |
Installing the OST plug-in on a DC fails. |
The code now supports this option. |
|
15067 |
Handle the ‘.’ as part of the NETBIOS name. |
Domain join to the AD domain controller is ok but access to DR4000 share fails. Handle/allow '.' in NETBIOS name.
Access from windows client using test.com\administrator.
smb.conf: workgroup = TEST.COM realm = ad.test.com administrator@swsys-84 > authenticate --show Domain: ad.test.com Login group: test.com\domain users administrator@swsys-84 > |
Corrected the code path to allow '.' for domain login groups. |
|
14959 |
System did not come to operational state after upgrade due hardware monitor failing to start. |
Intermittently after an upgrade the unit does not come into an operational state and remained in maintenance mode. |
Added code to check the status of the SNMPD before starting the hardware monitor which resolves this issue. |
|
14957 |
Support bundles can be large. We need to support options to gather more specific info in these special situations. |
Add following new options for diagnostics collection.
|
• |
--logs — Collect only logs and system configuration. |
The auto_diags option is hidden since this is a very special use case. |
diagnostics --help collect Usage:
|
|
14949 |
CLI expansion license was showing up as “In Use: No” even though the expansion license was installed. |
Corrected the CLI command system --show --license –verbose to display the license in the correct state. |
|
|
14897 |
OST limiter throughput below the set value. |
The throttling speed limits that can be set using the DR Series system CLI commands (replication --limit --speed) would not match the set replication bandwidth limits. |
Corrected some minor issues with the OST limits to correct this issue. |
|
14889 |
Add the option to the CLI to show if the SNMP Trap’s email is on or off. |
Added additional option to alerts --show –email command.
|
Added additional option to alerts --show –email command to show status of Trap’s e-mail. |
|
14845 |
system --upgrade command fails with an error message:Upgrade image not found. |
After replacing a hardware CRU or FRU, the DR may come up in support mode with a request to upgrade the hardware. |
The GUI and CLI now place the uploaded SW package into the same directory so upon HW replacement this same image can be utilized to upgrade the new component when necessary with no special user action required. |
|
14724 |
Replication speed limits not throttling as expected. |
The throttling speed limits that can be set using the DR Series system CLI commands (replication --limit --speed) would not match the set replication bandwidth limits. |
Corrected some minor issues with the replication limits to address this issue. |
|
13537 |
Dell DR4100 system enclosure hot add fails in Release 2.0. |
Attempting to perform a "hot add" of an external expansion shelf enclosure in a DR4000 or DR4100 system fails because this is not a supported method of operation in the 2.0 product release. To prevent this error/failure condition from occurring, observe the following best practice:
Ensure that before an external expansion shelf enclosure is cabled to and powered on to a Release 2.0 DR4000 or DR4100 system only after the DR Series system has been powered down. |
The workaround is to observe the following best practice for connecting an external expansion shelf enclosure to a Release 2.0 DR4000 or DR4100 system:
|
|
13580 |
User intervention is required when booting up a system that was rebooted due to a shelf going offline. |
This condition can occur when an external expansion shelf enclosure goes offline, which requires that the DR Series system be rebooted. During the DR Series system boot up, it halts in the PowerEdge RAID Controller (PERC) H800 configuration process, and prompts you to press <F> to import the Foreign Disks. |
To resolve this issue, press <F> to import the Foreign Disks, and allow the boot up process for the DR Series system to complete and boot normally. Once the process completes normally, the DR Series system will come up, and enter its Operational mode. |
|
13790 |
DR Series system performance drops when background initialization runs on an external expansion shelf. |
Whenever an external expansion shelf enclosure is added to the DR Series system, this causes a one-time only impact to the DR Series system performance.
The impact is a result of the background initialization (BGI) process running for an external expansion shelf (the system RAID disks require such initialization).
BGI can take approximately 2 hours for a 3 Terabyte (TB) external expansion shelf enclosure to complete. |
There is no workaround for BGI. This is a one-time only process that occurs when an external expansion shelf enclosure is added.
During BGI that is associated with the addition of an external expansion shelf enclosure, you should expect that performance for the DR Series system will be slower than usual. |
|
14126 |
Do not connect an external expansion shelf enclosure to a DR Series system prior to upgrading to the 2.0 release. |
System issues occur if any DR4000 systems running the pre-2.0 release system software connect and power on any external expansion shelf enclosure, and then upgrade to the DR Series system 2.0 release software. To prevent this condition, observe the following best practice:
|
To resolve this issue, observe the following best practice for upgrading earlier DR4000 systems to the 2.0 release software (this must be done prior to connecting and powering on an external expansion shelf enclosure):
|
|
14427 |
The Google Chrome browser reports that the upgrade page is unresponsive during a file upload. |
The Google Chrome browser displays a Page(s) Unresponsive dialog, which indicates it is in a "waiting" mode when uploading the DR4000 system software payload needed for the upgrade. The Page(s) Unresponsive dialog allows only two options:
|
There is no workaround at this time. Dell recommends that you click Wait and allow sufficient time for the uploading of the DR4000 system software upgrade to complete. |
|
14895 |
Restore Manager needs to add a message to remove the USB key after the operating system installation completes. |
The USB key used during the Dell DR Restore Manager operating system installation process can be overwritten if it is not removed after successfully installing the operating system. |
To prevent the overwriting of the USB key, when the operating system installation is successful, it is recommended that you observe the following best practices:
|
|
14920 |
Kernel panic due to soft lockup after killing power to the enclosure. |
A softlock error condition can occur if an active data ingest is in progress and any active external expansion shelf enclosure loses both of its power supplies.
Because an error associated with inflight write data is detected, the DR Series system performs a "kernel panic" and reboots.
During the reboot, if the external expansion shelf enclosure was already powered on and there was active inflight data in the PERC controller cache, the DR Series system remains in the BIOS window. |
The workaround to resolve this issue is to perform the following:
|
