Release Notes

Dell EMC Data Domain® Operating System

Version 6.0.2.40

Release Notes
302-005-491
REV 02
March 2019

Always check the support site for the latest revision of this document before
proceeding. Any printed version of this document may be out of date.
Suggestions from users help to improve the accuracy, organization, and overall quality
of our publications. Send feedback of this document to [email protected].
l Revisions................................................................................................................ 2
l Product description................................................................................................ 2
l New features in DD OS 6.0..................................................................................... 2
l Command changes................................................................................................. 8
l Fixed issues.......................................................................................................... 22
l Known issues and limitations.................................................................................67
l Environment and system requirements................................................................. 72
l Software media, organization, and files.................................................................73
l Install and upgrade................................................................................................75
l Additional Resources............................................................................................ 83
Release Notes

Revisions
Table 1 Publication history

Revision Date Description

Rev 02 March 2019 Added fixed platform issue 227463 (CVE-2018-3180)

Rev 01 February 2019 Initial publication.

Product description
Learn about Data Domain Operating System.
The Data Domain Operating System (DD OS) is the intelligence that powers Data
Domain. It provides the agility, security and reliability that enables the Data Domain
platform to deliver scalable, high-speed, and cloud-enabled protection storage for
backup and archive.

New features in DD OS 6.0

This version of DD OS offers new systems and software enhancements.

New in DD OS 6.0.2.0
The following clarifications apply to DD OS 6.0.2.0:
Replication with High Availability (HA):
Over IP networks, HA systems use a floating IP address to provide data access to the
Data Domain HA pair, regardless of which physical node is the active node. The net
config command provides the [type {fixed | floating}] option to configure
a floating IP address. The Data Domain Operating System Command Reference Guide
provides more information.
If a domain name is needed to access the floating IP address, specify the HA system
name as the domain name. Run the ha status command to locate the HA system
name.

Note

Run the net show hostname type ha-system command to display the HA
system name, and if required, run the net set hostname ha-system command to
change the HA system name.

All file system access should be through the floating IP address. When configuring
backup and replication operations on an HA pair, always specify the floating IP address
as the IP address for the Data Domain system. Data Domain features such as DD
Boost and replication will accept the floating IP address for the HA pair the same way
as they accept the system IP address for a non-HA system.
Replication is supported between HA and non-HA systems. The "Replication between
HA and non-HA systems" section of the Data Domain Operating System Administration
Guide provides additional information about the supported ways to manage replication
between HA and non-HA systems.

2 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

New features in DD OS 6.0.1

DD OS 6.0.1 modernizes data protection through new cloud capabilities and expanded
advanced integration with backup and Big Data applications.
DD Cloud Tier/DD System Manager feature enhancements include:
l Amazon Web Services (AWS) Signature Version 4 request signing support for DD
Cloud Tier
l Support for new AWS regions -- China region is not supported
l Enhancements to DD Cloud Tier resiliency
l DD System Manager enhancements, including support for DD Cloud Tier file recall
Other enhancements for DD OS 6.0.1 include:
l Protection Storage Appliance
l Protection Storage Everywhere -- DD VE certification with vSphere 6.0 P03
l DD Management Center performance enhancements

New features in DD OS 6.0

DD OS 6.0 modernizes data protection through new cloud capabilities and expanded
advanced integration with backup and Big Data applications.
l Natively tier deduplicated data directly from Data Domain to the public, private or
hybrid cloud for efficient long-term retention with Data Domain Cloud Tier.
l Increased security for private cloud and service providers through secure multi-
tenancy enhancements.
l Expand the benefits of DD Boost to new workloads and partners including Big Data
applications.
l Included random I/O optimizations provide improved performance for applications
and use cases that generate larger amounts of random read and write operations
than sequential read and write operations.
l Metadata on Flash (MDoF) creates caches for file system metadata using flash
technologies.

Hardware Enhancements
The Data Domain Operating System (DD OS) 6.0 release introduces no new hardware.

FS15 SSD shelf

This release introduces an SSD storage shelf, the model FS15.
l The FS15 supports 2, 5, 8, or 15 SSD drives
l A FS15 shelf is part of the new high-end DD9800 and can be added to systems
running DD OS 6.0

DD6300
The new DD6300 system includes the following features:
l 2 Intel EP processors (Model: E5-2620v3)
l AIO memory configurations

New features in DD OS 6.0.1 3

Release Notes

n Systems with 48 GB of memory installed support up to.1 x 4-TB shelves, adding

up to 84 TB of total usable capacity (36 internal and 48 external).
n Systems with 96 GB of memory installed support up to 6 x 2-TB or 4 x 3-TB or
3 x 4-TB shelves, adding up to 180 TB of total usable external capacity (36
internal and 144 external).
l AIO memory configurations using 7200 RPM SAS HDD
n Base: 7 x 4TB HDDs, 16 TB usable.
n Factory expanded: 12 x 4TB HDDs, 36 TB usable.
n Base upgrade: 7 x 4TB HDDs + 5 x 4TB HDDs, 28 TB usable.
l Performance up to 24.6 TB/hr for aggregate writes using DD Boost.
l Performance up to 7.5 TB/hr for aggregate writes using CIFS.
l Increased stream counts for backup and archiving workloads:
n Up to 270 concurrent backup write streams.
n Up to 75 concurrent backup read streams.
n Up to 270 destination replication streams.
n Up to 150 source replication streams.
l 6 system fans, 5 + 1 redundant
l 2 hot-swappable power units, 1 +1 redundant

DD6800
The new DD6800 system includes the following features:
l 2 Intel EP processors (model E5-2630v3)
l Supports 192 GB memory configuration
n Systems with 192 GB of memory installed support up to.6 x 2-TB or 4 x 3-TB or
3 x 4-TB shelves, adding up to 144 TB of usable external capacity.
n Systems with expansion kit installed (2 additional data cache SSDs), support
up to 12 x 2-TB or 8 x 3-TB or 6 x 4-TB shelves, adding up to 288 TB of usable
external capacity.
n Systems with with Data Domain Extended Retention software have 192 GB of
memory installed and support up to 16 ES30 (each with 15 x 3-TB drives)
shelves adding up to a maximum of 576 TB of usable external capacity.
n Systems enabled with DD Cloud Tier have 192 GB of memory installed and
support up to 576 TB of usable cloud storage.
n 192 GB is required for DD Cloud Tier and Extended Retention. (Split the HA
line, mutually exclusion ER.)
n HA is supported with both memory configurations.
l Performance up to 33.1 TB/hr for aggregate writes using DD Boost.
l Performance up to 9.5 TB/hr for aggregate writes using CIFS.
l Increased stream counts for backup and archiving workloads:
n Up to 400 concurrent backup write streams.
n Up to 110 concurrent backup read streams.
n Up to 400 destination replication streams.

4 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

n Up to 220 source replication streams.

l 6 system fans, 5 + 1 redundant
l 2 hot-swappable power units, 1 +1 redundant

DD9300
The new DD9300 system includes the following features:
l 2 Intel EP processors (model E5-2680v3)
l Supports 192 GB and 384 GB memory configurations
n Systems with 192 GB of memory installed support up to 16 x 2-TB or 8 x 4-TB
shelves, adding up to 384 TB of usable external capacity.
n Systems with 384 GB of memory installed support up to 20 x 3-TB or 15 x 4-TB
shelves adding up to 720 TB of usable external capacity.
n Systems with Data Domain Extended Retention software have 384 GB of
memory installed and support up to 28 ES30 (four strings of 7 ES30 and each
with 15 x 3-TB drives) shelves adding up to a maximum of 1,008TB or 10
DS60-180 (each with 60 x 3-TB drives) shelves adding up to maximum of 1,440
TB of usable external capacity.
n Systems enabled with DD Cloud Tier have 384 GB of memory installed and
support up to 1,440 TB of usable cloud storage.
n 384 GB is required for DD Cloud Tier and Extended Retention (ER). (Split the
HA line, mutually exclusion ER.)
n HA is supported with both memory configurations.
l Performance up to 41.2 TB/hr for aggregate writes using DD Boost.
l Performance up to 15 TB/hr for aggregate writes using CIFS.
l Increased stream counts for backup and archiving workloads:
n Up to 800 concurrent backup write streams.
n Up to 220 concurrent backup read streams.
n Up to 800 destination replication streams.
n Up to 440 source replication streams.
l 6 system fans, 5 + 1 redundant.
l 2 hot-swappable power units, 1 +1 redundant.

DD9800 system
The new high-end DD9800 system includes the following features:
l 4 Intel EX processors.
l SSD storage shelf, cache tier.
l Supports 256GB and 768GB memory configurations
n Systems with 256 GB of memory installed support up to 21 x 2-TB or 14 x 3-TB
shelves, adding up to 504 TB of usable external capacity.
n Systems with 768 GB of memory installed support up to 42 x 2-TB or 28 x 3-TB
shelves adding up to 1,008 TB of usable external capacity.

Hardware Enhancements 5
Release Notes

n Systems with Data Domain Extended Retention software have 768 GB of

memory installed and support up to 56 ES30 (each with 15 x 3-TB drives)
shelves adding up to a maximum of 2,016 TB of usable external capacity.
n Systems enabled with DD Cloud Tier have 768 GB of memory installed and
support up to 2,016 TB of usable cloud storage.
n 768 GB is required for DD Cloud Tier and Extended Retention. HA is supported
with both memory configurations.
l Performance up to 58.7 TB/hr for aggregate writes using DD Boost.
l Performance up to 27.2TB/hr for aggregate writes using CIFS.
l Increased stream counts for backup and archiving workloads:
n Up to 1885 concurrent backup write streams.
n Up to 300 concurrent backup read streams.
n Up to 1885 destination replication streams.
n Up to 540 source replication streams.
l 8 hot-swappable fans, redundant.
l 4 hot-swappable power units, 2 pairs of 1 +1 redundant.

Software enhancements
This version of DD OS offers these important software enhancements.

Data Domain Cloud Tier

This feature allows data to be moved to low cost, high capacity object storage either
on-premise (e.g., EMC Elastic Cloud Storage (ECS)) or public cloud (e.g., Virtustream
Storage Cloud, Azure, or Amazon Web Services (AWS) Standard S3 storage) for
long-term retention. Enterprises and service providers can use DD Cloud Tier for long-
term retention of protection data with the benefits of:
l Scalable, native cloud tiering: automated, policy-based tiering directly from Data
Domain and store up to 2x of the maximum active tier capacity in the cloud for
long-term retention
l Lower TCO: Send only unique, deduplicated data to cloud storage for reduced
storage footprint and network bandwidth
l Meet regulatory and compliance policies
l Reduce costs with low cost object storage in the cloud (on-prem or public)
l Migrate data from tape to cloud
l Cold storage archiving with limited retrieval of data
l If the source system is running DD OS 5.6 or 5.7 and replicating into a Cloud Tier-
enabled system using MTree replication, the source system must be upgraded to a
release that can replicate to a Cloud Tier-enabled system, i.e., upgrade 5.6 to
5.6.2 or 5.7 to 5.7.3. Please see the DD OS system requirements.

Note

Data movement to cloud is not supported on VTL and VDISK MTrees.

Enhancements for 6.0.1 include:

6 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

l Amazon Web Services (AWS) Signature Version 4 request signing support for DD
Cloud Tier for enhanced security, the DD Cloud Tier feature uses Signature
Version 4 for all AWS requests. AWS V4 signing is enabled by default.
l New AWS Regions: This release features added support for the following new
AWS regions: ap-south-1, ap-northeast-2, eu-central-1.
l DD System Manager Enhancements
n Support for DD Cloud Tier file recall
n Support for new generation HDD drives available in 4K sector format

Note

Refer to the DD OS Administration Guide for information about platforms and

configurations that support DD Cloud Tier.

Data Domain Boost Filesystem (FS) Plug-in

This release introduces a new DD Boost feature called BoostFS, which runs on the
client and exposes the DD Boost protocol as a standard file system to the application.
The BoostFS plug-in is installed onto the Linux operating system of the application
server, which creates a Linux mount point. Backups or snapshots that are written to
the mount point are transmitted to the Data Domain using the DD Boost protocol,
which is transparent to the operator.
BoostFS combines the storage and bandwidth efficiencies of DD Boost in a simple well
known protocol format that's easy to understand and use. BoostFS allows customers
to extend the benefits of DD Boost to new applications and workloads that were
previously unavailable.
BoostFS is an open program that is available for any application or workload that
supports NFS protocol on Data Domain. The benefits of BoostFS would have to be
validated before BoostFS can be put into production. For the initial release, validated
applications include MySQL, MongoDB and Commvault. A list of validated applications
can be found in the BoostFS whitepaper, Boost Everywhere - Data Domain BoostFS
Integration Guide: Application Validation and Best Practices for Boost File System Plug-In.
Features:
l Distributed Segment Processing
l Dynamic Interface Groups
l Client Encryption (TLS 1.2)
l MTree Replication
l DD Boost over IP
l User Authentication - RSA LockBox or Kerberos
Supported Operating Systems: RHEL, SuSE, Ubuntu, CentOS
Validated Application:
l Commvault Simpana v11, v10, v9
l MongoDB Community v2.6, 3.0, 3.2
l MySQL Community - v5.7. v5.6
l MySQL Enterprise Mgr v5.7, v5.6

Software enhancements 7
Release Notes

DD Boost support for Targeted AIR

In this release Targeted AIR builds on the existing OST Plugin classic NetBackup AIR
functionality and provides the ability to use the DD Boost association command to
define one-to-many and many-to-one.
Configuration supported: DD OS 6.0 with the OST plug-in v3.3 for NetBackup 7.7.
(For more information, see the Data Domain Boost Compatibility Guide.)

ProtectPoint on Extended Retention (ER) enabled systems

ProtectPoint is now supported on Extended Retention enabled systems.

ProtectPoint integration with DD OS High Availability (HA)

This release now allows customers with a working ProtectPoint configuration to
deploy an HA pair and supports the failover capability.

Command changes
The subsections of this topic are summaries only. For full information about these
and other DD OS commands, refer to the DD OS Command Reference Guide for
details on how to use the DD OS 6.0 CLI commands.

Command typography is as follows:

Monospace type
Indicates a command name that is entered as shown.
Monospace italic type
Indicates a variable for which an actual value is supplied.

adminaccess change history

New commands in DD OS 6.0
adminaccess certificate generate self-signed-cert [regenerate-
ca]
Generates a self-signed CA certificate and host certificate.

adminaccess certificate cert-revoke-list delete {issuer

issuer-name | fingerprint fingerprint} [application {all |
cloud | ddboost | login-auth | application-list}]
Deletes the certificate revoke list for the specified issuer, fingerprint, or
application.

adminaccess certificate cert-revoke-list import application

{all | cloud | ddboost | login-auth | application-list} [file
file-name ]
Imports certificate revocation list file for applications.

adminaccess certificate cert-revoke-list show [detailed]

{application {all | cloud | ddboost | login-auth |

8 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

application-list} | issuer issuer-name | fingerprint

fingerprint}
Shows the certificate revocation list file present on the system using application,
CRL issuer or fingerprint options.

Modified arguments in DD OS 6.0

adminaccess certificate delete {imported-host application {all
| ddboost | https | rkm | application-list} | imported-ca
application {all | cloud | ddboost | login-auth | rkm |
support | application-list}}
The cloud application and login-auth have been added.
adminaccess certificate import {host application {all |
ddboost | https | rkm | application-list} | ca application
{all | cloud | ddboost | login-auth | rkm | application-list}}
[file file-name]
The cloud application and login-auth have been added.

adminaccess certificate show [detailed] [imported-host

[application {all | ddboost | https | rkm | application-list}]
| imported-ca [application {all | cloud | ddboost | login-auth
| rkm | support | application-list}] | host | ca | subject
subject-name | fingerprint fingerprint
The cloud application and login-auth have been added.

alerts change history

New commands in DD OS 6.0
alerts test events alert-id-list [prompt-for-input]
Generate a test alert on the Data Domain system. The prompt-for-input
prompts for user input as the command runs. This option requires interactive
mode.

Modified arguments in DD OS 6.0

alerts notify-list create group-name {class class-list
[severity severity] | tenant-unit tenant-unit | tenant
<tenant> }
Adds the tenant option.

alerts notify-list show [group group-name | email email-addr]

| tenant-unit tenant-unit | tenant <tenant>]
Adds the tenant option.

Modified output in DD OS 6.0

alerts notify-list create group-name {class class-list
[severity severity] | tenant-unit tenant-unit | tenant
<tenant> }
Informs the user that the new alert notification list will be used for all tenant-units
owned by a tenant specified when the list is created.

alerts change history 9

Release Notes

authentication change history

Modified arguments in DD OS 6.0
authentication nis groups show [role {user | admin | backup-
operator | limited-admin}]
The limited-admin role has been added.

authentication nis groups del group-list role {user | admin |

backup-operator | limited-admin}
The limited-admin role has been added

authentication nis groups add group-list role {user | admin |

backup-operator | limited-admin}
The limited-admin role has been added

cifs change history

Modified behavior in DD OS 6.0
cifs option reset name
Name field will support group name “dd limited-admin group1” to “dd limited-
admin group50”.

cifs option set name value

Name field will support group name “dd limited-admin group1” to “dd limited-
admin group50”.

client-group change history

New commands in DD OS 6.0
This is the first release of the client-group command family.

cloud change history

New commands in DD OS 6.0
This is the first release of the cloud command family.

data-movement change history

New commands in DD OS 6.0
This is the first release of the data-movement command family.

ddboost change history

Modified arguments in DD OS 6.0
ddboost clients add client-list [authentication-mode {one-way
| two-way | anonymous}] | [authentication-mode kerberos]
Adds the kerberos option, which is available only to clients running BoostFS.

10 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

ddboost clients modify client-list {encryption-strength {none

| {medium | high} authentication-mode {one-way | two-way |
anonymous}}} | {authentication-mode kerberos}
Adds the kerberos option, which is available only to clients running BoostFS.

Modified behavior in DD OS 6.0

ddboost fc group add group-name initiator initiator-spec
If "disk" is not specified, then the default DFC device type ("Processor") is
added.

Modified output in DD OS 6.0

ddboost file-replication show active [all | storage-unit
storage-unit | tenant-unit tenant-unit]
Show the status of a DD Boost file-replication to destination Data Domain
systems.

ddboost file-replication show history [duration duration{day |

hr}] [interval interval{hr}]
Show the data transfer history between the source and destination Data Domain
systems.

disk change history

New commands for DD OS 6.0
disk release persistent-id {persistent-id | all}
Releases the disk's persistent ID and enables persistent ID to be assigned on the
next boot.

elicense change history

The elicense commands are new in the DD OS 6.0 release.

filesys change history

Modified arguments in DD OS 6.0
filesys encryption disable [tier active | cloud-unit {unit-
name | all}]
Updated to accept the tier and unit-name to manage encryption independently on
each tier or cloud unit.
filesys encryption enable [tier active | cloud-unit {unit-name
| all}]
Updated to accept the tier and unit-name to manage encryption independently on
each tier or cloud unit.
filesys encryption keys show [tier {active | archive | cloud}
| archive-unit archive-unit-name | cloud-unit cloud-unit-name]
Updated to accept the tier and unit-name to manage encryption independently on
each tier or cloud unit.

disk change history 11

Release Notes

filesys show compression [tier {active | archive | cloud}]

