Dell DR Series System Release Notes for Version 3.2.0.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Release notes.............................................................................................................................. 4 Upgrade notes.......................................................................................................................................................... 4 Checking system information...................................................................................................................................
Release notes 1 These Release Notes are intended to supplement the Dell DR Series system documentation to provide last minute information available for the current release of the DR Series system software. For a complete list of available DR Series system documentation, see the topic, “Other Information You May Need,” at the end of these Release Notes.
3. Click View All Drivers. 4. Confirm that you have the correct product to begin the search for all the related drivers, software, and firmware. For information about how to check the current version of the DR Series system software installed, see the Dell DR Series System Administrator Guide or the Dell DR Series System Command Line Reference Guide at dell.com/support/ home.
a. Create registry key HKLM\SOFTWARE\\Dell\\RDA\RdaOpdupRetries of type DWORD, and assign a value that is equal to the number of retries. b. Start duplication, and run the command, tcpkill, for the opdup connection multiple times to verify the retry. For Unix: • a. Stop the NetVault service. b. Export "OCA_RDA_OPDUP_RETRIES" by setting it to the desired number of retries. c. Start the NetVault service. d.
a. The Standard STK L700 library with 10 Ultrium 3850 LTO4 drives b. An OEM – Dell version of the same library. Each library will be initially instantiated with 10 tapes of either of the following tapes sizes 10GB, 50GB, 100GB, 200GB, 400GB and 800GB. Additional capability is provided to append new media (tapes) as required. • Support for NDMP and iSCSI backup protocols for VTLs — VTLs can be accessed by either NDMP or iSCSI protocols.
Open issues The following table lists the open issues in the current release. ID Issue Workaround 27538 Secure connection error occurs in Firefox when navigating to the DR Series system page: "Error code: sec_error_reused_issuer_and_serial" Delete your old exception and use temporary exceptions for subsequent visits to the DR Series system page. To delete your old exception: 1. In the Firefox window, click the button and then click .
ID Issue Workaround Do you want to continue with the installation of [y,n,?]y 24597 CIFS usage graph shows that there are CIFS writes, when running iSCSI I/O only. The stats reported on the iSCSI graph are accurate. Due to a bug false stats getting reported on the CIFS chart which can be ignored. This issue will be fixed in the upcoming 3.2 hot-fix.
Known issues and resolutions The following table lists known issues and the related resolutions for the current DR Series system release. ID Issue Resolution 28032 The DR4000 crashes when breaking a replication relationship and running fsck. This issue has been addressed in 3.2.0.2. 27847 RDNFS plugin issue with Oracle Linux 7.0. This issue has been addressed in 3.2.0.2. 27736, 27671 Replication fix for large configurations. This issue has been addressed in 3.2.0.2.
ID Issue Description Workaround/Solution 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.
ID Issue Description Workaround/Solution 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.
ID Issue 20456 Installation of SSL Certificate file in the GUI failed on Internet Explorer (IE) when using Remote Desktop. Description Workaround/Solution 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. 1. Under Internet Options > Security, in the "Internet" or "Intranet" area, click Custom Level.
ID Issue Description Workaround/Solution 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.
ID Issue Description Workaround/Solution 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.
ID Issue 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.
ID Issue Description Workaround/Solution 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.
ID Issue Description Workaround/Solution 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.
ID Issue Description Workaround/Solution Ethernet tab. Scroll to the bottom of the page and enter the desired MTU size. • SonicOS Standard: Click Network -> Settings -> Ethernet Tab. • SonicOS Enhanced: Click Network -> Interfaces. Click the Configure icon next to the WAN interface. Click the Advanced tab. NOTE: It is recommended to check the 'Fragment outbound packets larger than WAN MTU' if the MTU is set below the default of 1500. Use the 'Update' button to process the changes entered.
ID Issue Description Workaround/Solution 7. Check the upstream device configuration. 8. Check for the NAT Traversal option. 9. On the computer where GVC is installed, make sure the NAT Traversal option is disabled under Connection Properties --> Peers --> Edit --> NAT - Traversal. 21468 If the IP address changed you could not modify a broken replication connection in the GUI. Corrected in version 3.1.1.
ID Issue Description Workaround/Solution 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.
ID Issue Description Workaround/Solution 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.
ID Issue Description Workaround/Solution 18124 Ability to get encryption on OST replication opdup 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 nonoptimized replication is performed when the devices are available again. Corrected in version 3.1.1.
ID Issue Description Workaround/Solution 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.
ID Issue Description Workaround/Solution 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.
ID Issue 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.
ID Issue Description Workaround/Solution 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.
ID Issue 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.
ID Issue Description Workaround/Solution 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.
ID Issue 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.
ID Issue Description Workaround/Solution 15297, 15667, 15945 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.
ID Issue Description Workaround/Solution 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 Corrected in the 2.1 release. 2.0.1.0, the 32-bit OST You now have access to both plugin is missing. The URL plugins. for this plugin points to the 64-bit version. 16425 GUI incorrectly displaying DNS suffix as none. GUI incorrectly displaying Corrected the issue in the DNS suffix as none.
ID Issue Description Workaround/Solution 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. Corrected the code path to allow '.' for domain login groups. Access from windows client using test.com \administrator. smb.conf: workgroup = TEST.COM realm = ad.test.
ID Issue Description Workaround/Solution 14949 CLI expansion license was showing up as “In Use: Corrected the CLI No” even though the expansion license was command system -show --license – installed. verbose to display the license in the correct state. 14897 OST limiter throughput below the set value. The throttling speed limits Corrected some minor issues that can be set using the with the OST limits to correct DR Series system CLI this issue.
ID Issue Description Workaround/Solution 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: external expansion shelf enclosure to a Release 2.0 DR4000 or DR4100 system: • • Ensure that before an external expansion shelf • enclosure is cabled to and powered on to a Release 2.
ID Issue Description Workaround/Solution expansion shelf enclosure to complete. 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.
ID 14920 Issue Description Workaround/Solution process can be overwritten if it is not removed after successfully installing the operating system. recommended that you observe the following best practices: Kernel panic due to soft lockup after killing power A softlock error condition to the enclosure. can occur if an active data ingest is in progress and any active external expansion shelf enclosure loses both of its power supplies.
2 Third party components This product contains the third-party components listed below. For third-party license information, go to http:// software.dell.com/legal/license-agreements.aspx. Source code for some components can be found at http://opensource.dell.com. Copyright notices can be found below at Copyright Notices . Component License Notes keyutils utility 1.2.1.el5 GPL (GNU General Public License) 2.0 A copy of the license can be found below at GNU (Lesser General Public License) 3.
GPL (GNU General Public License) 2.0 GNU GENERAL PUBLIC LICENSE VERSION 2 Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it.
disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2.
of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11.
Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. [signature of Ty Coon], 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library.
TERMS AND CONDITIONS 0. Definitions "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations.
unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.
6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b.
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read [http:// www.gnu.org/philosophy/why-not-lgpl.html]. GNU (Lesser General Public License) 3.
4. a. Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License. b. Accompany the object code with a copy of the GNU GPL and this license document. Combined Works.
Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation. If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used.
Copyright Notices Components libtalloc2 utility Copyright (C) Andrew Tridgell 2004-2005 Copyright (C) Stefan Metzmacher 2006 Copyright (C) Jelmer Vernooij 2008 Libxml2 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. Copyright (C) 2000 Gary Pennington and Daniel Veillard. Copyright 1991 by the Massachusetts Institute of Technology Copyright (C) 2000 Bjorn Reese and Daniel Veillard.
Components Copyright (C) 2010 Nicholas A. Bellinger Copyright (C) 2011 Alexander Nezhinsky Copyright (C) 2010 FUJITA Tomonori Copyright (C) 2013 Nippon Telegraph and Telephone Corporation. Copyright (C) 2011 Alexander Nezhinsky Copyright (C) 2007 Davide Libenzi Copyright (C) 2013 Dan Lambright Copyright (C) 2006-2007 FUJITA Tomonori
Components (C) Martin Pool 2002 Copyright (C) Jelmer Vernooij 2002 Copyright (C) James J Myers 2003 Copyright (C) Stefan (metze) Metzmacher 2004 Copyright (C) Andrew Tridgell 1998 Copyright (C) Andrew Tridgell 1992-2003 Copyright (C) James J Myers 2003 Copyright (C) Andrew Tridgell 2003 Copyright (C) James J Myers 2003 Copyright (C) Andrew Tridgell 1992-2005 Copyright (C) James J Myers 2003
Getting help 3 Other information you may need WARNING: The following table lists the documentation available for the Dell DR Series systems. The documentation listed is available at dell.com/support/home by browsing and selecting your specific DR Series system. For more information about DR Series system hardware, see the safety and regulatory information that shipped with your DR Series system. Warranty information might be included as a separate document.
Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer-service issues, go to dell.com/support. Locating Service Tag of your system Your system is identified by a unique Express Service Code and Service Tag number. The Express Service Code and Service Tag are found on the front of the system by pulling out the information tag. Alternatively, the information may be on a sticker on the chassis of the system.
