サポートと今すぐチャット
サポートとのチャット

DR Series Software 3.2.0.2 - Release Notes

Resolutions for earlier releases

Resolutions for earlier releases

The following table lists known issues, descriptions, and related solutions or workarounds for earlier releases of the DR Series system.

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.

2.
In the Security settings, scroll down to Include local directory path when uploading files to a server and ensure it is not selected.
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.
—cores —Collect only cores
--auto_diags <#> — Collect only specified number of previous auto diagnostics.
--tcp_dump— Collect tcp dump report.

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:

2.
Click Wait.

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:

Third party components

Third party components

This product contains the third-party components listed below. For third-party license information, go to http://quest.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.0

libtalloc2 2.0.8.24.1

GPL (GNU General Public License) 3.0

A copy of the license can be found below at GNU (Lesser General Public License) 3.0

libsigc++20 2.2.4.2.1.el6

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GNU (Lesser General Public License) 3.0

libxml++ 2.30.0.1.el6

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GPL (GNU General Public License) 2.0

Linux SCSI target framework

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GPL (GNU General Public License) 2.0

mhVTL

GPL (GNU General Public License) 2.0

A copy of the license can be found below at GPL (GNU General Public License) 2.0

OpenSSL 1.0.1e

OpenSSL License

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)

A copy of the license can be found below at Open SSL License

Samba 3.5

GPL (GNU General Public License) 3.0

A copy of the license can be found below at GNU (General Public License) 3.0

Xmlsec1 2.12.8.el6

MIT

A copy of the license can be found below at The MIT License (MIT)

xmlsec1-openssl 2.12.8.el6

OpenSSL License

A copy of the license can be found below at Open SSL License

GPL (GNU General Public License) 2.0

GPL (GNU General Public License) 2.0

GNU GENERAL PUBLIC LICENSE VERSION 2

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. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

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.

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) 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.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

NO WARRANTY

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

[one line to give the program's name and a brief idea of what it does.] Copyright (C) [year] [name of author]

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author

Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.

This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

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. If this is what you want to do, use the GNU Lesser General Public License instead of this License.

GNU (General Public License) 3.0

GNU (General Public License) 3.0

Copyright (C) 2007 Free Software Foundation, Inc. [http://fsf.org/] Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.

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.

To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.

A "covered work" means either the unmodified Program or a work based on the Program.

To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.

To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.

The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.

A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.

The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the 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. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.

No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.

You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

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 separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.

A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.

"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

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.

Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

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.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version".

A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.

In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.

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 of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.

A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.

If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.

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.

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

[one line to give the program's name and a brief idea of what it does.] Copyright (C) [year] [name of author]

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see [http://www.gnu.org/licenses/].

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

[program] Copyright (C) [year] [name of author] This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box".

You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see [http://www.gnu.org/licenses/].

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].

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択