summary | daily | daily-detailed {[last n {hours | days |
weeks | months}] | start date [end date]
Updated for cloud tier.
filesys show space [tier {active | archive | cloud | total} |
archive-unit {all | unit-name} | cloud-unit {all | unit-name}]
Updated for cloud tier.

Modified output in DD OS 6.0

filesys encryption disable [tier active | cloud-unit {unit-
name | all}]
Command output is updated to show status for cloud units.
filesys encryption enable [tier active | cloud-unit {unit-name
| all}]
Command output is updated to show status for cloud units.
filesys encryption key-manager disable
An error message is displayed when encryption is enabled on one or more cloud
units.
filesys encryption key-manager enable
An error message is displayed when encryption is enabled on one or more cloud
units.
filesys encryption key-manager reset
An error message is displayed when encryption is enabled on one or more cloud
units.
filesys encryption key-manager set
An error message is displayed when encryption is enabled on one or more cloud
units.
filesys encryption key-manager show
An error message is displayed when encryption is enabled on one or more cloud
units.
filesys encryption keys show [tier {active | archive | cloud}
| archive-unit archive-unit-name | cloud-unit cloud-unit-name]
Command output is updated to show status for cloud units.
filesys encryption lock
An error message is displayed when encryption is not enabled on the active tier.
filesys encryption show
Command output is updated to show information for cloud units.
filesys encryption status
Command output is updated to show information for cloud units.
filesys show compression [tier {active | archive | cloud}]
summary | daily | daily-detailed {[last n {hours | days |
weeks | months}] | start date [end date]
Command output is updated to show compression for the cloud tier.

12 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

ha change history
Modified output in DD OS 6.0
ha status [detailed]
Add the percentage of HA availability in the detailed output.

license change history

Modified arguments in DD OS 6.0
license show scheme [local]
Updated to show the licensing scheme: unknown, DD licensing, or elicensing.

log change history

New commands in DD OS 6.0
log view access-info [authentication-failures {all | known-
users | unknown-users} | access-history {all | logins |
logouts} | user-management] [user <user-name>] [last <n>
{hours | days | weeks | months} | start <MMDDhhmm[[CC]YY]>
[end <MMDDhhmm[[CC]YY]>]]
Displays a history of user logins and logouts on the system, including both
successful and unsuccessful attempts to log in.
log view audit-info [authorization-errors | all-errors] [user
<user-name>] | user-role {admin | security | user | backup-
operator | none}] [tenant-unit <tenant-unit>] [host <host>]
[application {CLI | REST | GUI | VDISK}] [string <str>] [last
<n> {hours | days | weeks | months} | start <MMDDhhmm[[CC]YY]>
[end <MMDDhhmm[[CC]YY]>]]
Displays a list of all system management configuration changes, and provides the
following the following details:
l Username of the user who initiated the configuration change
l TImestamp
l Requested operation
l Operation outcome

mtree change history

Modified arguments in DD OS 6.0
mtree show compression {mtree-path | tenant-unit tenant-unit}
[tier {active | archive | cloud}] [summary | daily | daily-
detailed] [last n {hours | days | weeks | months} | start date
[end date]]
Updated for cloud tier.

ha change history 13
Release Notes

Modified output in DD OS 6.0

mtree show performance {mtree-path | tenant-unit tenant-unit}
[interval n {mins | hours}] [last n {hours | days | weeks |
months} | start MMDDhhmm[[CC]YY] [end MMDDhhmm[[CC]YY]]]
This command now displays random and sequential read and write stream
performance counters.
mtree show compression {mtree-path | tenant-unit tenant-unit}
[tier {active | archive | cloud}] [summary | daily | daily-
detailed] [last n {hours | days | weeks | months} | start date
[end date]]
Command output is updated to show compression for the cloud tier.

net change history

New commands in DD OS 6.0
net config addresses type {fixed | floating}
Bulk convert IP addresses on the Data Domain system to the specified type. The
system prompts for each IP address individually. This command only works on HA
systems. Role required: admin.
net filter add [seq-id n] operation {allow | block} [clients
{host-list | ipaddr-list}] [except-clients {host-list |
ipaddr-list}] [interfaces {ifname-list | ipaddr-list}]
[except-interfaces {ifname-list | ipaddr-list}] [ipversion
{ipv4 | ipv6}]
Add a set of rules to the iptables. You cannot mix client hosts and addresses, and
you cannot mix interface names and local IP addresses.
net filter clear stats
Clear all iptables rules statistics.
net filter config reset [admin-interface] [ipversion {ipv4 |
ipv6}]
Set the net filter configuration option to the default value; reset all if no options
specified.
net filter config set [admin-interface ifname] [ipversion
{ipv4 | ipv6}]
Set a net filter option.
net filter config show [admin-interface] [ipversion {ipv4 |
ipv6}]
Show the net filter configuration option; show all if no options specified.
net filter delete {seq-id | all} [ipversion {ipv4 | ipv6}]
Delete one net filter command or all of them. A default function cannot be
deleted.
net filter disable {seq-id | all} [ipversion {ipv4 | ipv6}]
Disable one net filter command or all of them.
net filter enable {seq-id | all} [ipversion {ipv4 | ipv6}]
Enable one net filter command or all of them.

14 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

net filter log start

Start writing to the net filter log.
net filter log stop
Stop writing to the net filter log.
net filter move seq-id new-seq-id [chain {chain-name | all}]
[ipversion {ipv4 | ipv6}]
Move command at seq-id to new-seq-id.
net filter show kernel [ipversion {ipv4 | ipv6}] [chain
{chain-name | all}]
Show iptable rules configured. If a chain is given only the rules for that chain are
displayed. If all is given then all the rules for all of the chains are displayed. The
format is the same format used by iptables to display the rules.
net filter show map {ids | all} [ipversion {ipv4 | ipv6}]
[chain {chain-name | all}]
Show the net filter functions configured and the iptable rules associated with
each function. One id or a list of ids can be given.
net filter show seq-id-list {ids | all} [ipversion {ipv4 |
ipv6}] [chain {chain-name | all}]
Show the net filter commands configured. One id or a list of ids can be given.
net filter start
Create the restricted rules, create the required iptable chains, and add the default
net filter functions along with the associated iptable rules.
net route add gateway ipv4address [interface name]
Add a gateway address to the list of gateway addresses on the Data Domain
system. Optionally specify a specific interface to associate with the gateway
address. If the gateway is unreachable, the system displays a warning, but still
adds the gateway.
net route del gateway ipv4address [interface name]
Deletes the specified gateway, along with its associated route entries and route
rules. If the gateway is "targeted" (associated with a specific interface), the
interface must be also given.
net route show config
Display the configured static routes.
net route show gateways [detailed] [ipversion {ipv4 | ipv6}]
Displays the configured or DHCP-supplied IPv4 and IPv6 gateways as specified.
The detailed option displays the network interface or type, associated routing
tables, interface addresses, and owners if applicable. If no IP version is specified,
both gateway versions are displayed.
net route show tables [table-name-list | ipversion {ipv4 |
ipv6}]
Displays the IPv4 and IPv6 routing tables as specified. If no IP version is specified,
both table versions are displayed. For IPv4, a list of routing tables is displayed; the
routing within each table is displayed and the rules associated with the table is
displayed. The main IPv4 routing table is displayed in the same form as was done
previously, but the other tables are displayed in the same form as the output from

net change history 15

Release Notes

the ip route list command. The output for IPv6 versions is the same as it
was previously.

qos change history

New commands in DD OS 6.0
This is the first release of the qos command family.

replication change history

New commands in DD OS 6.0.2.0
replication modify destination crepl-gc-bw-optim {enabled |
disabled}
Modify the state of the collection replication setups in production. This setting
will only be allowed when the file system is disabled. Role required: admin, limited-
admin.

Modified behavior in DD OS 6.0.2.0

replication show performance {obj-spec-list | tenant-unit
tenant-unit | all} [interval sec] [count count]
Due to the presence of multiple threads working on behalf of the specified
replication context, the average values are displayed. This average is calculated
by adding all the values from all the threads that worked on behalf of the
replication context, and dividing this sum with the number of threads that worked
on behalf of the context.

replication change history

New commands in DD OS 6.0.2.0
replication modify destination crepl-gc-bw-optim {enabled |
disabled}
Modify the state of the collection replication setups in production. This setting
will only be allowed when the file system is disabled. Role required: admin, limited-
admin.

route change history

New commands in DD OS 6.0
route add gateway ipv4address [interface name]
Add a gateway address to the list of gateway addresses on the Data Domain
system. Optionally specify a specific interface to associate with the gateway
address. If the gateway is unreachable, the system displays a warning, but still
adds the gateway.
route del gateway {ipv4address | routing-table-name name
Deletes the specified gateway, along with its associated route entries and route
rules.

16 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Modified arguments in DD OS 6.0

route add [ipversion {ipv4 | ipv6}] [type {fixed | floating}]
<route spec>
Lets you specify either a fixed or floating static route.
route show config [routing-table-name name]
Adds an option to specify routing tables.
route show gateways [detailed] [ipversion {ipv4 | ipv6}]
Adds the detailed option to display the network interface or type, associated
routing tables, interface addresses, and owners if applicable.
route show tables [table-name-list | gateway ipv4addr |
ipversion {ipv4 | ipv6}]
Adds options to specify table names or gateway addresses.

smt change history

New commands in DD OS 6.0
smt tenant-unit data-ip add local ipv4-ipv6-list [remote
ipaddr-list] tenant-unit tenant-unit
Add a local or remote data-ip to a Tenant Unit.
smt tenant-unit data-ip del local ipv4-ipv6-list [remote
ipaddr-list] tenant-unit tenant-unit
Delete a local or remote data-ip from a Tenant Unit.
smt tenant-unit data-ip show [tenant-unit | all]
Show the local and remote data IP addresses for a Tenant Unit.
smt tenant-unit gateway add ipv4-address tenant-unit tenant-
unit
Add a gateway to a Tenant Unit.
smt tenant-unit gateway del ipv4-address tenant-unit tenant-
unit
Delete a gateway from a Tenant Unit.
smt tenant-unit gateway show [tenant-unit | all]
Show the gateway for a Tenant Unit.
smt tenant-unit hostname reset tenant-unit tenant-unit
Delete a hostname from a Tenant Unit.
smt tenant-unit hostname set hostname tenant-unit tenant-unit
Add a hostname to a Tenant Unit.
smt tenant-unit hostname show [tenant-unit | all]
Show the hostname for a Tenant Unit.

smt change history 17

Release Notes

storage change history

Modified arguments in DD OS 6.0
storage add [tier {active | archive | cache | cloud}]
{enclosures <enclosure-list> | disks <disk-list> | <LUN-list>
[spindle-group <1-16>]}
The arguments have been modified to provide the ability to add multiple devices
at once and to add storage to the cloud and cache tiers.
storage remove {enclosures <enclosure-list> | disks <disk-
list> | <LUN-list> [spindle-group <1-16>]}
The arguments have been modified to provide the ability to remove multiple
devices at once.
storage show {all | summary | tier {active | archive | cache |
cloud}}
The arguments have been modified to include cloud and cache tier storage.

Modified behavior in DD OS 6.0

storage migration precheck source-enclosures enclosure-list
destination-enclosures enclosure-list
Perform checks to determine if data migration can proceed from one or more
source enclosures to one or more destination enclosures. For example, the
storage on the destination enclosure set must be equal to or larger than the
storage on the source enclosure set.
storage migration start source-enclosures enclosure-list
destination-enclosures enclosure-list
Initiate data migration from one or more source enclosures to one or more
destination enclosures. The storage on the destination enclosure set must be
equal to or larger than the storage on the source enclosure set. If necessary the
command reserves space inside the file system to account for different types of
drives.

Modified output in DD OS 6.0

storage migration precheck source-enclosures enclosure-list
destination-enclosures enclosure-list
Perform checks to determine if data migration can proceed from one or more
source enclosures to one or more destination enclosures. For example, the
storage on the destination enclosure set must be equal to or larger than the
storage on the source enclosure set.
storage migration start source-enclosures enclosure-list
destination-enclosures enclosure-list
Initiate data migration from one or more source enclosures to one or more
destination enclosures. The storage on the destination enclosure set must be
equal to or larger than the storage on the source enclosure set. If necessary the
command reserves space inside the file system to account for different types of
drives.
storage migration status
Display the status of storage migration.

18 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

support change history

New commands in DD OS 6.0
support connectemc device register ipaddr esrs-gateway {ipaddr
| hostname } [ha-peer ipaddr]
Register the system to the ESRS gateway.
support connectemc device unregister
The system displays a warning message that ConnectEMC will be unregistered
from the ESRS gateway, and email will be set as the notification method.
support connectemc device update [new-ipaddr] [ha-peer new-
ipaddr]
Update the system's IP address for the ESRS gateway.

Modified output in DD OS 6.0

support bundle create default [with-files file-list] [and-
upload [transport {http|https}]]
The maximum number of support bundles allowed has been changed from 10 to 5.

Deleted commands in DD OS 6.0

support connectemc config add alternate {direct [transport
{email}] | esrs-gateway ip-address [transport {email | ftp |
https}]}
Add an alternate transport for ConnectEMC reporting when the primary or other
alternates are not available. You can configure multiple alternates. The arguments
for this command are the same as those for support connectemc config
set.

support connectemc config del alternate {all | direct

[transport {email}] | esrs-gateway ip-address [transport
{email | ftp | https}]}
Delete an alternate transport for ConnectEMC reporting. The arguments for this
command are the same as those for support connectemc config set.

support connectemc config set {direct [transport {email}] |

esrs-gateway ip-address [transport {email | ftp | https}]}
Select the primary transport method for ConnectEMC messages. You can
configure only one primary transport. The direct method sends messages by
secure email directly to EMC. The ESRS-gateway method sends messages to an
EMC Secure Remote Support (ESRS) gateway at the specified IP address (or
resolvable hostname) using the specified protocol. If you omit the transport
protocol, the default protocol for the ESRS-gateway method is HTTPS.
support connectemc config set notify-admin {none | onfailure |
always}
Define which notification event types trigger an email alert to the system
administrator. The onfailure option is the default and alerts the administrator only
when EMC notification fails. The always option alerts the administrator each time
a notification is sent to EMC.

support change history 19

Release Notes

support connectemc reset

Reset the transport method to the default method, which is direct transport using
email.

system change history

Modified arguments in DD OS 6.0
system package show installed
Lists the packages that are installed on the system.
system upgrade uninstall package [local]
Requests that the named add-on package be uninstalled.

Modified output in DD OS 6.0

system show all
Show all system information.

system package list [file]

system show all
Show all system information.

Now indicates whether the package is signed and, if so, whether the signature is
valid.

system show serialno [detailed]

Now shows whether encryption is enabled.

user change history

Modified arguments in DD OS 6.0
user add user [role {admin | limited-admin | security | user |
backup-operator | none}] [min-days-between-change days] [max-
days-between-change days] [warn-days-before-expire days]
[disable-days-after-expire days] [disable-date date] [force-
password-change {yes | no}]
The role of limited-admin has been added.

user change role user {admin | limited-admin | user | backup-

operator | none}
The role of limited-admin has been added.

Modified behavior in DD OS 6.0

user add user [role {admin | limited-admin | security | user |
backup-operator | none}] [min-days-between-change days] [max-
days-between-change days] [warn-days-before-expire days]
[disable-days-after-expire days] [disable-date date] [force-
password-change {yes | no}]
The following list describes the roles that can add new users, and the level of
users that they can add:
l sysadmin: Can add admin, limited-admin, backup-operator, user, none.

20 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

l admin: Can add limited-admin, backup-operator, user, none.

l limited-admin: Can add backup-operator, user, none.

user change password [user]

The following list describes the roles that can change passwords and the level of
users that they can change passwords for:
l sysadmin: Can change password for itself, admin, limited-admin, backup-
operator, user, none.
l admin: Can change password for itself, limited-admin, backup-operator, user,
none.
l limited-admin: Can change password for itself, backup-operator, user, none.
l security officer: Can change its own password only.

user change role user {admin | limited-admin | user | backup-

operator | none}
The following list describes the roles that can change the roles of other users, and
the level of users that they can act upon:
l sysadmin: Can change admin, limited-admin, backup-operator, user, none.
l admin: Can change limited-admin, backup-operator, user, none.
l limited-admin: Can change backup-operator, user, none.

user del user

The following list describes the roles that can delete users, and the level of users
that they can delete:
l sysadmin: Can delete admin, limited-admin, backup-operator, user, none.
l admin: Can delete limited-admin, backup-operator, user, none.
l limited-admin: Can delete backup-operator, user, none.

user disable user

The following list describes the roles that can disable users, and the level of users
that they can disable:
l sysadmin: Can disable admin, limited-admin, backup-operator, user, none.
l admin: Can disable limited-admin, backup-operator, user, none.
l limited-admin: Can disable backup-operator, user, none.

user enable user [disable-date date]

The following list describes the roles that can enable users, and the level of users
that they can enable:
l sysadmin: Can enable admin, limited-admin, backup-operator, user, none.
l admin: Can enable limited-admin, backup-operator, user, none.
l limited-admin: Can enable backup-operator, user, none.

user change history 21

Release Notes

vdisk change history

New commands in DD OS 6.0
vdisk config export [{pool <pool-name>| pool <pool-name>
device-group <device-group-name>}] output-file <file-name>
Export a vdisk configuration to a file pathname Optionally specify a specific pool
or device-group configuration for export.
vdisk config import [{pool <pool-name>| pool <pool-name>
device-group <device-group-name>}] [check-only] [skip-
initiators] [retain-serial-numbers] [on-error {continue |
stop}] input-file <filename>
Import a vdisk configuration that was exported to a file for migration to another
location.

Modified behavior in DD OS 6.0

vdisk device show detailed [wwn <wwn-name>] | [<device-spec>]
[{pool <pool-name> | pool <pool-name> device-group <device-
group-name>}]
Added the wwn parameter to display device information for a specific device.
vdisk device show list [wwn <wwn-name>] | [<device-spec>]
[{pool <pool-name> | pool <pool-name> device-group <device-
group-name>}]
Added the wwn parameter to display device information for a specific device.

Modified output in DD OS 6.0

vdisk show config
The maximum values are system-wide limits inherited from the MTree limit. The
command adjusts the output based on MTrees used by other protocols. The
maximum number of pools supported ranges from 100 to 256, depending on the
specific model of Data Domain system.

Fixed issues
This release of DD OS, 6.0.2.40-615545, includes a number of fixed issues. The
release also includes fixed issues from prior releases in the DD OS 6.0 feature family.

Fixed in version 6.0.2.40 - 615545

This list contains important changes and updates that are made to this version of DD
OS.

Table 2 DD OS 6.0.2.40— CIFS/NFS Issues: Fixed

Issue Description
206534 The cifs set authentication active-directory operation fails with no error if issued
while another Active Directory domain join operation is in progress. DD OS now
returns the message, "The domain join operation is already in progress."

22 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 2 DD OS 6.0.2.40— CIFS/NFS Issues: Fixed (continued)

Issue Description
225434 When using System Manager, theCIFS Share > Modify > Client field could
enter a state where it could not be modified.

Table 3 DD OS 6.0.2.40— DD Boost: Fixed

Issue Description
209295 Timing is increased to prevent a file system communication timeout for DD Boost
commands.

211387 A timeout and panic occurred when the Data Domain system tried to sync data
between HA pairs.
The following messages appeared in the messages.engineering log:
INFO: Async rpc procedure (NFSPROC3_DDP_OPEN_FILE) timed out, time
elapsed 446 secs.
ERROR: MSG-INTRNL-00001: PANIC: ddr/nfs/nfs_rpc.c: nfs_rpc_debug_cb:
299: Async rpc taking too long (> 420 secs)

Table 4 DD OS 6.0.2.40— File System Issues: Fixed

Issue Description
194301 The Data Domain File System panicked with the following message in the
ddfs.info file:
ERROR: MSG-INTRNL-00001: PANIC: include/dd_alloc.h:
_dd_malloc_aligned_pc: 634: Memalign returned null

199565 The filesystem restarted during cleaning. The following message was written to
the ddfs.info log:
EVT-FILESYS-00008: Filesystem has encountered an error and is restarting.

200786 When using system manager, the Filesystem page did not display any data. The
following error messages were found in the EM.info log:
ERROR [ajp-bio-8009-exec-1] Unable to retrieve cloud profiles: cloud profile:
AWS_profile not found
ERROR [ajp-bio-8009-exec-1] An exception occurred while handling a client
request java.lang.NullPointerException at
com.datadomain.sm.common.model.cloud.

219492 Replication jobs fail if source data was copied to the Data Domain system from a
Windows client using an xcopy command. The replication source was in the
following state: Error from remote host: failed to execute record 27760097 due
to a prior failure on record 27760051
The following message was found in ddfs.info log of the replication
destination:
ERROR: MSG-DREPL-00033: drepl:

224946 Erroneous CRITICAL hardware alerts halted filesystem operation or prevented

filesystem from starting.

Fixed in version 6.0.2.40 - 615545 23

Release Notes

Table 4 DD OS 6.0.2.40— File System Issues: Fixed (continued)

Issue Description
232037 The filesystem panicked. The following message appeared in the ddfs.info
log:
ERROR: MSG-INTRNL-00001: PANIC: ddr/sl/sl_blkset.c:
sl_blkset_resize_blkset_metadata: 7996: Fatal Error.

Table 5 DD OS 6.0.2.40— General Issues: Fixed

Issue Description
207150 This release fixes a security header issue with the user interface.

210041 A memory error caused the loss of System Manager access. The following
messages appeared in the sms.info log:
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "ajp-bio-8009-AsyncTimeout"
Exception in thread "Thread-2" java.lang.OutOfMemoryError: Java heap space

Table 6 DD OS 6.0.2.40— Networking Issues: Fixed

Issue Description
209952 When a fixed IP was configured on and Ethernet interface, and the interface was
configured for both active and standby mode, the following behaviors occurred:
Disabling the Ethernet interface on active node caused the Ethernet interface on
standby node to also be disabled.
Then, enabling the Ethernet interface on active node caused the Ethernet
interface on standby node to never come up.

217608 Floating routes were not restored after a standby node in an HA configuration
crashed.

Table 7 DD OS 6.0.2.40— Platform Issues: Fixed

Issue Description
184873 This release fixes the issue that cause the historical database to panic.

221562 The OpenSSH server running on the Data Domain system was potentially
vulnerable to the issue described in CVE-2017-15906.

227463 This issue mitigates the Data Domain JRE/JDK (third party platform) upgrade
vulnerability per PSRC-6615 Oracle Critical Patch Update Advisory - October
2018 described per CVE-2018-3180.

228946 This releases fixes an issue with the memriser alert. The old alert will now
disappear after the faulty memriser is replaced.

24 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 8 DD OS 6.0.2.40—Replication Issues: Fixed

Issue Description
196994 This release fixes the MTree synching issue that affected replication
performance.

227474 The basefile can be used if the basefile is moved to cloud but not moved on the
REPL target.

Table 9 DD OS 6.0.2.40— VTL/vDisk/Fibre Channel Protocols Issues: Fixed

Issue Description
186195, IBMi BRMS did not recognize the ejection of the tape from the Data Domain
228772 VTL.

226928 When upgrading from 5.7 to 6.X, drives in libraries whose name contained the
string "drive" were reclassified as type 1.
The following list contains examples of affected library names:
l LibLOT5drives
l VTL_V11_HPdrives
l VTL_IBMdrives

Fixed in version 6.0.2.30 - 606339

This list contains important changes and fixes that are made to this version of DD OS.

Table 10 DD OS 6.0.2.30— CIFS/NFS Issues: Fixed

Issue Description
189157 This release fixes a timing issue that previously occurred when there were out of
order read requests while reading from CIFS.

206299 During replication, local group members on destination Data Domain system are
removed or added correctly.

208572 This fix reconciles a race condition between one thread freeing ddfm request and
another thread (ddfm_stats_logger) logging it.

215111 This release fixes an with where a Data Domain System unjoins the AD and has
to rejoin the system manually every time.

Table 11 DD OS 6.0.2.30— DD Boost: Fixed

Issue Description
192549 This release addresses Oracle message sizes.

202950 This release fixes an issue with HA mirroring after a manual fail over.

Fixed in version 6.0.2.30 - 606339 25

Release Notes

Table 12 DD OS 6.0.2.30— DD Cloud Tier: Fixed

Issue Description
198328 This release fixes an issue with unsealing an archive unit on high end platforms
with Extended Retention (ER).

Table 13 DD OS 6.0.2.30— File System Issues: Fixed

Issue Description
86968 This release addresses the print_stat issue which caused the system to
panic.

170657 This fix verifies whether the system is shutting down before performing the
inline dmck thread, which may otherwise cause a system to panic.

172034 This release fixes an interruption of service issue that could occur when Physical
Capacity Reporting (PCR), Garbage Collection (GC), and MTree deletion are
simultaneously implemented.

175279 This release fixes the SegStore issue that causes the file system to panic.

176200 This release disables background PCR activities and now periodically displays
system space usage.

180321 This release upgrades OpenSSH to version 7.5p1.

180345 This release fixes a race condition with low free page, which may cause a system
to panic.

184148 A segmentation fault in the content store was fixed in this release.

187165 This release fixes an issue that may occur when CIFS attempt to open an MTree
with DOC flag set and possibly lead to a system panic.

190469 This release fixes an issue with MTree replication (MREPL) stat inflation during
fast copy overwrite.

190892 In this release, the alert interval has been increased from 10,000 to 1 billion to
release frequencies of these alerts.

193302 This release fixes the Data Domain File System with a cloud issue that caused
the system to panic.

196008 This release no longer clears the buffers used by readdir during destroy
session.

197031 This release resolves an issue that caused a user to be unable to update an
expiring password.

197321 This release disables background PCR activities and now periodically displays
system space usage.

197654 Correct speed is now displayed for MTree show performance command for DD
Boost backups.

199267 This release fixes an issue where the Data Domain File System may panic
consistently every N number of days, where N depends on the Data Domain
platform and workload. For more information, see KB article# 513385

200161 Multiple exit points have been added in inline dmck path to prevent system
panics.

26 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 13 DD OS 6.0.2.30— File System Issues: Fixed (continued)

Issue Description
203762 This release adjusts Cloud GC selection for container sizing.

204159 This release resolves an issue that could cause a system to panic. See KB
article# 517450 for more information.

206141 This release corrects a file system expunge issue that could cause a system to
panic.

207571 In this release, the index now purges all dead entries, which otherwise may cause
a file system to become read-only or cause a system to panic.

208027 This release fixes CREPL issues that caused I/O errors on containers.

208389 This release disables the removal of attributes from Attribute BTree when
DMCK runs.

208570 Replicating errors that occur during replication now display an error message
instead causing a file system panic.

209382 This release addresses a file manager issue that caused HMON panic.

209959 This release fixes the MREPL issue that caused the file system panic.

210451 The fix allows the https host certificate to be imported correctly on the active
node and on standby.

211807 This release fixes the issue that caused the system to panic during a system
shutdown or when an MTree is deleted.

216655 This release fixes the issue where NVRAM replay incorrectly skipped some
containers after a filesystem panic.

216787 Computations for 64-bit usage were corrected to allow the PCR to function
correctly.

218623 Improvements the CLI and HMON performance during disk rebuilding were made
in this release.

219583 Files being read via CIFS are no longer truncated by an overwrite attempt.

222367 This release fixes an issue where the "checksum verify" failed and caused a
system to panic.

Table 14 DD OS 6.0.2.30 General Issues: Fixed

Issue Description
180639 This release fixes an issue in the Data Domain shutdown path where FMIG
interfaces can exit gracefully.

183970 This release corrects an issue where FMIG ran with fewer threads when the
"space full" condition is reached.

187943 With this fix, cloud sealing now syncs the CP after writing the prime containers.

208584 This release fixes an issue where large files could cause the verification phase to
timeout and not moving the eligible files to DD Cloud Tier.

Fixed in version 6.0.2.30 - 606339 27

Release Notes

Table 14 DD OS 6.0.2.30 General Issues: Fixed (continued)

Issue Description
211397 This release removes unnecessary log prints during fm copy operation to avoid
possible coring on HA systems.

Table 15 DD OS 6.0.2.30— Networking Issues: Fixed

Issue Description
166123 This release addresses disk_show reliability data reports for disks in the cloud.

197110 This release resolves an HMON timeout error that could cause a system to panic.

209021 User may now use net config <ifname> down command to bring an
interface down.

Table 16 DD OS 6.0.2.30— Platform Issues: Fixed

Issue Description
170264 This release fixes an issue where the system detected an invalid hardware
configuration on DD4500.

179156 This fix deletes the flag which changes the code path.

182628 This release sets the flag to show that a failback is in progress and delays post
alert.

182660 This release addresses system time alerts on the DD6300.

187864 This release fixes the platform library issue that caused the system to panic.

188134 The power issue which caused the file system to panic was resolved in this
release.

189505 This release addresses the issue that caused the file system to panic during a
PRAM synch.

196016 This release corrects an issue where SMT PCR schedules were previously not
completing on the tenant unit.

196962 This fix allows systems with POST to upgrade and restart successfully.

198311 This release fixes the issue which caused the heramon output log file to cause
the system to panic.

198465 This release fixes a persistent "low on spares" alert on DD6300 systems that
started as a five drive unit and expanded to 12 drives with at least 1 SSD
configured in the cache tier.

202997 This release resolves an issue with an upgrade-related corrupted registry and
synchronization issue.

203690 This release fixes an issue where a single disk failure could cause a filesys restart.

203945 There is no longer an issue with the system show stats view sysstat
command, which previously did not perform correctly on the first run.

204028 This release adds support to register to multiple Secure Remote Services
gateways.

28 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 16 DD OS 6.0.2.30— Platform Issues: Fixed (continued)

Issue Description
209512 This release fixes an issue with an error message that is not applicable to the
DD860.

213031 This release fixes an issue where a system could not auto-reboot.

213401 This fix uses the correct maximum max_hdbs number for the check and avoids
an out of bounds memory access issue.

215017 This release fixes the driver pointer context issue that could cause the kernel to
panic.

216538 This is the fix for the DD9800 SmartMod SSD issue.

216788 This releases fixes the NVRAM issue on the DD9800 that caused the to panic.

217812 This release prunes the DD Boost sample count.

219535 This release fixes an issue with DD860/DD890 systems that may encounter a
BMC hang incident after an upgrade to DD OS 6.0.2.20.

Table 17 DD OS 6.0.2.30 Replication Issues: Fixed

Issue Description
184506 This release fixes the managed file replication history logging issue.

188943 This CREPL fix prevents mishandling in the error path.

190429 This release fixes the SegFile issue in the replication directory.

196870 This release fixes the replication directory issue that caused the system to panic.

202444 The fix in this release is to unlock the relevant mutex before replication.

205089 This release fixes the MTree issue that caused MREPL to panic.

205625 This release addresses the one-to-many replication configuration that previously
caused the system to panic.

206082 This release addresses high log overhead that previously caused the file system
to panic.

206212 The fix in this release captures debug logs to prevent file system panic.

206884 This release fixes the MTree issue that caused the file system to panic.

207372 This release enhances collection replication performance after upgrading to

6.0.2.013 from 5.7.4.014.

208755 This release fixes a recipe issue that could cause a system to panic.

213176 This release fixes an issue where the Replication > Automatic tab on the GUI
was indefinitely unresponsive.

Table 18 DD OS 6.0.2.30— VTL/vDisk/Fibre Channel Protocols Issues: Fixed

Issue Description
191424 This release addresses slow UI and CLI performance that was caused by VTL
issues.

Fixed in version 6.0.2.30 - 606339 29

Release Notes

Table 18 DD OS 6.0.2.30— VTL/vDisk/Fibre Channel Protocols Issues: Fixed (continued)

Issue Description
215672 A check (step) was added to the VTL to validate enough space is available to
write current record.

Fixed in version 6.0.2.20 - 587212

This list contains important changes and fixes that are made to this version of DD OS.

Table 19 Security Updates in DD OS 6.0.2.20

Issue Description
207248 This release upgrades JRE used in DD MC which addresses JRE security issues.

Refer to the Common Vulnerabilities and Exposures (CVEs) section for more
information about CVEs.

Table 20 DD OS 6.0.2.20— CIFS/NFS Issues: fixed

Issue Description
176179 NFSv4 high-stream count read performance has been improved.

195120 This release fixes an issue where High Availability (HA) configurations
experienced issues with syncing that could cause a system to panic.

196269 Backups will no longer panic over SMB2 while using Windows 2012 with this
release.

Table 21 DD OS 6.0.2.20— Cloud Issues: fixed

Issue Description
188995 Cloud capacity details can now appear if the cloud unit is in the Delete-Pending
state.

201910 DD9550 migrating data to local ECS cloud, previously reported ECS
unavailability due to multiple File System restarts.

203349 Avamar recall from cloud no longer panics because the size of the recalled file is
larger than free space on active tier.

Table 22 DD OS 6.0.2.20— File System Issues: fixed

Issue Description
165999 This release fixes the cloud tier enablement issue which caused the system to
panic.

171926 This release fixes the issue which caused an alert to post and an active CP to
panic during cloud CP startup.

175910 Logging context was allocated in NFS thread context to prevent HMON panics.

178315 This release addresses the DD VE issues with AWS that caused HMON panics.

30 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 22 DD OS 6.0.2.20— File System Issues: fixed (continued)

Issue Description
181594 The timeout window for data migration to Cloud Tier has been increased from 1
second to 20 seconds.

186587 This fix addresses the Content Store workload issue which caused the file
system to panic.

187058 This release resolves an issue with ASUP collection that could cause a system to
panic.

193979 This release resolves a timeout issue that may occur when the DM span reads
are more than 1 L1 and stall if n-1 L1 cache pages are dirty.

195156 This release fixes a race between dmbt_passive_compactor_thread and

dmbt_remove_entry when INTR1 page is empty.

196256 This release fixes the encryption issue for a second cloud unit's CP key table.

198041 This release fixes the missing segment issue that caused the file system to panic.

200394 With this fix, the software configuration management tool (SCM) control vector
now functions correctly Mtree adjustments.

202011 This release ensures that UNAVAIL clears all the cases for FMIG and Garbage
Collection (GC) invoked sealing.

204398 This release fixes the excessive logging during virtual synthetic backups.

Table 23 DD OS 6.0.2.20 General Issues: fixed

Issue Description
164700 This release fixes the incorrect CAL file name issue which caused the "cloud unit
not available" message.

173016 This release fixes the restart panic which occurred after data movement and
during an in-progress deletion.

178630 This release frees memory allocations during SMS.Memstat logging.

187236 The web GUI DDSM file system daily written chart is now shown correctly after
DD OS upgrade to 6.0.1.0.

196239 This release corrects an issue where CAL_UNAVAIL event may occur while the
file is not scheduled for migration yet.

198894 This HA BATS/PATS issue was resolved so that the restart occurs after reboot
within time parameters.

200628 This fix in this release includes a strong passphrase check when user enables
encryption.

200772 DD OS This fix corrects a deadlock situation while performing the

fmig_mtree_disable command.

201870 DD OS This release fixes a sizing-related computation that occurs during

sanitation.

201887 This release addresses the issue which produced incorrect "Pre-Comp"
statistics.

Fixed in version 6.0.2.20 - 587212 31

Release Notes

Table 23 DD OS 6.0.2.20 General Issues: fixed (continued)

Issue Description
207771 This release fixes the system panic caused previously when the user connects
with token authentication.

Table 24 DD OS 6.0.2.20— Networking Issues: fixed

Issue Description
200218 This release fixes synchronization issues which may cause used one CPU to wait
for a lock request although received by a different CPU.

Table 25 DD OS 6.0.2.20— Platform Issues: fixed

Issue Description
190882 This release fixes the platform issue which may cause a continuous timeout.

191182 The ELF specification has one extension mechanism for the case of large number
of mmap areas, the fix for this bug is to implement this extension.

198723 This release fixes the issue when using "se sms restart" from ddsh shell which
caused the SMS process to panic.

205571 This release enhances floating IP performance for HA.

205839 This release adjusts the temperature threshold for the Data Domain SAS-SSD
and SAS-HDD drives.

Table 26 DD OS 6.0.2.20 Replication Issues: fixed

Issue Description
197075 This release fixes an issue with AMS (automatic multi streaming) while using
VSR (virtual synthetic replication) optimization.

199179 This release fixes a segmentation fault in DDFS during AMS (automatic multi
streaming) replication.

199352 This release resolves an issue where a system could timeout during MFR and
Cloud Tier data movement.

202370 This release fixes an issue which can cause AMS (automatic multi streaming) to
be skipped for certain files.

204102 This release fixes the issue where using AMS (automatic multi streaming) caused
the Mrepl to panic.

Table 27 DD OS 6.0.2.20— VTL/vDisk/Fibre Channel Protocols Issues: fixed

Issue Description
200016 This release corrects the sequencing of locks on VTL, which now avoids an
unexpected VTL restart.

32 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Fixed in version 6.0.2.9 - 579709

This list contains important changes and fixes that are made to this version of DD OS.

Table 28 Security Updates in DD OS 6.0.2.9

Issue Description
194100 This release mitigates the Data Domain CIFS server vulnerability described per
CVE-2017-14385 (ESA-2017-157).

Refer to the Common Vulnerabilities and Exposures (CVEs) section for more
information about CVEs.

Table 29 DD OS 6.0.2.9— File System Issues: fixed

Issue Description
186976 This release resolves a potential HMON timeout that is caused by a deadlock
between fm_stream_get_stats and fm_readdirplus.

194353 This release fixes an issue with Cloud Tier access and migration, which could
cause a system to panic.

196382 This release fixes an issue with MREPL softlocks during multiple PCR schedules
jobs that could cause the Data Domain file system to panic.

196728 With this release, the MREPL restart cookie is now stored in a child key format
on the destination system.

199141 In this release, the data-movement throttle value does not reset when the
system restarts.

Table 30 DD OS 6.0.2.9— Networking Issues: fixed

Issue Description
190493 This release updates the client-group code to avoid a possible system panic
when streams are added.

198963 This release resolves a possible SMS core issue by reporting only the first 100
duplicate IPs.

199465 This release fixes the issue which caused degradation of NFS write performance.

Table 31 DD OS 6.0.2.9— Platform Issues: fixed

Issue Description
188587 This release fixes an issue where a single disk may fail during a superblock
update.

195120 This release fixes an issue where new High Availability (HA) configurations
experienced issues with syncing that could cause a system to panic.

197387 With this release, all PCR schedules are now automatically disabled when a Data
Domain system is converted to CREPL destination.

Fixed in version 6.0.2.9 - 579709 33

Release Notes

Table 32 DD OS 6.0.2.9— Replication Issues: fixed

Issue Description
195289 This release enables a source system to handle a fan-out error without using
recipe optimization.

198031 This release resolves an issue where certain files using MFR with backup
applications could not replicate.

199019 This release fixes an issue where AMS-MREPL did not work after an upgrade to
6.0.2.001.

199439 This release fixes a possible lag issue during MTree replication.

Fixed in version 6.0.2.0 - 575017

This is a listing of important changes and fixes that are made to this version of DD OS.

Table 33 DD OS 6.0.2.0— Security Updates

Issue Description
174677 This release mitigates the local privilege escalation issue per CVE-2016-5195,
also known as the “Dirty Cow” vulnerability.

Refer to the Common Vulnerabilities and Exposures (CVEs) section for more
information.

Table 34 DD OS 6.0.2.0— CIFS/NFS Issues: fixed

Issue Description
175909 This release fixes an issue where a new CLI or GUI session could not be opened
due to SMS becoming unresponsive. For more information, see KB article
#503298.

176851 This release fixes an issue with user accounts not being able to create files or
folders in locations they have been granted permission to do so.

181336 This release now gracefully handles the error condition when the ntStatus =
STATUS_NOT_SUPPORTED, which may otherwise cause a system to panic.

182198 This release fixes an issue where DB2 Restore could fail after upgrading to DD
OS 5.7.

182997 This release resolves an issue where the reported cleanable space on the active
tier is larger than the total space available.

184371 This release fixes a bug with the loop counter which could result in copying to an
invalid memory, which may cause the system to panic.

Table 35 DD OS 6.0.2.0— DD Boost Issues: fixed

Issue Description
175124 This release fixes an issue where SMS failed to initialize after an upgrade.

34 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 35 DD OS 6.0.2.0— DD Boost Issues: fixed (continued)

Issue Description
183310 This release corrects the DD Boost handles an NFS_Stale_Handle error during a
Synth Write. The job is now correctly removed for the queue, and the client is
notified of the error.

184912 This release allows for a DFC client connection to the source and target Data
Domain system.

Table 36 DD OS 6.0.2.0— File System Issues: fixed

Issue Description
143948 This release prevents a race condition with Garbage Collection (GC) and no
longer results in possible false missing segment issues.

146109 This release resolves an issue where a race condition may send a session delete
request before all the open files of the session are closed, which could result in a
panic.

165081 With this release, a notion of priority among running compacts is allowed in order
for a higher priority compact can abort a lower priority compact that might be
running.

167410 This release fixes an issue where a system may panic during a MTree or snapshot
deletion or a system shutdown.

169150 This fix increases the timeout for cloud related IO to a configurable value
(default 15 minutes).

170800 This release corrects an issue where NVRAM runs out of space, resulting in an
HMON timeout.

171047 This release fixes the issue where Data Domain systems that are enabled for DD
Cloud Tier could experience file system panics when a cloud unit is filled to
capacity.

171925 This release fixes the issue which caused backups to panic with NBU
Accelerator.

172377 This release fixes an issue where dmck -- -r -m <mtree_name> loops while
performing dmck_dm_mtree_rollback test.

174302 This release fixes a performance regression, which caused an imbalance in the
way streams get bound to CPU domains. The CPU domain selection algorithm
has been modified to accommodate this type of workload.

175046 This release resolves an issue where a Data Domain file system restart and cause
a panic due to a deadlock issue.

176331 This release fixes the issue in which intensive snapshot operations and Resclnt ID
could leak.

176957 This release has a dedicated SD cache for each MTree.

177871 This release resolves an issue where the file system may restart and cause a
system panic.

177948 This release fixes incorrect comparison of CC Partition type in various places
across the Data Domain file system.

Fixed in version 6.0.2.0 - 575017 35

Release Notes

Table 36 DD OS 6.0.2.0— File System Issues: fixed (continued)

Issue Description
178192 This release fixes a CIFS backup issue that may occur after upgrading a Data
Domain system to DD OS 6.0.0.21.

178218 This release fixes an issue where the SMS process may fail and log a PANIC.

178690 This release addresses the issue in which CIFS user may inadvertently delete
files on the Directory Replication destination.

179531 This release fixes an issue where sfs_dump was very slow (dumping only 22–25
files per second).

179644 This release fixes an issue where a Data Domain system with Extended Retention
(ER) may panic after a headswap.

179847 This release resolves an issue where scheduling multiple PCR pathsets in the
same MTree may fail after the first three pathsets.

180050 This release fixes an issue where the Data Domain file system may stop
responding during shutdown or cause an issue with DD Cloud connectivity, which
may cause a panic.

180134 In this release, there is a check against "max values" instead of "default values."

180325 This release fixes an issue with Apache and imported certificates, which could
result in a 404 error.

180345 This release fixes a race condition with low free page, which may cause a system
to panic.

180566 This release fixes an issue with a transient missing segment that is written to
disk.

180886 This release resolves an issue where CIFS File Permissions Applied Incorrectly to
New Backup Files after DD OS 5.7.4.0 Upgrade.

180960 This release resolves an issue with the Data Domain file system's allocated
memory that could interrupt an NFS or DD Boost backup and cause a system
panic.

181246 This release fixes an issue where changing the file permission of a special file
after it is fast copied may cause a system to panic.

181509 This release fixes an issue where reg_async daemon panics under stress.

181518 This release fixes an issue when Garbage Collection (GC) on DD Cloud is aborted
and could cause a system to panic.

181868 This release resolves an issue where a container write stops responding while
retrieving an error from DD Cloud while other containers go through to disk,
which may cause a system to panic.

182189 In this release, the index now purges all dead entries, which otherwise may cause
a file system to become read-only or cause a system to panic.

182199 This release fixes an issue where a system may panic after an upgrade to 6.0.1.0
from 5.6.x.x. See KB article 497451 for more information.

182444 This release fixes an issue on Data Domain systems with Index on SSD capability
that may stop responding during READ operations.

36 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 36 DD OS 6.0.2.0— File System Issues: fixed (continued)

Issue Description
182811 Newly created empty folders now have the "modified time" parameter.

183970 This release corrects an issue where FMIG ran with fewer threads when the
"space full" condition is reached.

183969 This release resolves a race condition between ingest and Garbage Collection
(GC) which could cause newly ingested segments to be mistakenly deleted,
resulting in data loss and a file system panic.

184227 This release corrects an issue where continuous segfaults occurred during
MREPL.

184681 With this release, some log messages are now "conditional" and have new
troubleshoot levels to decrease workloads.

185354 This release fixes an issue where the Data Domain file system may become
unavailable during background scrub activity.

186500 This release corrects an issue with the displayed MTree REPL count. The
completed count is now in sync with the remaining amount shown.

188220 This release resolves an issue where segments that are identified for cleaning
should not be deleted due to a timing mismatch.

188403 This release fixes an issue where Garbage Collection (GC) on DD Cloud schedule
is set to "0," which could cause a system to panic.

189551 This release fixes an issue with MTree replication from DD OS 6.0.1.10 to DD OS
5.7.3.0, which could cause a system to panic.

189855 This release corrects an issue with DD Cloud cleaning efficiency.

190199 This release fixes an issue with the file system is restarting during analysis phase
of Garbage Collection (GC) on DDOS 6.0 and later with Perfect Physical
Garbage Collection (PPGC) enabled. See KB article #502133 for more
information.

191017 This release fixes an issue where an index rebuild post headswap may fail when
upgrading from a smaller capacity system to a larger one. For more information,
see KB article #502789.

191941 This release fixes an issue where an Avamar rollback could take several hours to
complete fastcopy.

192115 This release ensures that the buffers are free before PCR job abort is complete.

192165 This release fixes an issue where a race condition between Garbage Collection
and Segstore may cause a system to panic.

192693 This release fixes an issue where a DD9300 may panic when the Data Domain
system is near full and PPGC is initiated.

192814 This release moves the key rotation policy registry from config namespace to
config_master namespace so only one registry is present for key rotation.

194675 This release no longer captures excessive DM logging messages.

Fixed in version 6.0.2.0 - 575017 37

Release Notes

Table 37 DD OS 6.0.2.0— General Issues: fixed

Issue Description
151880 This release increases the DH parameter length to 2048 prime for Apache-
Tomcat.

183068 This release fixes an RPC scheduling issue.

184377 This release fixes an issue where client-stream VS stream information may
fluctuate up and down and flood ddfs.info with start/stop messages.

189193 This release fixes an observed segfault at dd_fmig_monitor while suspending

data movement.

189688 a This release has the font "Roboto" bundled within the application.

190357 a Historical charts and topology charts can now be rendered in IE-11.
a. This issue is resolved only in instances where the Data Domain System Manager is running directly from DD OS
6.0.2.0 and not from DD Management Center.

Table 38 DD OS 6.0.2.0— Networking Issues: fixed

Issue Description
176738 This release makes registry entry persistent across reboots and avoiding a
system panic.

179200 This release fixes an issue where a system may panic during or after a UDP
communication during Avamar replication.

183072 This release resolves an issue with an assigned interface DHCP addresses that
are configured during failover after a DD OS upgrade to 5.7.4.0.

185984 This release fixes an issue where SNMP continuously cores when trying to read
enclosurePackTable.

188056 This release resolves a routing issue that could occur when two or more local IPs
are in the same subnet as the destination IP by internally using source IP routing.

Table 39 DD OS 6.0.2.0— Platform Issues: fixed

Issue Description
172092 This release resolves an issue where an upgrade from DD OS 5.6 to DD OS 6.0
may fail.

176572 This release now reports when a PCR job cannot complete or fails. An error is
returned for each failed task.

177754 This release fixes an issue where a corner case of HBA reset could cause a kernel
panic.

178539 This release fixes the FPU issue which caused kernel panic.

179574 This release fixes the issue which caused a reference counter to overflow and
caused kernel panic when the number of IOs to an array exceeds 4.2 billion.

180780 With this release, a spare drive fails instead of triggering Copy Reconstruction,
which otherwise could pose a data corruption risk.

38 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 39 DD OS 6.0.2.0— Platform Issues: fixed (continued)

Issue Description
182968 a This fix allows the customer to see storage related information in GUI.

183255 In this release, if the Data Domain file system does not respond, an error is
reported.

185559 This release fixes an issue where systems with ES20 enclosures and certain
ES30 SATA drives could not previously upgrade to DD OS 6.x.

186427 This release frees allocated memory that is used after returning information to
the SML layer to avoid possible memory allocation failures.

190681 a This release now allows for up to four letters in time zone abbreviations.

190991 a This release now displays the "failed disk count" on the dashboard.

191758 This release upgrades Apache Tomcat to version 7.0.55 and resolves an issue
with GUI availability.

192978 This fix corrects the issue of system shutdowns due to incorrect thermal
reporting on the DD9500 and DD9800 systems.
a. This issue is resolved only in instances where the Data Domain System Manager is running directly from DD OS
6.0.2.0 and not from DD Management Center.

Table 40 DD OS 6.0.2.0— Replication Issues: fixed

Issue Description
166996 This fix checks for the situations when a source is being asked to rollback and
now disallows the rollback. The user should not encounter any panics as a result
of such situations.

176907 This release corrects an issue with the CREPL "remaining bytes" reporting.

179785 This release no longer shows an alert like "No contact with replica" for MREPL.
MREPL connects and disconnects the connection at the end of every snapshot
that is replicated, and there is no connection problem between replication source
and destination in this instance.

180867 This release reduces the registry update time to every 5 minutes.

181295 a This release corrects a display issue with the Replication Performance Graph
under Automatic Replication Summary. This update also allows for this view to
launch from Topology graph.

182101 This release reduces the logging when MFR fails, which could otherwise cause a
system to panic.

183457 This release reduces the lock contention on nfc mutex.

184798 This release fixes an issue where the backup send filecopy hits RPC may cause a
system panic.

185171 This release prevents a race condition between a close thread and a fan-out
thread, which could otherwise cause a system to panic.

185464 This release does not save the basefile when basefile filecopy
close rpc fails.

Fixed in version 6.0.2.0 - 575017 39

Release Notes

Table 40 DD OS 6.0.2.0— Replication Issues: fixed (continued)

Issue Description
186110 This release checks if the start/end of a recipe is on a split reference.

187333 This release allows for a DD Boost storage unit to be renamed on the destination
system during MFR.

187681 a This release fixes an issue where an Invalid UUID error is displayed during
replication after an update to DD OS 6.0.1.x.

189435 a This release fixes an issue with the Replication Prediction graph display. For
more information, see KB article #502793.

189836 This release checks the base snapshot or incremental snapshot for a zeroed out
basefile and prevents its inclusion as part of find_base rpc.

192194 This release now supports MTree Replication with Low Bandwidth Optimization
enabled. See KB article #502498 for more information.

195375 This release changes the updated the Automatic multi-streaming (AMS) for
MTree Replication algorithm.

195772 This release resolves an issue where MTree replication destination during MRepl
may panic.
a. This issue is resolved only in instances where the Data Domain System Manager is running directly from DD OS
6.0.2.0 and not from DD Management Center.

Table 41 DD OS 6.0.2.0— VTL/vDisk/Fibre Channel Protocols issues: Fixed

Issue Description
175259 This release resolves an issue where some tape devices on NetWorker could
show "error reading: Device busy." Data transfer on these devices is no longer
broken.

184546 This release fixes an issue where a scheduled backup job could have been
interrupted due to a connection failure between the Data Domain system and
client.

184924 This release avoids running two VTL instances simultaneously, which may
otherwise cause a system to panic.

188496 a This release considers only pool names that belong to the same Data Domain
system and are considered for the delete eligibility check.

189597 This release fixes an issue where an error could occur with Fibre Channel HBA
firmware, which could cause a system to restart.
a. This issue is resolved only in instances where the Data Domain System Manager is running directly from DD OS
6.0.2.0 and not from DD Management Center.

Fixed in version 6.0.1.30—570211

This is a listing of important changes and fixes that are made to this version of DD OS.

40 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 42 DD OS 6.0.1.30— File System Issues: fixed

Issue Description
182189 In this release, the index now purges all dead entries, which otherwise may cause
a file system to become read-only or cause a system to panic.

192165 This release fixes an issue where a race condition between Garbage Collection
and Segstore may cause a system to panic.

Fixed in version 6.0.1.20 - 567551

This is a listing of important changes and fixes that are made to this version of DD OS.

Table 43 DD OS 6.0.1.20— File System Issues: fixed

Issue Description
171925 This release fixes the issue which caused backups with NetBackup Accelerator
to panic.

177948 This releases fixes incorrect comparison of CC Partition type in various places
across the Data Domain file system.

179531 This release fixes an issue where sfs_dump is very slow, dumping only 22-25
files per second.

180960 This release resolves an issue with the Data Domain file system's allocated
memory that could interrupt a NFS or DDBoost backup and cause a system
panic.

184681 With this release, some log messages are now "conditional" and have new debug
levels in order to decrease workloads.

188220 This release resolves an issue where segments identified for cleaning should not
be deleted due to a timing mismatch.

Table 44 DD OS 6.0.1.20— General Issues: fixed

Issue Description
184377 This release fixes an issues where client-stream VS stream information may
fluctuate up and down and flood ddfs.info with start/stop messages.

Table 45 DD OS 6.0.1.20— Replication Issues: fixed

Issue Description
176907 This release corrects an issue with the CREPL "remaining bytes" reporting.

184682 With this release, some log messages are now "conditional" and have new debug
levels in order to decrease workloads.

184798 This release fixes an issue where backup send filecopy hits a remote
procedure call (RPC) and may cause a system panic.

185171 This release prevents the race condition between a closed thread and a fanout
thread, which may cause a system to panic.

Fixed in version 6.0.1.20 - 567551 41

Release Notes

Table 45 DD OS 6.0.1.20— Replication Issues: fixed (continued)

Issue Description
185464 This release does not save the basefile when basefile filecopy close
rpc fails.

189836 This release checks the base snapshot or incremental snapshot for a zeroed out
basefile and prevents its inclusion as part of find_base rpc.

Fixed in version 6.0.1.11 - 561979

This is a listing of important changes and fixes that are made to this version of DD OS.

Table 46 DD OS 6.0.1.11— File System Issues: fixed

Issue Description
183969 This release resolves a race condition between ingest and Garbage Collection
(GC) which could cause newly ingested segments to be mistakenly deleted,
resulting in data loss and a file system panic.

Fixed in version 6.0.1.10 - 561375

This is a listing of important changes and fixes that are made to this version of DD OS.

Table 47 DD OS 6.0.1.10— CIFS/NFS Issues: fixed

Issue Description
181336 This release now gracefully handles the error condition when the ntStatus =
STATUS_NOT_SUPPORTED, which may otherwise cause services through CIFS
protocol to be unavailable.

Table 48 DD OS 6.0.1.10— File System Issues: fixed

Issue Description
181509 This release fixes an issue where reg_async daemon panics under stress.

182199 This release fixes an issue where a system may panic after an upgrade to 6.0.1.0
from 5.6.x.x. See KB article 497451 for more information.

183969 This release resolves a race condition between ingest and Garbage Collection
(GC) which could cause newly ingested segments to be mistakenly deleted,
resulting in data loss and a file system panic.

Table 49 DD OS 6.0.1.10— General Issues: fixed

Issue Description
179746 This release fixes the issue after filesys restart, where the ifgroup stops
forwarding clients to ifgroup IP. The fix performs ifgroup initialization prior to the
first time ifgroup is used.

42 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 50 DD OS 6.0.1.10— Networking Issues: fixed

Issue Description
176738 This release makes registry entry persistent across reboots and avoiding a
system panic. See KB article 492781 for more information.

Table 51 DD OS 6.0.1.10— Platform Issues: fixed

Issue Description
178539 This release fixes the FPU issue which caused kernel panic.

179574 This release fixes the issue which caused a reference counter to overflow and
caused kernel panic when the number of IOs to an array exceeds 4.2 billion.

182968 Storage related functions now work through both the GUI and the CLI.

Fixed in version 6.0.1 - 556307

This is a listing of important changes and fixes made to this version of DD OS.

Table 52 DD OS 6.0.1— CIFS/NFS Issues: fixed

Issue Description
165968 The fix includes a CIFS option which if set, will avoid the query to the forest root
global catalog which previously caused the CIFS AD user authentication to panic.

168462 The fix allows share access to trusted domain local groups that are added to the
share's user properties.

168813 The fix added error logs in AD_ReloadJoinedDomains code path.

175787 With this fix, newly created folders in CIFS share after upgrading to DDOS
5.7.3.0 are now accessible .

176734 This release fixes the CIFS issue which would cause CFS panic if a join operation,
joining a DDR to an Active Directory domain, took longer than 90 seconds.

Table 53 DD OS 6.0.1— DD Boost Issues: fixed

Issue Description
166988 For this release, the migration policy is not removed during ddboost storage-unit
delete.

168767 The fix rearranges code to prevent a deadlock between open_file and
_destroy_lsu_ and added a threshold timer to prevent abandon checks on all file
opens.

170139 The fix allows the system to perform backup using token authentication with
path/permissions configured which previously caused memory to panic.

172436 This release fixes the Avamar issue which caused a file to be deleted without
customer triggering it and without customer knowing it was deleted.

Fixed in version 6.0.1 - 556307 43

Release Notes

Table 53 DD OS 6.0.1— DD Boost Issues: fixed (continued)

Issue Description
172488 The current plugin builds from 6.0.1 and 6.1 had a race that prevented
simultaneous connections from succeeding. This change repairs the race and re-
enables PAM.

Table 54 DD OS 6.0.1— File System Issues: fixed

Issue Description
141630 This release corrects an issue with an inaccurate stream count in the system
show performance CLI command.

145221 This release fixes the SegStore issue which caused NVRAM panic.

157142 This fix ensures one user cannot transfer files to other user's home directories
using SCP.

157839 This fix ensures that Mtree cannot be modified to a storage-unit when the
customer replicates Mtree from node1 to a storage unit in node2.

163831 This release fixes the issue in which a user would experience an error while
passing a file name that includes ":" in "archive report generate file-location path
[path]"

164468 This release fixes the issue in which skewed IO's to particular shelves resulted in
slow IO completion.

164658 This fix reduces partial containers on DD VE with NBU or BoostFS. The partial
containers were generated due to frequent commits on unstable streams. The
solution involves detecting frequent commits in Segstore, and turning the
corresponding streams into stable streams. Please see KB article #485457.

166578 The fix addresses the issue which caused DDFS panic in GC because Index
doesn't return all the FPS belonging to GC working set when there were
workloads with too many duplicate FPS.

167348 This fix allows space to be reclaimed in /ddvar after file removal via CIFS/NFS.

167647 This release corrects the error message which previously did not indicate when
an Mtree was created.

168025 This release fixes the file system issue related to dereferencing a null pointer
which caused the system to panic.

168052 The user no longer sees incorrect time information when recalling status.

169182 This release fixes the issue which caused the system to log every process on
restart when the sytem is upgraded from 5.7 to 6.0.

169571 This fixes the random IO isssue which caused poor performance on destination
Mtree.

170305 This release fixes the issue which occurred while upgrading from DD OS 5.2 or
previous system to 6.0, causing no GUI to appear for customer interaction.

170561 This fix ensures that after an upgrade, "passwords-remembered" and "max-
days-between-change" are maintained if user is upgrading from DD OS (version
>= 5.6) to "5.7.3" or "6.0.1".

44 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 54 DD OS 6.0.1— File System Issues: fixed (continued)

Issue Description
170583 This release fixes the issue in which a CIFS attempt to open a Mtree with DOC
flag set caused the system to panic.

170678 This release fixes the 6.0 issue which caused the customer to face core panic
with a cloud GC run.

170679 This change adds a locking mechanism in the DDFS SMT cache, to protect the
cache with read-write lock. This allows the cache to be read simultaneously by
multiple threads but write by only one thread, and eliminates multiple threads
trying to write duplicate entries to the cache.

171072 This release fixes the retention unit sealing operation on Extended Retention
systems to prevent special file names from being incorrectly populated.

171163 This release fixes the issue in which lock contention issue causes the HMON
panic.

171194 This fix avoids leaking LP containers during GC copy forward.

171264 This release fixes the stats display to include disabled and disconnected cloud
units.

171378 This fix provides new check in cloud unit addition logic to prevent cloud unit
addition to cause system panic if the external key manager is enabled.

172078 This fix disables the elevation of privilege which was possible during
session_create when cert_based user auth was enabled.

172249 Encryption keys are now exported to the cloud. A new option has been added to
ddr_keys_util to recover/import the exported keys from cloud.

172480 This release fixes an incorrect_verify and removes a case where requests could
be reordered when split-refs are present.

Table 55 DD OS 6.0.1— General Issues: fixed

Issue Description
170468 This fix corrects duplicate labels so that customers will not see duplicate x-axis
labels if data is below 4 for FS ops and DD Boost connection's real time charts.

172481 Client-group feature will now properly initialize on an HA system with rolling
upgrade.

174476 This release fixes the DD VE issue which caused GC system panic.

175661 This release fixes the RPC issue which caused the TCP connections to remain
open.

176892 This release fixes the issue which resulted in the interruption in data-movement
upon every UNAVAIL event. The fix is to automatically restart data-movement
upon receiving AVAIL event.

Table 56 DD OS 6.0.1— Networking Issues: fixed

Issue Description
168562 This release captures all tcp.log files instead of only the first two.

Fixed in version 6.0.1 - 556307 45

Release Notes

Table 56 DD OS 6.0.1— Networking Issues: fixed (continued)

Issue Description
170415 This release fixes the issue which allowed the SMT gateway to be used as static
gateway (if the gateway was set before upgrade to 6.0).

Table 57 DD OS 6.0.1— Platform Issues: fixed

Issue Description
160125 This fix allows NVRAM driver upgrade without need to perform DDOS upgrade.

160844 This fixes the DFC drivers issue which caused the system to panic previously
when the system was very busy.

166789 This release fixes that issue that caused a rolling upgrade to fail on an HA system
when external enclosure firmware updates were needed.

168765 This fix prevents the incorrect alert "EVT-STORAGE-00026" after DDR upgrade
to 6.0.

169090 This release fixes the issue which caused DDFS panic due to malloc fail.

169277 This release fixes the problem in which the system boots up with incorrect
password with shadow files after headswap causing the system to be
inaccessible.

169980 This release addresses the platform issue which caused the kernel to panic.

170417 This release addresses the platform issue which caused slow GUI response."

171105 This release fixes the issue in which multiple DDFS threads open a single file
concurrently, causing the DDFS to hang after panic.

171935 This release changes the rotation of the hdc_data.log from daily to size-based
100M.

171985 The fix for this release removed the production public key on productions system
for both fresh install in manufacturing and upgrade versions.

172453 The fix in this release prevents CIFS user deleted files on drepl destination.

176871 This release fixes the memory issue which caused the kernel to panic.

Table 58 DD OS 6.0.1— Replication Issues: fixed

Issue Description
157827 This release fixes the replication issue which caused keys to be sent in a non-
FIPS compliant manner.

165092 This release fixes the issue which caused degraded performance when using
CIFS with large MTU (a feature in new SMB 2.1 and which is supported only in
5.7).

169636 This change in this release reduces retry attempts in nfc_status() if the filecopy
ctx is done and released but the nfc task is not yet released.

170222 This release fixes an issue which caused Collection Replication stalls when
replicating large datasets.

46 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 58 DD OS 6.0.1— Replication Issues: fixed (continued)

Issue Description
170443 Instead of causing system to panic, this release returns the basefile not found
error when the basefile open fails with EEXIST and there is no entry in the
basefile hash.

171468 This fix is to check if ent_cnt is not zero, then check if stream is available and
mark the stream availability after allocating the stream.

173925 This release fixes the Replication issue that hindered autosupport reports.

175164 This release fixes the Directory Replication issue which caused inaccurate alerts

Table 59 DD OS 6.0.1— Security Issues: fixed

Issue Description
161065 This fix addresses the security issue which occurred during file migration.

161984 This fix addresses the security issue which was related to session IDs and users
with higher privileges.

164387 This releases fixes the issue caused when using "sys-internal."

165177 This fix addresses vulnerability due to weak key size certificates.

167096 This release fixes the issue in which response time for error message was same
for both non-existent user and valid-username/incorrect-password combination.

167742 This fix address platform security issues.

170775 This release fixes the security issue related to denial of service CVE-2016-6515.

172219 This fix addresses the DDSH security issue.

172710 This release fixed security vulnerabilities that remained exposed in openssl
package.

172914 This release fixed security vulnerabilities in the GUI.

174923 This release fixes DDSH security issue.

171576 This fix ensures that Retention Lock cannot be set to DDBOOST file in DSP
mode during data ingest. The client will receive an error while locking the file
under ingest over DDBOOST in DSP mode.

Fixed in version 6.0.0.30 - 550720

This is a listing of important changes and fixes made to this version of DD OS.

Table 60 DD OS 6.0.0.30— DD Boost Issue: fixed

Issue Description
175684 This release fixes the NetWorker usage issue with ftruncate() which caused the
DD and HA pairs to panic.

Fixed in version 6.0.0.30 - 550720 47

Release Notes

Table 61 DD OS 6.0.0.30— File System Issues: fixed

Issue Description
172453 This release addresses the issue in which CIFS user deleted files on Directory
Replication destination.

172480 This release fixes the issue in which overwrites to virtual synthetic files caused
the customer experience DD file system panic.

175640 This release fixes the issue in which DD cloud tiering from Avamar could not be
enabled.

175751 This release fixes the MTree replication issue which caused system to panic.

Table 62 DD OS 6.0.0.30— General Issue: fixed

Issue Description
174362 This release fixes the storage add issue during volume assembly in HA
environment.

Table 63 DD OS 6.0.0.30— Replication Issue: fixed

Issue Description
173925 This release fixes the issue where autosupport generation failed on systems with
significant use of managed file replication.

Fixed in version 6.0.0.21 - 549019

This is a listing of important changes and fixes made to this version of DD OS.

Table 64 DD OS 6.0.0.21— Replication Issue: fixed

Issue Description
173925 This release fixes the issue where autosupport generation failed on systems with
significant use of managed file replication.

Fixed in version 6.0.0.20 - 547375

This is a listing of important changes and fixes made to this version of DD OS.

Table 65 DD OS 6.0.0.20—DD Boost issues: fixed

Issue Description
170139 This release fixes the issue which caused memory maps to panic.

Table 66 DD OS 6.0.0.20—File system issues: fixed

Issue Description
166922 This release now supports Cloud QoS on 16 TB DD VE configuration.

48 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 66 DD OS 6.0.0.20—File system issues: fixed (continued)

Issue Description
170305 This release allows host certificates to be regenerated during Java upgrade.

Table 67 DD OS 6.0.0.20— Platform Issues: fixed

Issue Description
147658 This release allows for data collection and additional fields/counters to be
collected for QoS.

169114 This release corrects counting of active disk group (DG) by only counting active
DG and not the cache tier DG.

170500 This release allows the user to create HA pairs on EOS T4.

Table 68 DD OS 6.0.0.20— Replication Issue: fixed

Issue Description
59903 This release fixes the issue in which MTree replication contexts containing
significantly large amounts of data to be configured and the contexts to be
initialized on a Data Domain system, incorrectly showed ERROR status to those
contexts in the Data Domain System Manager.

170222 This release fixes an issue which caused collection replication stalls when
replicating large datasets.

Fixed in version 6.0.0.9- 544198

This is a listing of important changes and fixes made to this version of DD OS.

Table 69 Security Updates in DD OS 6.0.0.9

Issue Description
170767 In this release, the CIFS test no longer hangs or returns Permission
denied when running the scp autosupport.sub command.

Table 70 DD OS 6.0.0.9—File system issues: fixed

Issue Description
147553 This fix will give engineering and support more information when missing
segment issues are detected in the field.

167690 This release fixes an issue with DD9500 shelf migration preparation that
previously could have caused a system to panic.

169002 With this release, the cloud unit should be created with minimum of tier size and
licensed size instead of only licensed size.

171194 This fix avoids leaking LP containers during GC copy forward.

Fixed in version 6.0.0.9- 544198 49

Release Notes

Table 71 DD OS 6.0.0.9— General Issue: fixed

Issue Description
132459 This release restores the old code for KERN.INFO section and moves the
misplaced info to the correct position.

167756 This release resolves an issue with FMIG on MREPL destination and opening the
cs stream, which could cause a system to panic.

Fixed in version 6.0.0.5-543356

This is a listing of important changes and fixes made to this version of DD OS.

Table 72 DD OS 6.0.0.5— CIFS/NFS: fixed

Issue Description
166220 This release resolves an issue where CIFS backup jobs could not run all at the
same time, causing sporadic job failures.

168055 This release removes obsolete CIFS code related to/ddr/var/cacerts and
updates the permission of that directory to 755.

Table 73 DD OS 6.0.0.5— DD Boost issues: fixed

Issue Description
139314 In this release, OpenSSL has been upgraded to version 1.0.1n.

163858 A registry has been added in DD OS to specify the minimum TLS version that DD
Boost can use.

165020 DD Boost now handles cases where FM could return DD_ERR_STALE from a
readdirplus function call.

170077 This release fixes an issue where a user may accidently enter bash mode from
DDSH.

Table 74 DD OS 6.0.0.5—File system issues: fixed

Issue Description
162450 This release fixes an issue where GC cannot run due to a coring condition, which
may cause the system to panic.

165427 In this release, Active Sync is not serialized behind Cloud Sync, which could
otherwise cause the system to panic.

166493 This release resolves the issue where a system may panic due to a HMON or
RPC timeout.

167664 This release fixes the issue where a system may panic during Avamar replication
(synthetic).

167882 The cleaning schedule and finish time in the CLI now syncs with the Web GUI.

167947 This release properly updates the "append notify" counters during error
handling.

50 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 74 DD OS 6.0.0.5—File system issues: fixed (continued)

Issue Description
169820 This release does not allow modification of ECS cloud profile endpoint.

Table 75 DD OS 6.0.0.5— General Issue: fixed

Issue Description
38969 The SHA-256 signature algorithm is used while generating certificates in this
release.

156900 In this release, the grub.conf password has been changed.

168482 The MTree GUI page now shows the Active Tier type.

168534 In this release, the scp command can no longer be used to access any Data
Domain system internal files or to enter bash mode.

168638 This release converts client-group hostname to lowercase on CLI entry.

169629 This release replaces locality repair with physical locality repair in order to size
down PLR on low-end systems and avoiding a system panic.

170106 This release removes the DD OS version and build number information from the
http header.

Table 76 DD OS 6.0.0.5— Platform issues: fixed

Issue Description
164473 This release fixes a FW issue with ECC error reporting.

Table 77 DD OS 6.0.0.5— Replication issues: fixed

Issue Description
165117 This release fixes the issue where a race condition in Managed File Replication
(MFR) led to a system panic.

167905 This release resolves the issues where Virtual Synthetic Replication (VSR) could
not be disabled.

Table 78 DD OS 6.0.0.5— VTL/vDisk/Fibre Channel Protocols issues: fixed

Issue Description
167896 This release fixes an issue with static analysis, which may cause a system to
panic.

168031 In this release, devices are no longer incorrectly marked as in the "inactive" state
on the error path.

Fixed in version 6.0.0.2-541180

This is a listing of important changes and fixes made to this version of DD OS.

Fixed in version 6.0.0.2-541180 51

Release Notes

Table 79 DD OS 6.0.0.2 —File system issues: fixed

Issue Description
164801 This fix corrects a cloud write error on a cmeta container, which could cause
the system to panic.

166496 This release modifies the behavior of cpm_cp_info_from_handle() in order to

negate missing segments when Cloud CP is down.

Table 80 DD OS 6.0.0.2 — Platform issues: fixed

Issue Description
168597 This release disables the expanded configuration check on HA systems.

Fixed in version 6.0.0.1-538504

This is a listing of important changes and fixes made to this version of DD OS.

Table 81 Security Updates in DD OS 6.0.0.1

Issue Description
135883 The implementation of the Linux kernel's net filter connection tracking has
been updated in this release to mitigate vulnerability CVE-2014-2523.

139712 This release updates the implementation of the Transport Layer Security
(TLS) protocol to mitigate vulnerability CVE-2015-4000, the “logjam”
vulnerability.

142674 For this release, the OpenSSL implementation was updated to resolve the
following vulnerabilities:
l CVE-2014-8176
l CVE-2015-1788
l CVE-2015-1789
l CVE-2015-1792
l CVE-2015-1790
l CVE-2015-1791

157144 This release updates the to mitigate security vulnerabilities exposed in glibc
per vulnerability CVE-2015-7547. For more information, see Vulnerability
Note# 457759 for more information.

Refer to the Common Vulnerabilities and Exposures (CVEs) section for more
information about CVEs.

Table 82 DD OS 6.0.0.1— CIFS/NFS: fixed

Issue Description
133717 This release changed log rotate interval to once in 20 minutes. This is needed for
CIFS logs since CIFS logs grow quickly at higher log rates.

52 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 82 DD OS 6.0.0.1— CIFS/NFS: fixed (continued)

Issue Description
143629 The NFS server incorrectly adds and keeps track of non-existing MTrees as
invalid export paths.

146174 This release fixes the issue in which a DD OS upgrade could result in applying
incorrect access options to an NFS client due to an incomplete resolution of host
names. As a possible result, an NFS client that normally had read-write access to
a Data Domain system before the upgrade might have read-only access
afterwards.

146224 CIFS shares with invalid users in users field will not be upgraded and will be
missing. The fix is to recreate the share after an upgrade.

146742 Customers upgrading with joined domains may not see their domains in DDEM
after upgrade. The workaround is for the customer to rejoin.

152928 This release fixes the issue in which CIFS backup failure due to cache flushing.

153231 This release fixes the CIFS issue which may cause the CIFS log rotation to stop
working after viewing a compressed CIFS log.

153638 CIFS services will panic during join domain if the

"config_master.windows.persist_auth" registry key is used during join and unjoin
domain. This key is not needed for 6.0.

153693 This release fixes the issue in which backups were failing through CIFS. This
occurred when a backup was performed by a non-admin user other than the
non-admin user that created the backup folder.

154005 This release addresses the issue of read-only shares becoming writable after
upgrade. Read-only shares will remain read only after upgrade.

154014 The CIFS backup failure due to memory leak in the LWIO process has been
resolved in this release.

154721 This release addresses an issue where select groups or users for shares can be
left un-migrated during the upgrade process.

154738 After an upgrade, CIFS share clients configuration could not be loaded from the
registry. This issue has been fixed.

155493 This release fixes a bug causes a leak of connection objects, which upon
reaching the maximum connection limit, prohibits clients from opening new
connections over CIFS.

155872 This release fixes the issue in which CIFS shares's "enabled/disabled" states
were not preserved during an upgrade.

155990 This release fixes a CIFS issue which may cause the system to panic.

157018 This release fixes the inability to control use of no_root_squash on NFS exports.

158031 This release fixes the issue in which backups panic when the customer has max
connections for share set.

158927 This release fixes the issue in which the ddfs.info is spammed with host
resolution errors which causes panics during high workloads on highly utilized
Data Domain systems.

Fixed in version 6.0.0.1-538504 53

Release Notes

Table 82 DD OS 6.0.0.1— CIFS/NFS: fixed (continued)

Issue Description
159027 This release fixes the issue where the race condition lwsmd may cause a system
panic.

159807 On CIFS share access list, CIDR formar subnet mask now works after upgrade.
For more information, see KB article# 462957.

161294 This release adds additional logging to capture default loglevel information when
the error INVALID_SERVER_STATE is issued.

162058 Due to higher rate of incoming connections per sec, the Data Domain system
could not serve any CIFS authentication based requests, leading to the inability
to login or map shares. This release resolves this issue.

162843 This release fixes an issue where the CIFS process core due to dcerpc
association group overflow.

162960 A snapshot folder under the root directory has been created in this release.

Table 83 DD OS 6.0.0.1— DD Boost issues: fixed

Issue Description
127564 This release fixes the issue in which an RPC panic occurred during the SSL
reconnect of an ongoing job.

137939 This release changes DFC support in AIX to use a disk type device. Use the
following: CLI to adverte DFC Disk device type. ddboost fc group add
group-name device-set [count <count>] [endpoint {all | none
| <endpoint-list>}] [disk] Add DDBoost devices to a DDBoost
FC groupIf "disk" is not specified then default DFC device type ("Processor")
is added. Once a device type is added, we want to discourage changing it.
Hence, we do not provide option modifying the DFC device type via the
ddboost fc group modify <group-name> device-set command.
Additionally, the DD Boost fc group show detailed command shall show
information about the DFC Disk access group.

138024 This release fixes the issue in which a NetBackup AIR (Automatic Image
Replication) operation could fail because the Data Domain source system where
NetBackup AIR is running used more streams for the outbound replication
filecopy jobs than the destination Data Domain system was able to ingest.

143024, Veritas NetBackup previously reported bytes transferred as a value that is too
143043 large. The number of bytes transferred for an AIR filecopy is now correct.

143861 This release fixes the issue where NFS read/write displays OST_FH_PERM FAIL
message in error.

146349 Segfault could occur when clienthost name is not found in token.

146425 This release fixes the issue in which an EMC Avamar garbage collection client or
a Data Domain managed file replication client could fail to traverse the
directories correctly on the Data Domain system when the client was connected
to multiple servers running a combination of DD OS versions, including DD OS
6.0 and DD OS 5.7 or earlier.

54 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 83 DD OS 6.0.0.1— DD Boost issues: fixed (continued)

Issue Description
146540 This release fixes the issue in which the user's system would experience a file
system panic during a DDBoost backup when the client attempts to correct
certain fanout errors.

147873 This release fixes the issue in which incorrect MFR details for active jobs could
occur while using DD Management Center to monitor active MFR jobs.

152811 After a DD OS 5.5.x.x and 5.4.2.x upgrade, the Data Domain system is hard
coded to use an NFS_FILECOPY_TIMEOUT of 43200 (12 hours) for NetBackup
AIR. Even if the NFS_FILECOPY_TIMEOUT is set to a value larger than 43200,
the setting will not be honored and will default back to 12 hours. For some
environments, a 12-hour timeout may be insufficient, and a longer timeout will be
required. Refer to KB article# 182302 for additional information for this
workaround.

153126 The Data Domain file system could panic when CLI snapshots or mrepl are used
on an Avamar MTree.

153442 This release fixes an issue where DD Boost virtual synthetic backups may cause
the file system to panic.

154161 Multiple issues with the current AIX DFC device driver have been resolved.

155401 This release fixes the issue caused if an unsupported 2.5.0 or older OST plugin is
used with a 5.7 or greater. the Data Domain file system may panic in response to
a resolvefilename RPC.

157282 In this release, the system now checks if the storage-unit is also shared via CIFS
and will block the change if the CIFS share exists.

160211 This release fixes the SMS issue which cause the SMS to panic when active
streams are queried.

165239 Resolved issue bypassing the wild card encryption option. Setting is now
honored.

165852 This release fixes the issue where a system panic may occur if an AIR replication
is the first DD Boost job on a newly powered Data Domain file system.

Table 84 DD OS 6.0.0.1—File system issues: fixed

Issue Description
102486 This release fixes the issue in which a Data Domain system could incorrectly
report that cleanable data existed even after a garbage cleanup operation had
successfully completed.

102707 This release addresses the registry issue that caused system panic.

104660 Based on segstore read latency calculate the copy refs quota for the next copy
refs job on this stream, that we can complete within the NFS/HMON timeout.
Return this length to the copy refs caller so that they can use this feedback to
dynamically adjust the length of the include. The System Parameter
cs_copy_refs_async_quots is now set to a small value at the beginning.

105878 This release enables a customer alert when cleaning fails to start according to
schedule.

Fixed in version 6.0.0.1-538504 55

Release Notes

Table 84 DD OS 6.0.0.1—File system issues: fixed (continued)

Issue Description
112768 This release enables the command to force NTP update within the Data Domain
file system.

113538 This release fixes the issue which caused the networker to panic while doing a
rename operation.

130127 This release fixes the issue which caused a SCRUB to be in a suspended state
when a CP is selected.

135269 This release addresses th issue which caused GC copy speed to be slow.

136434 This release fixes the issue in which the field length was too short for the
certificate key when updating the database.

138353 This release fixes the segmentation fault issue which caused the Data Domain
file system to panic.

138456 This release fixes the issue in which a user wants to determine the SLFS details
of a number of corrupted ppart_offsets that exceeds 200.

139728 This release fixes the issue in which a headswap cannot be retried after a panic
or disruption the first time.

140268 This release fixes the issue in which any overwrite to the beginning of a backup
performed on a Data Domain system with the Extended Retention software
option enabled could cause incorrect data to be written and invalid data to be
read back.

141468 This release fixes the issue in which user would not experience stream thrashing
even while going beyond supported stream counts. This bug only impacted
certain systems such as DD620/DD640, etc. Now, with the fix, the user may
experience stream thrashing when stream count crosses the supported limit.

141831 This release fixes the CS page issue which caused slow performance and RPC
timeouts.

142450 This fix ensures that the flush that is triggered in the "not enough NVRAM
space" case also updates the MTree CH.

142912 This release fixes the issue in which virtual synthetic operations caused the file
system to panic.

142991 This release fixes the issue where the mtree undelete command would fail.

143754 FM no longer reports a failed permission check on the file create inside the
"oradnfs" MTree.

144035 This release fixes the issue which caused the Data Domain file system to panic in
a Data Domain system when too many sfs_clone related activities are triggered
via the DD Boost interface.

144181 This release fixes the issue in which a Data Domain system could not start a
storage migration process despite a successful migration pre-check because the
Volume Manager was not available due to a previous chassis upgrade to DD4200,
DD4500, DD7200, or DD9500.

144438 This release fixes the issue in which some peer Data Domain systems with the
Extended Retention software option enabled could experience multiple file
system panics after upgrading to DD OS 5.5.2.x or higher. This issue was related

56 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 84 DD OS 6.0.0.1—File system issues: fixed (continued)

Issue Description
to a file format change instituted in Extended Retention systems via the DD OS
upgrade in conjunction with RPC errors in the replication path.

144808 When GC reaches a set time limit, it will now stop and no longer core.

145844 Cache values now update to reflect the correct stats after a capacity expansion.

146104 This release prevents offline dmck from unnecessarily updating Utree content
handle and deadlocking the system.

146180 This fix allows setattr on symlinks (not setsize).

146747 This release fixes the issue in which SREC-FMIG was not migrating the final set
of files which spanned the archive-unit and caused the archive tier to panic.

146830 Pre-upgrade will no longer stop when registry check fails.

146934 This release fixes the issue in which the user's system panics when ddfs.info.1.gz
is manually uncompressed in /ddr/var/log/debug. After this change, the
support bundle will include ddfs.info.1.tmp in case compression is not completed
and the box panics. ddfs.info.1.tmp should be considered as a part of the log
files.

147138 This release fixes the issue in which file verification processes could cause the
DD OS file system to panic due to overflows of the file verification byte counter.
This could potentially occur when the system had a virtual synthetics workload
with a decent number of very large files.

148098 This release fixes the issue in which an overwrite on a hard link returned an
incorrect I/O error.

148573 This release fixes the issue where dd_ext_check_mount: can not stat /ddr/
ext.

148650 This release fixes the issue which caused a missing check output file with whole
path that was not in /ddr directory.

148972 This release fixes the issue in which the file system failed to shutdown cleanly
during an upgrade.

149540 This release fixes the issue where low-end Data Domain systems with little RAM
(including DD VE) may panic with message: sscb_reclaim_eligible: 5807: !
(total_cnt > target_free). See KB article# 486317 for more information.

149818 This release fixes the issue in which intensive snapshot operations and Resclnt ID
could leak.

150656 Panic could occur when using DD Boost and while doing multiple storage unit
(MTree) renames/deletes/creates.

150776 This release fixes the issue where the Windows client would not throw an error
when a RL file was deleted.

150912 This release fixes the issue which may cause the customer to experience files or
folders disappearing after a DD OS upgrade to 5.7.0.3. This bug appears during
optimization of file creation in very large directories. This causes the regression
for lookups on older MTrees created in release 5.1 or earlier.

Fixed in version 6.0.0.1-538504 57

Release Notes

Table 84 DD OS 6.0.0.1—File system issues: fixed (continued)

Issue Description
151165 This release fixes the issue where the Data Domain file system gets terminated
with signal 8, Arithmetic exception during Avamar GSAN metadata backup (or
cpbackups). The file system could fail to restart after multiple attempts after a
DD OS 5.7.0.3-507764 upgrade. The user may work around this issue by turning
off the Avamar GSAN metadata backups.

151795 This release fixes an issue where the Data Domain file system may panic during
NVRAM replay.

151823 This release fixes the issue in which the assistance root caused Data Domain file
system to panic in pcr_cache_consume_fm_op().

151826 A Data Domain file system panic could occur in fm_nsput() after upgrade to DD
OS 5.7.0.3.

151828 This release fixes the issue in which the Data Domain file system could panic and
mrepl doesn't complete.

152028 HMON panic could occur when DM Locality measurement is running under
certain conditions.

152685 This release fixes the issue in the file verification which may cause the system to
panic.

152770 This release fixes the issue where a system may panic due to the dd_panic_if()
in fms_clone_cb_new_item_file().

152891 This release fixes a file manager issue which may cause the system to panic.

152968 This release fixes the issue in which the logical replication could cause the
system to panic by allowing commands (link and rename) to occur outside the
replication context.

153144 This release fixes the issue that occurs if a customer is reading files from MTree
replication over a CIFS. This caused the file system to repeatedly panic.

153386 This release corrects an issue during Data Domain file system shutdown or
upgrade that may cause the system to panic.

155175 The customer may not be able to copy files from ddvar share via CIFS. The
workaround for this issue is to copy files from /ddr/var via scp or other
network copy utilities

155186 The file inode consumption alert is now generated when 250 million files is
passed on an MTree.

155256 This release fixes the issue in which the CPM scheduler may not schedule jobs
while waiting for Archive CP recovery, causing the system to panic.

155281 This release adds a filter in the _sms_user_list function to increase performance
of the user show list command.

155659 This release allows GC to preempt FMIG on Extended Retention (ER) systems,
which could otherwise result in the Active Tier reaching capacity too quickly.

155839 This release fixes the issue in which HA does not go to degraded mode when all
SAS cables are pulled out from standby. The system is in the false HA state,
while storage is not accessible from standby. All SAS cables should be pulled
from standby node

58 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 84 DD OS 6.0.0.1—File system issues: fixed (continued)

Issue Description
156822 This release addresses the issue in which Data Domain file system panics are
seen during fast copy operations.

157071 The contents of the root node of the B+tree and the contents of the internal
nodes are now synchronized.

157883 A new system parameter has been introduced in this release for the maximum
age threshold for data movement named "fmig_max_age_thres". FMIG can now
use the upper age limit threshold for selecting files for migration.

158374 This release fixes an issue where a user could not change the debug level and
debug mask dynamically using the script config_debug for the 64 bit mask values
in versions below and including 5.7.0.10.

158595 This release fixes the issue in which a system panics when a system aborts GC
while in the analysis phase and the index is not fully converted.

158698 This release resolves the issue in which SMS failed and the system panics.

158900 This release modifies the order in which the locks are taken during PCR btree
flush to avoid a system panic.

158909 This release fixes the issue that occurs if a customer is reading files from a
Collection Replication over CIFS. This causes the file system to repeatedly panic
as new primes are installed due to Collection Replication updates.

159226 This release fixes the issue which allowed the sysadmin user to enter two
different passwords during initial configuration.

159784 This release fixes the issue where in case of a remote client, race condition can
occur between fm_session_destroy_all() and fm_session_delete(), resulting in a
system panic.

160285 This release resolves the issue where DM was not maintaining a correct MTree
deletion state in-core.

160474 This release allows for sfs_dump with option -l on Extended Retention enabled
systems.

160499 This release now avoids an unnecessary CH update. For more information, see
KB article# 482920.

160919 The infinite loop issue in dd_cache_elem_evict() is now resolved.

162745 This release contains updates to cs_copy_refs_copy() and copy_refs_split.

165302 This release fixes an issue where the RD lock may not release, causing the
system to panic.

165540 This release fixes an issue with large directories where if a file is not found, it
tries to read every record in a directory, which causes the system to timeout.

Table 85 DD OS 6.0.0.1— General Issue: fixed

Issue Description
66831 This release adds hostname to alert summary emails.

96596 This release allows the user to test SNMP and other DD OS alerts.

Fixed in version 6.0.0.1-538504 59

Release Notes

Table 85 DD OS 6.0.0.1— General Issue: fixed (continued)

Issue Description
105794 In this release, dd_qostool no longer logs the error "The filesystem is not
responding" when the filesystem is not running.

116402 This release allows the UDP to mount a NFS share using UDP.

138591 This release fixes the issue in which an unnecessary syslog alert stating that an
indirect call is not allowed was generated because of a security scanner's
operations. In the case of the security scanner, the alert could be ignored.

140819 This release allows for a high stream count ingest without causing the system to
panic.

143048 The JRE has been upgraded to version 8u65 and corresponding changes have
been applied to the DD System Manager build and code.

144887 This release amends the firmware file and the upgrade rules to allow the drive to
be upgraded.

145155 A user can now add a wildcard client to any DD Boost ifgroup via DD System
Manager.

149274 This release fixes an NFS issue which may cause the system to panic.

154670 HMON timeout caused by deadlock between SegStore, NFS and Cron has been
resolved in this release.

154763 This release renames the "pre-" and "post-" comp labels in the GUI to Physical
and Logical Written.

155639 This release fixes the GUI issue that occurred when there is an Ifgroup conflict.

155995 In this release, system show uptime has been modified to show information
for only the active node of an HA pair; no file system uptime is shown on standby
node.

156074 Updates have been made in this release to am-email of standby node to not
show any file system related information.

156702 This release fixes the resource leak issue which caused the system to have
symptoms such as not able to open the maximum supported NDMP sessions.

159751 This release fixes a GUI timeout issue due to following the
config_master.web_svc_session_timeout registry entry. For more information,
see KB article# 480838.

159776 This release includes support for auto firmware upgrades for more HDD models;
model names that start with "HUS72" or "ST" or "HUSMR" are now supported.

162612 This release resets the fd limit for dd_rpc.

168534 In this release, the scp command can no longer be used to access any Data
Domain system internal files or to enter bash mode.

168638 This release converts client-group hostname to lowercase on CLI entry.

60 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 86 DD OS 6.0.0.1— Networking issues: fixed

Issue Description
68086 The new network filter feature has been added to 6.0 release.

107267 This release enables the feature to support a unique default gateway on each of
the interfaces.

116645 This release presents a fix to enable the default gateway to allow the data flow
to be more flexible.

137684 This release fixes the issue in which duplicate communication errorr occurred
during wizard configuration.

141558 In this release, ha_interconnect keys are not removed when an HA pairing is
destroyed.

142283 In this release, the Data Domain system no longer sends SNMPv1 traps. The
SNMPv1 traps may have been sent previously when the SNMP configuration
changed or the SNMP agent started or stopped.

143541 This release fixes an issue where an IO may timeout and the system panics.

144888 When upgrading from pre-5.7 to 5.7 static routes may be lost. The user can
manually reenter the static routes after upgrading.

147673 This release addresses the issue in which the customer receives incorrect
information via SNMP that one or more temperature sensors in the system are
overheatCritical.

147686 This release fixes the issue in which the SNMP replication status OID causes file
descriptor leaks if replication is licensed, but not configured.

147698 GUI VTL backwards compatibility has been fixed in this release.

148157 This release now allows for updating the IP address of a failover interface from
the GUI and CLI.

148311, This release includes the functionality to turn on/off rp_filtering through the CLI.
156605

149856 HA-Net Active HA node gives error with system SH ports, with heavy NFS and
DD Boost traffic. The fix for this issue is to use get_sysfs_ethernet_devices()
instead of the sysfs_get_class_device.

150344 This release fixes the net SNMP issue that occurred during upgrade from 5.4 to
5.7.

153571 In this release, GUI and remote administration users now have the same
information on multiple routing tables previously available only in the CLI.

153707 This release fixes the issue in which the LACP bonding on Intel 10G NICs (with
non-default MTU) doesn't work after an upgrade--due to connectivity loss on
that interface.

155155 This release fixes the issue in which fixed IPs were not labeled correctly. This
release fixes the issue in which gateway errors on the standby node were
unclear.

157341 Users are now have the option to create an Mtree automatically while creating
CIFS share and NFS exports in the configuration wizard.

Fixed in version 6.0.0.1-538504 61

Release Notes

Table 86 DD OS 6.0.0.1— Networking issues: fixed (continued)

Issue Description
157375 When standby is in offline mode, network CLIs may have previously failed during
configuration. This release fixes this issue.

158211 The SNMP service may not start after upgrade due to an incorrect
configuration. The customer will have to manually reconfigure the SNMP
settings.

160034 Users can now deploy DD VE with ovftool and specify the network for each
vNIC.

160497 This release resolves an issue where an SNMP notification from the Data Domain
System with the incorrect community 'public' string specified might be received.
The emsmon process may not recognize the registry entry when a custom port is
used. This fix corrects the way emsmon retrieves the registry entry.

161942 This release fixes the issue where a long running snmptrapd process could result
in reduced system performance and excessive memory and cpu consumption.
The system will now automatically disable the snmptrapd process after 24 to 48
hours.

162937 This release displays a help message about formatting if the net option
command is incorrectly entered.

167440 This release corrects an issue where some systems report the chassis serial
number instead of the system serial number from the Data Domain system via
SNMP.

Table 87 DD OS 6.0.0.1— Platform issues: fixed

Issue Description
117960 This release causes the SMART/BMS to check for errors during devperf read
test to locate a bad drive.

134008 This release adds a proxy feature for the support bundle to upload over HTTP.

137685 This release fixes the issue in which an unexpected GUI errorr occurred on the
DD Management Center.

140719 This release fixes an issue where I/O may timeout for all drives in a DS60 shelf
following an SXP reset and blocking discovery.

142047 This release fixes the issue in which a heartbeat timeout in the system health
monitor could cause the file system to hang and then to restart.

142182 The source enclosure model and min size disk is now included in ASUP.

143087 This release fixes this platform issue which could cause the customer to
experience kernel panic and system reboots.

143525, In this fix, an alert is no longer shown when root fs usage is 90%-95%.
146205

144319 This fix an issues where a disk with a connectivity issue may cause a system
panic.

144560 This release fixes an issue where systems using mpt2sas drivers could panic
while handling the kernel NULL pointer dereference.

62 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 87 DD OS 6.0.0.1— Platform issues: fixed (continued)

Issue Description
144955 This release fixes the PRAM vault issue which caused the Data Domain file
system to panic and reboot.

145283 This release fixes the issue in which the user was unable to view the daily space
usage from GUI.

145543 This release fixes the issue in which kernel panic may occur when creating filesys
on 5.7.0.3-501504.

145638 Qlogic driver firmware has been updated to 8.03. 02 in this release.

147005 This release fixes the issue in which a mutex is not released after drive failure
while gathering iostat information.

147494 This release fixes the issue in which this incorrect error message appears:
"/bin/cp: cannot stat `/var/lib/dhcpc/*': No such file or
directory".

148551 This release fixes the issue in which the End of Month Snapshot schedule only
worked for months with 31 days.

148989 Email support delivery can now be configured from DD System Manager in this
release.

151685 This release fixes the issue in which locality repair writes too many duplicates
which may cause the index bucket to overflow.

151837 This release fixes the issue in which the system could panic due to HDC requiring
more base memory due to new library.

152197 This release fixes the issue in the locality repair of spanning files which may
cause the system to panic.

152370 This release fixes the issue in which the system panics due to core during locality
repair.

153044 This release fixes the issue in which DD9500s could generate alerts about space
in /ddvar after headswap from DD990.

153645 This release fixes the issue in which there were HA historical database failover
issues.

154313 This release fixes the issue in which the ddr_attributes file could not be found
after an upgrade resulting in error messages to the user.

155631 This release fixes the issue which caused Data Domain file system HMON
timeout due to thread stuck in fm_ht_for_each_stream().

156322 This release fixes an issue where the lwsmd process cores on some traffic,
causing the system to panic.

156338 Shelf migration on a system with 17 or more shelves may cause system to panic.

156640 This release fixes an issue where a SLIC persistent indictment required a second
reboot to clear.

157187 PCR now handles a pathset containing a path with spaces.

157387 This release fixes the issue in which the system would not allow the user to log in
as sysadmin when using DDSH command.

Fixed in version 6.0.0.1-538504 63

Release Notes

Table 87 DD OS 6.0.0.1— Platform issues: fixed (continued)

Issue Description
157929 Network interfaces are now listed in alphabetical order in this release.

158911 This release fixes the issue in which the collection replication destination could
not restart.

160450 When the DD Boost SU name "Son," is the trailing name of a replication MTree,
it can now be deleted through both the CLI and GUI in this release.

161920 This release introduces new optional parameters, GUID and UID, as part of the
DDCP CLI that supports copying files in an LSU owned by a non-sysadmin user.

162439 The storage relevant commands may fail and report a "Session handle is stale"
error.

162863 An SNMP query will now return a value of "0" for individual disk stats (read,
write, and busy) when they are invalid.

164176 In this release, a reboot during an upgrade will no longer clear a registry entry.

166645 This release allows a user to add storage and then configure DD Cloud Tier from
the GUI and CLI.

Table 88 DD OS 6.0.0.1— Replication issues: fixed

Issue Description
82562 CLI commands "replication show history" and "replication show detailed-history"
will have consistent replication statistics across all the UIs with this release.

138307 This release fixes a replication reporting error, where replication stats,
particularly "Pre-Comp Remaining" might report 0 even when replication is going
on.

138826 This release fixes the issue in which MTree replication initialization or resync may
not continue after a source restart.

139791 This release fixes the issue in directory replication where frequent registry
updates could lead to a panic.

140550 This release fixes the issue in which the SNMP service could time out because
the replication show detailed-history command took longer than expected to
complete.

141598 This release fixes the issue in directory replication where the system could panic
during repl initialize with a very large directory.

141961 This release fixes the issue which caused replication commands to hang when
MTree replication was active.

142231 This release fixes the issue which caused the system to panic when a replication
context was modified with a wrong destination-host.

142956 The Data Domain file system will no longer panic if directory replication
encounters an error during snapshot-based initialization.

143413 This release fixes an issue which could cause a system panic due to memory
shortage on a collection replication destination.

145506 This release prevents a system panic due to RPC timeouts.

64 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 88 DD OS 6.0.0.1— Replication issues: fixed (continued)

Issue Description
145869 If replica target file system is full during replication, the Data Domain file system
will no longer panic.

146492 This releases fixes a bug in directory replication that caused the replica file
system to crash when applying ACLs on directories.

146619 This release fixes the issue where the GUI would block creation of replication
pairs between two Data Domain Extended Retention systems when their DD OS
versions differ, even if the configuration is valid.

148667 This release fixes the issue which caused a panic in directory replication during
log processing.

149358 This release fixes an issue which caused a panic on an MTree replication
destination.

151351 This release fixes the issue where deleting a file during BOOST ingest could
cause a panic.

152145 This release fixes the issue where directory replication could stop making
progress.

152659 This release fixes an issue with the stats calculation. The remaining bytes will no
longer jump to zero even when there is a lot of data still to be replicated.

152665 This release enables replication of a Governance-enabled MTree to a destination

system which is not governance enabled/licensed. Only the source system needs
to be licensed.

153753 This release fixes the issue where MTree replication stopped making progress
when multiple directory replication contexts were enabled.

156321 This release fixes an MREPL startup issue which caused the Data Domain file
system to panic.

156380 The error “attribute syncing” will no longer be displayed in the replication GUI.

157003 This releases fixes the issue where the MTree replication destination
unnecessarily runs out of space.

157214 This release fixes the replication issue that caused a panic in Managed File
Replication (MFR).

158021 This release fixes the issue where a panic could occur in Virtual Synthetic
Replication.

159874 This release fixes the issue where collection replication hangs during
initialization.

160370 This release fixes an issue with a SHA1 vulnerability. Data Domain Replicator
supports data-in-flight encryption using standard TLS 1.2 with SHA2.

160498 This release resolves the issue where a timeout in replication will cause the
system to panic.

161432 This fix removes the warning message that is no long applicable to MTree
replication from DD OS 5.5+.

Fixed in version 6.0.0.1-538504 65

Release Notes

Table 88 DD OS 6.0.0.1— Replication issues: fixed (continued)

Issue Description
163328 This release fixes an issue where a timeout in Virtual Synthetic Replication leads
to a system panic.

Table 89 DD OS 6.0.0.1— VTL/vDisk/Fibre Channel Protocols issues: fixed

Issue Description
136765 In this release, the failure to discover Data Domain system fibre channel targets
as been fixed.

138047 This release fixes the issue in which scsitarget initiator show list/detailed doesn't
list the directly connected initiator.

144589 This release fixes the VTL drivers issue in which the system may panic.

145103 This release fixes the issue in which the system returns an incorrect SCSI
Response. The system now returns the correct SCSI Response of 28 00 instead
of 28 03.

146655 This release fixes the issue in which VTL screen refreshes resulted in lost selects.

148990 In this release, the GUI will run initiator rename on the selected host instead of
on the management host.

149515 This release fixes an issue that occurs in a shared FibreChannel environment
when initiators use Reserve/Release to share devices causing the Data Domain
system to panic.

152820 Fibre Channel now works well with poor quality cable connection.

154887 This release adds new system param VTL_IBM_ULTRIUM5_DEVICEID_FIX,

which will give the correct device identification page for LTO5 and allowing port
failover.

157076 This release fixes an VTL CLI and GUI RPC error where the rpc error message
could not be sent.

157458 This release fixes the issue which caused very slow response for the backup
application to read element status SCSI command using VTL which caused the
SCSI daemon to panic.

160160 SCSI Mode sense response have been modified to consider IBM LTO4 and LTO5
media types.

66 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Known issues and limitations

Users should be aware of these known issues in DD OS version 6.0.2.40.

Known issues with DD Management Center

If DD Management Center 2.0.1.0 is used to manage systems running DD OS 6.0.2.x,
the following list of issues could be encountered. These issues are not encountered
when the Data Domain System Manager is running directly from DD OS 6.0.2.x.

Table 90 DD Management Center known issues

Issue Problem Description

179398 Static routes cannot be created through Data Domain System Manager.

189759 GUI does not support IPv6 static route creation.

CIFS/NFS known issues

Table 91 CIFS/NFS known issues

Issue Problem Description Workaround/Resolution

86682 While you can add conditional auditing to a file There is no workaround for this
in Windows 2012, the option to add conditional issue.
auditing to a file is not available on a Data
Domain CIFS share volume.

74086 On a Windows Vista or Windows 7 computer, This is a suggested workaround.

you may see a "File in use" or On desktops accessing the files
"Filename is locked for editing on a remote shared folder, modify
by username" message when opening a the following settings in Windows
Microsoft Office document (e.g., Excel or Word Explorer to disable the Windows
file) in a remote shared folder in Windows functions that cause this
Explorer that used the Details view and the behavior:
Preview Pane layout. This is caused by 1. Click Tools > Folder
Windows holding a lock on the files for longer
Options and select the
than normal, which is behavior associated with
View tab.
the Details view and Preview Pane layout. The
cause of this issue is a sharing violation that 2. Uncheck Show pop-up
happens between the operating system and the description for folder
Office application over a network resource. and desktop items.
3. Uncheck Show preview
handlers in preview pane.
4. Click Apply and then OK.

5. Click Organize > Layout

and uncheck Details pane.
6. Click Organize > Layout
and uncheck Preview pane.

Known issues and limitations 67

Release Notes

Table 91 CIFS/NFS known issues (continued)

Issue Problem Description Workaround/Resolution

71296 Because DD OS does not support file locking To resolve this issue, mount the
(byte-range locks), the Network Lock Manager Data Domain file system with the
(NLM) service has been disabled starting with appropriate option that prevents
DD OS 5.2. (This was done to prevent upgrade sending of NLM requests to Data
issues when local clients or scripts are Domain system. That is, the client
accessing the /data mount point.) This can or application should not rely on
cause backup jobs to hang or fail unexpectedly the NLM service on the Data
when the backup application or client relies on Domain system. For Linux clients,
the NLM service on the Data Domain system. use the -nolock mount option. For
Solaris clients, use the -llock
option. For other clients, refer to
the manual entry for the NFS
mount command.

56250 While DD Boost I/O jobs (backup or restore) There is no workaround for this
are in progress, do not make configuration issue.
changes with either the ddboost or nfs CLI
commands. The only exceptions, resulting in
safe configuration changes, are for enabling or
disabling distributed segment processing and
ifgroup changes.

DD Boost known issues

Table 92 DD Boost known issues

Issue Problem Description Workaround/Resolution

139304 If a failover occurs in a NetBackup environment There is no workaround for this
using DD Boost-over-Fibre Channel, the job will issue.
need to be run again.

DD Cloud Tier known issues

Table 93 DD Cloud Tier known issues

Issue Problem Description Workaround/Resolution

169334 When using CLI command cloud clean Run the command with <interval>
frequency set <interval>, if interval is as a number.
given as a string, the frequency is defaulted to
never. For example, the command cloud
clean frequency set abc sets the DD
Cloud Tier cleaning frequency to never.

168583 In case of failure during fmig or GC, on restart No workaround available.

fmig or GC might take a while to start due to
cloud unit recovery. Amount of time depends
on amount of data to recover, network speed,
and other system-related variables.

68 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Table 93 DD Cloud Tier known issues (continued)

Issue Problem Description Workaround/Resolution

168269 The WAN route that is used depends on the Set a static route for range of the
source address. Since the source address is not valid AWS IP in the main routing
definitively set (normally done by using bind), table.
the source address that is used may cause the
data to go over the admin port (usually 1 Gb/s)
instead of the data port (usually 10 Gb/s).

164704 Single Cloud Unit unavailable event due to There is no workaround for this
retries and timeouts observed with DD9500 and issue.
ECS as cloud target.

151561 Files in the cloud tier can be accessed while in There is no workaround for this
the nfs client cache. issue.

File system known issues

Table 94 File system known issues

Issue Problem Description Workaround/Resolution

171683 DSA-based authentication for passwordless Use RSA-based authentication.
SSH in not supported.

162598 When a remote IP with subnet is added to a To reproduce, complete this

tenant-unit, a range of ips becomes associated process. Pre-requisites
with that tenant-unit. According to mutual
l Tenant-unit tu1 belongs to
exclusion rule for remote-ips, tenant-units
tenant t1
belonging to different tenants should not share
remote ips. But a remote IP belonging to that l Tenant-unit tu2 belongs to
subnet range is allowed to be added to another tenant t2
tenant currently. Steps:

1. Add local data-ip ip1 to

tenant-unit tu1
2. Add remote data-ip ip2
(192.168.0.1/24) to ip1 (from
step1) to tenant-unit tu1
3. Add a list of 3 local data-ip
and list of remote data-ips
using single cli to tu2. Use
remote ips of same subnet.
For example, 192.169.0.10,
192.169.0.20, 192.169.0.30

161459 For a controller upgrade, the filesys command Perform storage remove of SSDs
requires additional storage in the cache tier. and storage add of the cache
SSDs to ensure required storage.

150633 Using floating hostname/IP to connect to HA The solution is to clear the entry
system through CLI, if SSH fingerprints are in the known host list. For more
stored in the known-hosts list of your local information, see KB article#
shell, then after HA-failover, you will get a 212538.

File system known issues 69

Release Notes

Table 94 File system known issues (continued)

Issue Problem Description Workaround/Resolution

"Host identification" error. (A floating
hostname/IP mapping was done for the
previous node.)

146536 On an HA system if a failover occurs, system If you run se sysparam set to

parameters that were set using the se change system parameters on the
sysparam command in rare cases may not be active node of an HA pair, run the
propagated to the surviving node. CLI command filesys restart on
the standby node to make the
change take effect.

General known issues

Table 95 General known issues

Issue Problem Description Workaround/Resolution

153672 Backup jobs that are run from AIX clients to HA To have the AIX client recognize
systems via Fibre Channel do not survive an HA the new server, run these two
failover. AIX clients work the same way on an AIX-specific commands on the
HA pair as they do on a single-node system. client:
The AIX driver does not recognize changes to
the fibre environment once loaded into
memory. #rmdev -Rdl DDdfc

#cfmgr

Networking known issues

Table 96 Networking known issues

Issue Problem Description Workaround/Resolution

97458 IPv6 is not supported on eth0/eth0a for the There is no workaround for this
DD160 and DD620 systems including any issue.
VLANs created in this interface, but IPv6 is
supported on any of the other interfaces of
these systems.

67152, The first ro-community with access to There is no workaround for this
64969, localhost must be present in order for issue.
51635 SNMP traps to be sent out.

70 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Platform known issues

Table 97 Platform known issues

Issue Problem Description Workaround/Resolution

122790 DD OS downgrade, even between the same There is no workaround for this
major version with different minor versions, is issue.
not supported. Under rare circumstances, a
Data Domain system's DD OS version can be
revised downward.

106621 If you are upgrading to a new version of DD OS There is no workaround for this
that requires you to perform multiple separate issue.
upgrades, such as from 5.0 to 5.2 and 5.2 to
5.4, you must insure that the first upgrade is
complete before starting the second upgrade.
Be sure to follow all of the upgrade instructions
for each upgrade process, and verify that the
process is complete before initiating a
subsequent upgrade. Certain versions of DD OS
disallow upgrades if those versions themselves
are not completely upgradable on the given
platforms.

Replication known issues

Table 98 Replication known issues

Issue Problem Description Workaround/Resolution

148755 On an HA system performing replication, after a There is no workaround for this
failover there may be a mismatch in the issue.
statistics reported for the replication on the
source and destination machines.

VTL/vDisk/Fibre Channel Protocols known issues

Table 99 VTL/vDisk/Fibre Channel Protocols known issues

Issue Problem Description Workaround/Resolution

103265 When access groups are updated, the There is no workaround for this
scsitarget endpoint show stats issue.
command displays only zeros because I/O is
suspended. The operation takes time to
complete and may require a few seconds before
I/O resumes.

Platform known issues 71

Release Notes

Environment and system requirements

In order for DD OS 6.0.2.40 to function properly, ensure that your Data Domain
system and client system tools meet these minimal requirements.
Support matrix
Refer to the Data Domain Support Matrix on the support website for compatibility and
interoperability information.
Screen Size
The minimum resolution for using the Data Domain GUI is 1024 x 768 pixels. Smaller
screens may be able to display the GUI in full screen mode.

Supported systems
DD OS 6.0.2.40 is only supported on the following Data Domain systems, running DD
OS 5.6 or later, and Data Domain Virtual Editions (DD VE):
l Appliance Series: DD160, DD620, DD640, DD670, DD860, DD890, DD990,
DD2200, DD2500, DD4200, DD4500, DD6800, DD7200, DD9300, DD9500, and
DD9800
l Appliance Series with the Data Domain Extended Retention software option:
DD860, DD990, DD4200, DD4500, DD6800, DD7200, DD9300, DD9500, and
DD9800
l Virtual Appliance Series: DD VE 2.0 (RPM upgrade) and DD VE 3.0

Note

The Global Deduplication Array (GDA) is not supported in DD OS 5.5 and later.

Supported browsers
The following browsers are supported for use with the Data Domain System Manager:

Table 100 Supported browsers

Microsoft Windows 7, 8, and 10 Apple OS X

Internet Explorer (IE11) N/A

Edge (only on Windows 10) N/A

Google Chrome Google Chrome

Mozilla Firefox Mozilla Firefox

File downloads
If you receive a certificate error when trying to access Data Domain, refer to your
internet browser instructions to either bypass the error or to install the self-signed
array certificate. For more detail about your system certificates, refer to the relevant
Data Domain Product Configuration Guide.

72 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Supported Flash versions

The latest version of Flash is recommended for use with the Data Domain System
Manager.

Software media, organization, and files

Learn about software media, organization, and files required for 6.0.2.40.
Required update
We recommend that you keep your Data Domain system up to date by upgrading to
the latest software version.
Problems downloading this release
If you have difficulty downloading this release, try using a newer version of Microsoft
Internet Explorer, Google Chrome, or Mozilla Firefox.

Obtaining and installing product licenses

Register your product. This provides you instant access to easy-to-use tools to plan,
install, maintain, and service your product. It also entitles you to software updates,
installation tools, and more.
Before you can use DD OS to protect your data, you must install product and feature
licenses on your system.
If you are a customer purchasing upgrade features/licenses that are new to the 6.0
release and installing them on legacy platforms, you will need to use the Data Domain
eLicense Conversion Tool to convert your existing licenses on your hardware prior to
purchasing and installing the new licenses.

Note

The following types of environments need the Data Domain eLicense Conversion Tool
to set-up the DD OS:
l EMC internal
l Existing systems that purchase a new feature that requires electronic licensing
l Existing systems but customers want to move licensing to electronic

Note

The following types of environments need an EMC Software license:

l A new system running DD OS 6.0 (except DD2200)
l Existing systems upgraded to DD OS 6.0 and are using the conversion tool to set
up the operating system

Note

Existing systems adding a new SW feature (exclude the Data Domain Cloud Tier
feature) that have not converted its existing license to electronic licensing need a
legacy license.

Supported Flash versions 73

Release Notes

EMC Software License Central will facilitate electronic licensing for Data Domain
systems through EMC Software Licensing Central (SLC) Portal
Ensure that you have the following:
1. License Authorization Code (LAC)-The LAC is sent by email from EMC.
a. This will be used to obtain your licenses from Software Licensing Central by
clicking on the URL under the Activating Your Software section of the email
2. The system serial number (physical systems) or the system UUID (virtual
systems).
3. License file downloaded from the Software Licensing Central site.

Using the Configuration Wizard for licenses during initial configuration

Procedure
1. On the Configuration Wizard page of the Initial Configuration wizard, select
License.
2. From the License type drop-down list of the Initial Configuration wizard, select
Electronic License Management System .
Select Data Domain if you are using the legacy licensing.
3. Follow the instructions on the licensing website and download the license file
locally.
Do not change the name of the license file.
4. Select Install License and use Choose File to browse to the license file you
downloaded locally.
5. Select Apply.
Results
The Results page will confirm the license was successfully installed.

Using the CLI to install licenses during initial configuration

Procedure
1. # system show serialno
Serial number: xxxnnnnnnnnnnn
2. # elicense update [<filename>]

Note

If there is a desire to copy the previously downloaded license file to the Data
Domain system's /ddvar location, use the elicense update <filename>
form of the CLI.

3. Enter the content of license file and then press Control-D.

Updating additional licenses after initial configuration

Procedure
1. Go to Maintenance > System > Configure System.
2. On Administration Licenses, select Update Licenses.

74 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

3. Navigate to the license file you downloaded locally.

4. Select Apply.
5. Select a product license from the list to display a description of that license.
6. To upload a product license, select Install License.
7. Review the Software License and Maintenance Agreement and select Accept
license agreement.
8. Locate the license file, select it, and select Open to install the license file on the
storage system.
Results
The license file is installed on the storage system.

Install and upgrade

Learn how to install and upgrade 6.0.2.40.

Note

If you purchased features that require a license, then refer to the Obtaining and
installing product licenses section for information on using the Software Licensing
Central (SLC) Portal. If you are not applying new features, then you can use DD OS
6.0 without accessing the licensing system.

Assuring overall compatibility of the DD OS upgrade

Upgrading the DD OS on a Data Domain system affects more than the Data Domain
system itself. It also affects the array of software applications and hardware devices
on which your backup and recovery activities rely.
While this version of DD OS may be compatible with the Data Domain system models
listed in Supported systems on page 72, it may not be compatible with any third-party
software or hardware currently in use at your installation. Upgrading to this version of
DD OS may prevent your Data Domain system from interoperating with those
software applications and hardware devices.
Data Domain maintains an active program of testing software and hardware that are
used with Data Domain systems, and we publish a wide range of compatibility guides.
Consult these guides, available on the Online Support site, to make sure that all key
components of your Data Domain system installation are compatible with this version
of DD OS. The relevant publications are the following:
l Backup Compatibility Guide, Data Domain Operating System 5.7
l Backup Compatibility Guide, Data Domain Operating System 5.6
l Data Domain Boost Version Compatibility Guide (covers all DD OS versions)
l Data Domain Archive Product Compatibility Matrix (covers all DD OS versions)
You can also access Data Domain software compatibility information at this website.
This resource for Data Domain software compatibility information eventually
supersedes the compatibility guide publications.

Preparing to upgrade to DD OS 6.0

Only Data Domain systems running DD OS 5.6.1.x, later releases of 5.6, and 5.7.x can
upgrade directly to DD OS 6.0. This restriction is due to the RPM signing. Typically

Install and upgrade 75

Release Notes

when upgrading DD OS, we only support the ability to upgrade two release families at
a time (e.g., 4.7 to 4.9, or 4.8 to 5.0, etc.). In order to upgrade to release 6.0 from a
release family earlier than 5.6, you will need to upgrade in steps. See the latest 4.4,
4.5, 4.6, 4.7, 4.8, 4.9, 5.0, 5.1, 5.2, 5.3, 5.4, or 5.5 release notes for upgrade
instructions as appropriate for the version your system is currently running for exact
upgrade steps. The most current release notes for all versions of DD OS can be found
online at the EMC Online Support site.

Note

DD OS 6.0 is the next release after DD OS 5.7.

If your upgrade plan calls for multiple successive upgrades (for example, from 5.1 to
5.4 to 5.6 and then to 6.0), use the filesys show space command to verify that
the file system is available before you start the next upgrade. If the filesys show
space command does not display the Active Tier Resource information, or if it
displays the The filesystem is unavailable at this time message, the
system is not ready for the next upgrade.

Note

After the completion of each upgrade to a newer release family, it is recommended

that you perform a spot check of the upgraded system by verifying that the expected
files are present and readable from either a CIFS, VTL, or an NFS client.

To upgrade from a release 5.6.1.x or later, download the 6.0 image from the
appropriate EMC download site, and follow the upgrade instructions, as described in
Upgrading to DD OS version 6.0.2.40 on page 80. The time for the upgrade process
to run depends on the platform and amount of data on the Data Domain system.
Be aware of the following before you perform the upgrade to DD OS 6.0:
l When upgrading to a DD OS 6.0, the upgrade will not proceed if LUN numbers
greater than 255 and initiators are present in the same group.

Note

This issue is only present if upgrading from pre-5.7 release to 5.7 or above.

The upgrade will proceed once the LUN numbers greater than 255 have been
removed from the identified groups or the initiator(s) are removed from the
identified group. It is necessary to remove (at an operating system level) any of
the VTL devices from the initiators associated with blocking the upgrade. Initiators
with an address method set to VSA will not block the upgrade and do not require
any changes. Once the upgrade completes, the removed initiators or devices can
be added back to the configuration on the Data Domain system. It is then
necessary to re-discover the VTL devices on any of the initiators associated with
blocking the upgrade. See KB article 191123 at the EMC Online Support site for
further details.
l If you are using NetWorker with VTL, you should take the following steps to
mitigate any data compression loss:
n Set the NetWorker tape block size on the Media Server to 256 KB. This value is
safe for all operating systems and drivers.
n Make sure there is at least 10% free space available on the Data Domain
system.
n To avoid low deduplication rates due to multiplexing of multiple backup
streams, it is recommended to set NetWorker device properties “target

76 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

sessions” and “maximum sessions” to 1. For further options on multiplexed

backups to Data Domain VTL, refer to the NetWorker documentation.
l For systems using CommVault for backups, the chunk size must be increased. See
the Data Domain KB article “Commvault Backup Fails with Chunk Size Mismatch”
for instructions on how to increase the chunk size.
l System controller upgrades are supported only from DD4200, DD4500, DD7200,
and DD990 systems. See the documentation for your particular platform, including
the appropriate Field Replacement Unit documents, and sections of the Data
Domain Hardware Guide. See also the Data Domain System Controller Upgrade Guide.
l In a small number of customer systems, registry parameters may have been
overridden by the SE to tune them for your environment. If you know that your SE
has overridden registry parameters, contact your support provider or visit us
online at the EMC Online Support site before upgrading to 6.0.x, as those
parameters may or may not need to be reset before upgrading.
l For systems that are already part of a collection replication pair, upgrade the
destination system first, and then upgrade the source system.
l For a DD OS upgrade, it is not necessary to disable replication on either system in
the pair.
l An upgrade of the destination Data Domain system from 5.6.1.x releases to 6.0.x in
a collection replication pair may take an hour or more. The slow upgrade results
when replication to the destination lags significantly or, in some cases, when doing
an upgrade just after a filesys clean operation. The best time to upgrade the
destination is when little data is waiting for replication and before (rather than just
after) a filesys clean operation.
Use the filesys show space command on the source and the destination. If
the value for the Data line in the Use% column is 2% or larger on the destination
than on the source, replication or processing of filesys clean results lags.
Assume that an upgrade on the destination will be slow.
The upgrade process generates a message periodically while the upgrade is making
progress. However, the messages are seen only from a serial console. Use a serial
console to verify that progress is continuous when doing an upgrade that you
suspect will be slow.
l Do not attempt to power down the system while the upgrade process is running.
l For an HA system, make sure both active and standby node are online before
performing an upgrade.

Pre-upgrade checklists and overview

Before performing any DD OS upgrade, you should review the items in these
checklists before proceeding. Doing so can simplify the upgrade process and ward off
potential difficulties.

Pre-upgrade manual tasks

These are tasks that you should plan to do prior to the upgrade. These tasks are not
performed automatically by any process.
1. Reboot the Data Domain system. (If the upgrade is an MDU upgrade on a single
node or for an HA system, you may not need to perform the reboot. For an HA
upgrade, please refer toSingle Node to High Availability Upgrade for DD6800,
DD9300, DD9500, and DD9800 Guide.)

Pre-upgrade checklists and overview 77

Release Notes

2. Check for current alerts; this can reveal many such disk and other hardware
failures that should be addressed prior to upgrading:
# alert show current
3. Check that registry settings for config.net.*, crontab, and those related to
networking are valid.
For example, use the reg show config.net operation, and check to see
whether noauto.enabled, noauto.speed, and noauto.full_duplex are
appropriately set. This will allow the network to negotiate speed. Also check to see
whether .use_dhcp=true, because this will allow quick setup of not only the IP
address and netmask, but also the gateway.
This check is important because if these elements are mis-configured, rebooting
may cause the network to be unavailable.
4. Check whether all network interfaces are up and have appropriate IP addresses,
and check whether the Data Domain system is accessible via the Data Domain
System Manager or any other client used:
# ifconfig
5. Check the disk states, and do not perform the upgrade if the Data Domain system
is low on spares:

# disk show state

# disk show reliability-data

6. Check the enclosure status:
# enclosure show all
It should say “OK” for all devices.
7. Check whether the enclosure topology is correct:
# enclosure show topology
Also check whether any error appears with an asterisk (*) next to the
enc.ctrl.port field. Also check the Error Message field for any errors such as "A
possible problem was detected for this shelf controller or
the cable connected to it."
8. Check that the device port mapping is correct:
# system show hardware
9. Check the link speed for connected ports:
# system show ports
10. Check the status of the file system to determine that file system is running
normally:
# filesys status
11. If replication is enabled, check its status:
# replication status
12. If the system is in a cluster configuration, check whether the cluster is up and
running:
# cluster show config
13. Check kern.info log, and if you notice frequent failures in hardware, contact
Data Domain Support to inspect your system before you perform the upgrade.

78 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

# log view debug/platform/kern.info

14. Run an Autosupport Report just prior to performing the DD OS upgrade to
determine whether any remaining issues need to be addressed:
# autosupport send <your_email_address>

Automatic tasks performed prior to the upgrade

Understanding these aspects of a DD OS upgrade assures a smoother process.
The version of DD OS on your Data Domain system prior to upgrading performs these
tasks:
1. Determine whether replication initialization is in progress. If it is, the upgrade does
not proceed.
2. Inspect all the digests and signatures contained in .rpm file to ensure the integrity
and origin of the package. If the signature is not valid, the upgrade does not
proceed.
3. Determine whether the upgrade from the old version of DD OS to the new one is
permissible. Data Domain systems running DD OS 5.6.x or 5.7.x can upgrade
directly to 6.0. This restriction is due to the RPM signing. An upgrade is not
generally permitted under these circumstances:
a. The upgrade is between the same versions, such as from 6.0.0.1 to 6.0.0.4.
(This can be overridden in some specific circumstances; consult your Data
Domain support representative for further details.)
b. The upgrade is backward, such as from 6.0 to 5.7.
c. The upgrade exceeds two feature families, such as from 5.5 to 6.0.
4. Determine whether any NFS mount points are unknown. If any NFS mount points
are unknown, the upgrade does not proceed.
5. Determine whether the previous upgrade, if any, completed successfully. If the
previous upgrade was unsuccessful or did not complete, the current upgrade does
not proceed.

Automatic tasks performed by the upgrade script (in the .rpm file) prior to upgrade
These tests precede the actual upgrade process on the Data Domain system:
1. Determine whether two different kinds of NVRAM cards are present.
2. Check the /ddr partition and / (root) partition sizes for space utilization.
3. Check the OST version.
4. Determine whether the RAID metagroup is assembled. If it is not assembled, the
upgrade process does not begin.
5. Determine available space for the file system.
6. Determine whether sufficient space is available for the upgrade.
7. Check the VTL version, if VTL is present.
8. Determine whether the file system is enabled, and if it is not enabled, enable it.
9. Determine whether VTL is enabled.
10. Check the VTL pools to insure that they can be converted to MTrees.
11. Determine whether sufficient VTL space is available.
12. Insure that the numbers of MTrees and VTL pools do not exceed 100. (This check
enforced from DD OS version 5.0 onward.)

Pre-upgrade checklists and overview 79

Release Notes

13. Determine whether all dg0 disks are located on head unit. If not, the upgrade
process does not begin, and the problem must be addressed.
14. Check if ConnectEMC has been configured. If it is, a warning message is displayed
informing the customer to reconfigure ConnectEMC after the upgrade.
In addition to these checks, the system determines whether the file system can be
shutdown cleanly and without problems. If the file system cannot be shut down in a
clean manner, the upgrade process will stop.

Conditions that prevent the upgrade process

Several conditions can cause the upgrade process to be stopped:
l The Data Domain system is not in a functional state. For example:
n Storage is functionally deficient, such as an enclosure is missing.
n The file system did not shutdown cleanly, resulting in a core dump.
n The previous upgrade did not complete correctly.
l Space usage is problematic. For example:
n The / (root) or /ddr partition is full with log files, core dumps, and so forth.
n Insufficient storage space is available to perform the data upgrade.
l The Data Domain system is not configured correctly. For example, NFS mount
points were manually created under root.
l Storage unit names fail to be converted to MTree names. In order to convert to
MTree names, the storage unit names must contain only upper and lower case
letters (a-z, A-Z), digits (0-9), and underscore (_) and be no longer than 50
characters.
The goal of checking these conditions is to prevent any problematic upgrades or file
system anomalies to occur or propagate. The conditions are also applied in upgrades
involving source and destination partner systems in replication. A failed upgrade or file
system anomaly on a Data Domain system serving as a replication source causes no
corruption in the file system on a Data Domain system serving as a replication
destination.

Upgrading to DD OS version 6.0.2.40

Before you begin
l Prior to upgrading your Data Domain system, be sure to review the upgrade
preparations and considerations described in Preparing to upgrade to DD OS 6.0
on page 75.
l It is recommended that you reboot the Data Domain system before upgrading to
verify that the hardware is in a clean state. This step confirms there are no
hardware failures and you are ready to upgrade.
l If you are upgrading to a new version of DD OS that requires you to perform
multiple separate upgrades, such as from 5.4 to 5.6 and then from 5.6 to 6.0, you
must insure that the first upgrade is complete before starting the second upgrade.
Be sure to follow all of the upgrade instructions for the each upgrade process, and
verify that the process is complete before initiating a subsequent upgrade. Be
aware that certain versions of DD OS disallow upgrades if those versions
themselves are not completely upgradable on the given platforms.
l Be sure to determine that any applications or hardware devices that interoperate
with your Data Domain system are compatible with the DD OS version to which

80 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

you want to upgrade. Consult the following publications, which are available on the
EMC Online Support site:
n Backup Compatibility Guide, Data Domain Operating System 5.7
n Backup Compatibility Guide, Data Domain Operating System 5.6
n Data Domain Boost Version Compatibility Guide (covers all DD OS versions)
n Data Domain Archive Product Compatibility Matrix (covers all DD OS versions)
If any applications or hardware devices on which your Data Domain system
configuration relies are not compatible with the DD OS version to which you want
to upgrade, do not perform the upgrade. Consider upgrading to a different and
compatible DD OS version, or schedule your upgrade after the application's or
hardware device's compatibility with the desired DD OS version has been verified.
Procedure
1. Download the image for the DD OS 6.0.2.40-615545 from the appropriate EMC
download or support site.
2. Store the file, 6.0.2.40-615545.rpm, in the /ddvar/releases directory
on the Data Domain system.
Do not rename any software upgrade package that you received for your Data
Domain system and its licensed features. Upgrade processes and procedures
rely on the software package names being what they are. Renaming a software
upgrade package will cause the upgrade process to fail.
When downloading a Data Domain system software upgrade image using
Internet Explorer, the browser may add bracket and numeric characters to the
upgrade image name. Remove the added characters before performing the
system upgrade.

3. Make sure that the Data Domain system is idle. All replication initialization and
re-synchronization should be complete, and no backups should be running. A
useful command to assess the system's readiness is the alert show
current CLI operation.
4. For systems that are already part of a replication pair before the upgrade,
upgrade the destination system first, and then upgrade the source system.
You do not need to disable replication on either system in the pair.
5. Stop (log out from) all Data Domain System Manager sessions on the Data
Domain system.
6. Stop any active CIFS client connections before starting the upgrade. Use the
cifs show active command to check for CIFS activity. Disconnect any
client that is active. On the client, enter the command net use \\dd
\backup /delete.
7. To upgrade the system using the Data Domain System Manager GUI, follow
these sub-steps. To use the CLI, go to step 8. For an HA system, perform the
following steps on the active node.
To upgrade a Data Domain system running release 6.0.2.40,

a. Log in to the system where the upgrade is to be performed.

You can select any system from the Data Domain Network device list, but
you can upgrade only the system where you are logged in.

Upgrading to DD OS version 6.0.2.40 81

Release Notes

b. Click the name of the host system you are upgrading in the Navigation pane.
c. Select Maintenance > System.
d. From the Upgrade Packages Available on this Data Domain System list,
select the checkbox of the image to use for the upgrade.
e. Select Perform System Upgrade.
f. The Upgrade System dialog box appears.
g. Verify the version of the target image (the upgrade image) is
6.0.2.40-615545 and click OK.
A progress dialog box appears and advises that the system will automatically
reboot to complete the upgrade.
For the upgrade on a single node (non-HA system), the reboot phase can take
20 minutes or more, depending on features of your particular system. Do not
manually reboot the system during this time. During the reboot phase, the
connection with the system will be lost. After the reboot completes, log back
into the system.
For the upgrade on an HA system, the standby node reboots first. After it boots
up with the new DD OS, there will be a failover to let the newly upgraded node
to take over as the active node. Then the old active reboots to finish the
upgrade.

8. To upgrade a Data Domain system running release 6.0.2.40 using the CLI, issue
the command: (For an HA system, issue the command on the active node.)
system upgrade start 6.0.2.40-615545.rpm

The upgrade process includes a precheck phase that evaluates a set of

parameters and indicates whether there are any issues that will prevent an
upgrade. The version of the planned DD OS upgrade must be later than the DD
OS version currently installed. “Reverse upgrades,” or reverting to an earlier DD
OS version than the version currently installed, are not supported. If you want
to perform the precheck without proceeding to the actual upgrade process, you
can use this command:
system upgrade precheck 6.0.2.40-615545.rpm

The general effects of upgrading the Data Domain system to DD OS 6.0.2.40 by

means of the CLI are the same as those described in the previous step.

Results
When upgrading, the following error may display:
[UPGRADE]: Upgrade in progess:
[UPGRADE]: Node 0: phase 1/4 (Precheck 1%)
[UPGRADE]: **** Upgrade failed: RPM "/ddr/var/releases/
6.0.2.40-615545.rpm"
[UPGRADE]: is not a valid

If you see this error, the .rpm file you downloaded to your Data Domain system was
probably corrupted during the download. Make sure to set the transfer mode to binary
(the default is byte) when downloading the .rpm file from the website. You can also
validate the .rpm file hash through use of the checksum. To find the hash value for
the file, click the View MD5 button on the page where you downloaded the .rpm file.
If upgrade fails, contact your contracted support provider or visit us online at the EMC
Online Support site.

82 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Replication notes
With collection replication, no files are visible on the destination Data Domain system
if replication was not finished before starting the upgrade. After the upgrade, wait
until replication completes to see files on the destination.

ConnectEMC notes
In this release, ConnectEMC has been changed to support the Secure Remote Service
Virtual Edition (ESRS VE) gateway. This change requires a reconfiguration of the Data
Domain system to ConnectEMC after the upgrade.

Note

ConnectEMC only works with ESRS VE (V3) and can not send emails with older
versions of ESRS or on it s own. If ConnectEMC has been used with previous releases
of DD OS (e.g., 5.7 or 5.6), the ESRS VE server configuration will need to be re-
entered as it was removed during the upgrade process due to the to technology
upgrade.

Note

If an older ESRS gateway is being used, the ESRS VE gateway will need to be
implemented to allow for secure communications.

During the upgrade, if ConnectEMC is detected as configured, the existing

configuration will be removed. In addition, if the support notification method is
configured as ConnectEMC to send event messages to the company, it will switch to
email. After the upgrade, you can reconfigure the ConnectEMC with new
ConnectEMC command: support connectemc device register.
After ConnectEMC is configured, enable ConnectEMC with support
notification method set connectemc.

Additional Resources
As part of an effort to improve its product lines, we periodically release revisions of
software and hardware. Therefore, some functions described in this document might
not be supported by all versions of the software or hardware currently in use. The
product release notes provide the most up-to-date information on product features,
software updates, software compatibility guides, and information about our products,
licensing, and service.
Contact your technical support professional if a product does not function properly or
does not function as described in this document.

Getting Help
Support, product, and licensing information can be obtained as follows:
Where to find product documentation
For the most up-to-date documentation and help go to Online Support at https://
support.emc.com.

Additional Resources 83
Release Notes

Product Information
For technical support resources that may enable you to resolve a product issue before
contacting Customer Service, go to the following Support by Product pages on Online
Support (registration required) https://support.emc.com.
After logging in to the appropriate Support by Product page, you can access product
documentation, release notes, software updates, Knowledge base articles, How-to and
troubleshooting information, hardware, and software compatibility guides or
information about our products, licensing, and service.
Troubleshooting and Technical Support
For information about our products, software updates, licensing, and service, go to
Online Support (registration required) at https://support.emc.com. After logging in,
locate the appropriate Support by Product page.

Advisories
We provide you with technical advisories (ETAs) and security advisories (ESAs).
For information on an individual technical or security advisory, go to the Online
Support website search using the ESA number or "Security Advisories" as the
keyword. For a list of security advisories in the current year, refer to Security
advisories-All products-Current year. For a list of older ESAs, refer to Security
advisories-All products-Archive.
Set up the “My Advisory Alerts” option to receive alerts for Technical Advisories
(ETAs) and Security Advisories (ESAs) to stay informed of critical issues and prevent
potential impact to your environment. Go to Account Settings and Preferences, type
the name of an individual product, click to select it from the list, and then click Add
Alert. For the individual product or All Data Domain Products, select ETA’s and/or
ESA’s.
Common Vulnerabilities and Exposures (CVEs)
For more information about any of the Common Vulnerabilities and Exposures (CVEs)
mentioned here, consult the National Vulnerability Database (NVD). To search for a
particular CVE, use the database’s search utility.
Set up a profile in the Cassandra Tool to receive email alerts for vulnerabilities in the
National Vulnerability Database (NVD, formerly ICAT). Cassandra is a free tool from
CERIAS/Purdue University that monitors changes to the CVE List and sends
information about topics that are relevant to you. Go to Cassandra Tool, click New
User, complete the form to get an email containing a challenge password, then return
to Cassandra to finish setting up your profile. You have the option to receive email
notifications using keywords, products, and vendors.

Open source software

This software product may be distributed with open source code, licensed in
accordance with the applicable open source license. If you would like a copy of any
such source code, we will provide a copy of the source code that is required to be
made available in accordance with the applicable license. We may charge reasonable
shipping and handling charges for such distribution. Please direct requests for copies
of open source code in writing to this address:
Legal
ATTN: Open Source Program Office
176 South St.
Hopkinton, MA 01748

84 Data Domain Operating System 6.0.2.40 Release Notes

 Release Notes

Copyright © 2019 Dell Inc. or its subsidiaries. All rights reserved.

Published March 2019

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH
RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION
REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.

Open source software 85