Release Notes

Dell EMC Data Domain® Operating System,

Data Domain Virtual Edition 4.0 Update 4, and
Data Domain Management Center
Version 6.1.2.30

Release Notes
302-005-490
REV. 01
February 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 descriptions...............................................................................................2
l New features.......................................................................................................... 3
l Command changes..................................................................................................7
l Fixed issues........................................................................................................... 12
l Known issues and limitations................................................................................ 53
l DD OS and DD VE environment and system requirements.................................... 67
l DD Management Center environment and system requirements.......................... 69
l Software media, organization, and files................................................................ 70
l Install and upgrade................................................................................................75
l Additional Resources............................................................................................ 87
Release Notes

Revisions
Table 1 Publication history

Revision Date Description

01 February 2019 Initial Publication

Product descriptions
Learn about Data Domain Operating System, Data Domain Management Center, and
Data Domain Virtual Edition.

Data Domain Operating System overview

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.

Data Domain Virtual Edition overview

Data Domain Virtual Edition (DD VE) is a software protection appliance: a virtual
deduplication appliance that provides data protection for entry, enterprise and service
provider environments. Like any Data Domain system, DD VE is always paired with
backup software.
DD VE runs the Data Domain Operating System (DD OS), and provides the DD OS
command line interface (CLI) and the Data Domain System Manager graphical user
interface (GUI) for performing all system operations.
Data Domain Virtual Edition maintains the core Data Domain features that differentiate
it as the industry-leading protection storage. This includes high-speed, variable length
deduplication for a 10 - 30x reduction in storage requirements, unparalleled data
integrity to ensure reliable recovery, and seamless integration with leading backup and
archiving applications.
DD VE also comes with DD Boost, which speeds backups by 50%, DD Encryption for
enhanced security of data, and DD Replicator, which enables network efficient
replication for faster time-to-DR readiness. For more information about the features
and capabilities of Data Domain systems (both physical and virtual), see the Data
Domain Operating System Administration Guide.

Data Domain Management Center overview

Data Domain Management Center (DD MC) is a scalable, virtual system-based
solution for centralized management of multiple Data Domain systems and virtual data
protection system (DD VE instances).
l DD Management Center provides current and historical data for all of the managed
Data Domain systems, with subject presentation ranging from site-wide summaries
to granular detail for a selected object.

2 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

l DD Management Center can configure and monitor storage on multiple Data

Domain systems with secure multi-tenancy DD Boost backup and replication.
l DD Management Center is composed of a set of browser-based pages and is
installed and runs on a VMware, Hyper-V, or public cloud (for example, Amazon
Web Services (AWS) or Microsoft Azure) environment.

Note

Secure multi-tenancy is not supported on DD VE 2.0 instances, but it is supported on

DD VE 3.0 and later.

New features
This release offers new systems and software enhancements.

New features in DD OS 6.1.2

These release notes include information about these new features:
l DD Cloud Tier
n Cloud Tier Hardening
n Large Object Size for Cloud Tier
n AWS S3-IA
n Azure Cool Storage
l DD VE 4.0
n DD VE on S3 Storage and DD VE on Hot Blob Storage
– Backup/restore data into cloud object store while DD VE is running in the
cloud
– Use DD System Manager to configure, manage, and monitor DD VE on S3
storage on AWS and DD VE on hot blob storage on Azure
– Use DD MC for multisystem management of DD VE on S3 storage on AWS
and DD VE on hot blob storage on Azure
– Support VMC environments (VMware Cloud - flavor of AWS)
n Kernel-based Virtual Machine (KVM) Hypervisor
n SSD Cache Tier
n Cloud scale management: Provisioning and configuring DD VE systems for
backups to the cloud using REST
n Retention Lock Governance Edition support
l BoostFS Plug-in for Windows
l Certificate-based Authentication for Avamar and Networker backups in the cloud
with DD VE
l Data Cache: Deliver app consistent instant access and restore with backup apps
support
l Qualifications/Certifications:
n Cloud Tier Certification with ECS 3.2: geo-replication, metadata overhead,
large object size

New features 3
Release Notes

n Cloud Tier Certification with internal and external backup apps

n BoostFS & DD OS App Certifications
l Security enhancements
n Authentication improvements in DD System Manager and DD MC
n OpenLDAP support for NFS IDMapping

Hardware Enhancements
The Data Domain Operating System (DD OS) 6.1 introduces new hardware.

DD3300
The DD3300 includes the following features:
l DD OS software leveraging features from DD VE to allow it to run on a Dell
PowerEdge R740xd server
l 1 Intel 4110 series processor
l Supports DD Cloud Tier
l Three capacity configurations
Table 2 DD3300 configurations

Memory HDDs (4 TB 7200 Local storage Cloud storage

RPM NL-SAS) capacity capacity
16 4 4 TB 8 TB

48 10 16 TB 32 TB

64 16 32 TB 64 TB

l Expandable storage capacity:

n Expand a 4 TB system to 16 TB
n Expand a 16 TB system 32 TB (a system that is initially 4TB cannot be
upgraded to a 32TB)
l 4 x 1 GbE Ethernet connectivity
l Optional 2 x 10 GbE Ethernet connectivity
l 6 system fans, 5+1 redundant
l 1 or 2 power supply units (hot-swappable, 1+1 redundant when two PSUs are
installed)

Software enhancements
The DD OS 6.1 family offers these important software enhancements.
CIFS streams statistics and reports
CIFS integration with client-group display and reporting mechanism to provide DD
storage administrator or tenant administrator insight to each CIFS stream in progress
or completed. CIFS streams in progress information contains the CIFS host IP
connections, MTree path as well as progress in the form of last offset accessed and
duration of stream activity. Reports containing periodic maximum streams counts
allow backup administrators to adjust applications policies and set stream limits.

4 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

DD Boost MITM Mitigation

The DD Boost global authentication and encryption settings have been enhanced to
include protocol updates that prevent a rogue user from executing a Man in the
Middle (MITM) attack, which could compromise user data on a Data Domain system.
Key Management Interoperability Protocol (KMIP)
Relevant components of DD OS have been updated to support KMIP Key Manager and
achieve feature parity with RSA's Data Protection Manager (DPM).
NFS
This release provides NFS capabilities including:
l Version 4 support added to DD OS
l Exports redesign
l Manageability improvements
l Server scaling improvements
VTL streams statistics and reports
The Data Domain storage administrator or tenant administrator gain insight to VTL
streams (in progress or completed) via VTL streams and statistics reports. The
reports are also useful to backup administrators as well by providing periodic maximum
stream counts for setting stream limits.
VTL tape out to cloud support
VTL tape out to cloud provides ability to send tapes to cloud for long term retention.
Tape out to cloud provides alternate option of a cloud vault to customers for their PTL
offsite vault use case.

Note

VTL tape out cloud limitations are as follows:

1. Tape out to cloud from MREPL destination is not supported.
2. In case of HA failover, VTL tape out to cloud policies that are configured for pool
will not be replicated to failover node.
3. In case of HA failover, VTL tape location that is related to cloud and recalled time
will not be replicated to failover node.

New features for DD VE 4.0

l Kernel-based Virtual Machine (KVM) Hypervisor
l SSD Cache Tier
l Cloud scale management: Provisioning and configuring DD VE systems for backups
to the cloud using REST
l Retention Lock Governance (RLG) support

New features for DD VE 4.0 5

Release Notes

DD VE Licensing Modes
DD VE may be used with evaluation licenses or permanent licenses in served and
unserved licensing modes. Licenses are obtained from Software Licensing Central
(SLC).
Using the DD VE Evaluation License
When freshly deployed, the DD VE comes with an evaluation license with all supported
features and 500 GB capacity. The evaluation license now provides a 60-day grace
period following expiry on DD VE.

Note

Since DD VE 6.1.2.5 comes with 500 GB unserved licenses with supported features
when deployed, if you want to use served licenses, you must run elicense reset
to remove these before the license server is configured.

DD VE Retention Lock Governance License Feature

Retention Lock Governance (RLG) is now featured in DD VE in both served and
unserved modes.
Unserved Licensing Mode with RLG
1. If you upgrade to DD VE 4.0, but choose not to use RLG. DD VE will continue to
function with your existing licenses.
2. If you choose to upgrade to DD VE 4.0 and choose to use RLG, you will need to
obtain a new license file for the DD VE from the Software Licensing Portal with
the RLG License added to it. Then you may apply this license to the DD VE.
3. If you choose a fresh install of DD VE, follow instructions for item 2 above.
Served Licensing Mode with RLG
In served licensing, features are bundled with capacity, i.e., features are checked out
when capacity license is checked out. RLG will also be checked out as part of capacity
license checkout. If you want to use the RLG feature, you will need to obtain a new
license file with the RLG feature for the license server. Then apply the license file on
the license server.
1. If you upgrade to DD VE 4.0, the DD VE will automatically checkout the RLG
feature, if it is available on the license server. If it is not available on the license
server, DD VE will continue to function with the existing licenses on the system.
DD VE will continue to periodically attempt to checkout missing licenses.
2. If you choose a fresh install, on the checkout of the capacity license, DD VE will try
to checkout all feature licenses, including RLG. Even if all feature licenses could
not be checked out, the system will continue to function with checked out
licenses. DD VE will continue to periodically atempt to checkout missing licenses

DD Management Center new features

Data Domain Management Center provides comprehensive management, monitoring,
and control of Data Domain protection and storage, and it is periodically updated to
support upgrades to DD OS. The following is an overview of new features in the 6.1 DD
Management Center family.
The DD Management Center 6.1 release includes the following new feature:

6 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Public cloud manageability

Deployment of DD Management Center is now supported on these platforms and
environments:
l Amazon Web Services (AWS)
l Microsoft Azure

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.1 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.1.2
adminaccess option reset password-hash
Resets the password hash to its default value of MD5. Role required: admin.

adminaccess option set password-hash {md5 | sha512}

Specifies the hashing algorithm used to store local user passwords. After
changing the hashing algorithm, update the passwords for existing local users to
be compatible with the new algorithm. Role required: admin.

adminaccess ssh option set ciphers cipher-list

Sets the ciphers to be used by SSH daemon.

adminaccess ssh option set macs MAC-list

Sets the MACs to be used by SSH daemon.

Modified arguments in DD OS 6.1.2

adminaccess ssh option reset [ciphers | macs | server-port |
session-timeout]
The ciphers and macs parameters have been added.

adminaccess certificate delete { subject subject-name |

fingerprint fingerprint} [application {all | cloud | ddboost |
ldap | login-auth | https | keysecure | rkm | support |
application-list}]
The ldap parameter has been added.

adminaccess certificate import {host application {all |

ddboost | https | keysecure | rkm | application-list} | ca

Command changes 7
Release Notes

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

keysecure | rkm | application-list}} [file file-name]
The ldap parameter has been added for importing the x.509 host certificate.

adminaccess certificate show [detailed] [imported-host

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

client-group change history

New commands in DD OS 6.1.2
client-group show host-stats {all | hostname} view {current-
hour | last-24-hours | daily-total} [display-unit {Bytes | KiB
| MiB | GiB}]
Displays data sent and received by a specified host for the last hour, the last 24
hours, or a total daily summary. The system stores 24 hours worth of statistics
per host for average daily calculations. Daily statistics tracking for a host starts
with the first read/write stream processed by that host, and ends when the host
is inactive for 24 hours.
client-group show file-history {all | group-name} [last n
{mins | hours | days}] [end MMDDhhmm[[CC]YY]] [count n] [host
hostname] [mtree mtree-name] [min-size bytes]
Display the file history of a specified client group, or all client groups. Filtering
options include specifying a time period, a host, an MTree, or a minimum file size.
client-group show performance {group-name} {start
MMDDhhmm[[CC]YY]} [end MMDDhhmm[[CC]YY]] [display-unit {Bytes
| KiB | MiB | GiB}]
Display the performance history for a specific client-group, or all client groups in
10 minute intervals within the specified time range.
client-group show stream-history {all | group-name} view {log-
interval | performance-interval} [last n {mins | hours |
days}] [end MMDDhhmm[[CC]YY]] [count n]
Display the stream usage by a specific group, or all groups, for a specified time
period.

Modified arguments in DD OS 6.1.2

client-group compression show accumulated-history {all |
group-name} view {log-interval | performance-interval | reset-
interval} [end MMDDhhmm[[CC]YY]] [last n {mins | hours |
days}] [count n] [display-unit {Bytes | KiB | MiB | GiB}]
The performance-interval option displays statistics for 10 minute intervals
until the specified end time. The [display-unit {Bytes | KiB | MiB |
GiB}] option provides different measurement options for the output values.

8 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

cloud change history

New in DD OS 6.1.1
cloud provider verify
Validates the DD Cloud Tier configuration.

Modified behavior in DD OS 6.1.1

cloud profile add profile-name
Command now lets you add an Azure Government cloud profile, or an S3 Flexible
provider cloud profile.

data-movement change history

Modified arguments in DD OS 6.1.1
data-movement status [path {pathname | all | [queued]
[running] [completed] [failed]} | to-tier cloud [detailed] |
all]
Command is updated for to add the detailed option, to display additional
information about file scheduled for movement to cloud storage.

Modified output in DD OS 6.1.1

data-movement watch
View data movement progress while the operation is running. If the operation has
completed or is not running, output shows current status only.

Modified behavior in DD OS 6.1.1

data-movement status [path {pathname | all | [queued]
[running] [completed] [failed]} | to-tier cloud [detailed] |
all]
Command modified to display the number of files eligible for movement to cloud
storage.

Modified arguments in DD OS 6.1

data-movement status [path {pathname | all | [queued]
[running] [completed] [failed]} | to-tier cloud | all]
Command is updated for to add the queued, running, completed, and
failed parameters.

Modified behavior in DD OS 6.1

data-movement stop [path pathname | to-tier {active | cloud} |
all]
Command modified to stop a running recall job or remove a queued recall job.

cloud change history 9

Release Notes

ddboost change history

Modified arguments in DD OS 6.1
ddboost clients add client-list [encryption-strength {none |
medium | high} authentication-mode {one-way | two-way | two-
way-password | anonymous | kerberos}]
Two-way-password authentication mode option added. Role required: admin,
limited-admin.
ddboost clients modify client-list [encryption-strength {none
| medium | high} authentication-mode {one-way | two-way | two-
way-password | anonymous | kerberos}]
Two-way-password authentication mode option added. Role required: admin,
limited-admin.
ddboost fc show stats [endpoint endpoint-spec | initiator
initiator-spec] [interval interval] [count count]
Specify the endpoint or the initiator, not both. Role required: admin, limited-
admin, security, user, backup-operator, none.
ddboost option reset {distributed-segment-processing |
virtual-synthetics | fc | global-authentication-mode | global-
encryption-strength}
Global authentication mode and global encryption strength options added. Role
required: admin, limited-admin.
ddboost option set global-authentication-mode {none | two-way
| two-way-password} global-encryption-strength {none | medium
| high}
Global authentication mode and global encryption strength options added. Due to
dependencies, both options must be set at once. Encryption can be “none” only if
authentication is “none.” Role required: admin, limited-admin.
ddboost option show [distributed-segment-processing | virtual-
synthetics | fc | global-authentication-mode | global-
encryption-strength]
Global authentication mode and global encryption strength options added. Role
required: admin, limited-admin, security, user, backup-operator, none.

Modified output in DD OS 6.1

ddboost clients show active [all | client hostname | storage-
unit storage-unit | tenant-unit tenant-unit]
Output for the authentication mode can now indicate two-way-password is
enabled. Role required: admin, limited-admin, tenant-admin, security, user,
tenant-user, backup-operator, or none.

ddboost clients show config

Output for the authentication mode can now indicate two-way-password is
enabled. Role required: admin, limited-admin, security, user, backup-operator,
none.

10 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

filesys change history

New commands in DD OS 6.1.2
filesys encryption key-manager keys create
Creates a new active key on the KeySecure key manager.
filesys encryption key-manager set key-rotation-policy [every
<n> {weeks | months} | none]
Sets a key rotation policy on the KeySecure key manager.
filesys encryption key-manager reset [key-rotation-policy]
Change the existing key rotation policy on the KeySecure key manager.
filesys encryption key-manager keys modify [<key-id> | muid
<key-muid>]
Modifies the state of an existing key in the KeySecure key manager.

nfs change history

New commands in DD OS 6.1
nfs export create [<export-name>] path <path>
Create a named export and add a path.
nfs export destroy {<export-spec> | all}
Destroy one or multiple NFS exports.
nfs export rename <export-name> <new-export-name>
Rename a specific export.
nfs export add {<export-spec> | all} clients <client-list>
[options <option-list>]
Add a client or list of clients to export.
nfs export add {<export-spec> | all} referral <referral-name>
remote-servers <address-list > [ remote-path <path >]
Adds a new referral to an existing export or set of exports.
nfs export modify {<export-spec> | all} clients {<client-list>
| all} options <option-list>
Modify an export and modify clients across exports.
nfs export modify {<export-spec> | all} referral <referral-
name> [remote-servers <address-list>] [remote-path {<path> |
default}]
Update an existing referral to an export or set of exports.
nfs export del {<export-spec> | all} clients {<client-list> |
all}
Remove a client or a list of clients from existing exports.
nfs export del {<export-spec> | all} referrals {<referral-
list> | all}
Removes specified NFS referrals.

filesys change history 11

Release Notes

nfs export show summary [tenant-unit <tenant-unit>]

Show summary information for NFS exports.
nfs export show list [<export-spec>] [path <path-spec>]
[clients <client-list>] [tenant-unit <tenant-unit>]
View a list of exports.
nfs export show detailed [<export-spec>] [path <path-spec>]
[clients <client-list>] [tenant-unit <tenant-unit>]
Allows you to apply filters to selectively view certain exports, clients, paths, and
tenant-units.

Fixed issues
This is a listing of important changes and fixes that are made to this version of DD OS,
DD VE, and DD Management Center.

DD OS fixed issues
This release of DD OS, 6.1.2.30- 615547, includes a number of fixed issues. The
release also includes fixed issues from prior releases in the DD OS 6.1 feature family.

Fixed in version 6.1.2.30 - 615547

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

Table 3 DD OS 6.1.2.30— CIFS/NFS issues: Fixed

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

Table 4 DD OS 6.1.2.30— DDBoost issues: Fixed

Issue Description
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 5 DD OS 6.1.2.30— 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

12 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 5 DD OS 6.1.2.30— File System Issues: Fixed (continued)

Issue Description
205660 Multiple small files writing the exact same data simultaneously to the Data
Domain system caused DD OS to panic. The following message was written to
the messages.engineering log file:
ERROR: MSG-INTRNL-00001: PANIC: ddr/index/ss_index_mbuf.c:
ssim_add_container: 7860: !(mbuf->prtl_bucket_nentries[prtl_bucket_num] <=
SSIF_MAX_BUCKET_ENTRIES)

207227 The Data Domain system panicked when writing to cloud tier. The following
message appeared in the messages.engineering log:
DDFS PANIC: ddr/lib/ddr_keys.c: __ddr_keys_write_deks_to_cloud: 6625: !
(cpm_cp_is_cloud(cp) == TRUE)

215426 Replication update in cloud configuration caused a panic. The following message
appeared in the messages.engineering log:
ERROR: MSG-INTRNL-00001: PANIC: ddr/nfs/nfs_rpc.c: nfs_rpc_debug_cb:
321: Async rpc taking too long (> 420 secs)

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:

222643 If SMT was enabled but not configured during an upgrade to a version of DD OS
6.1.2.20 or earlier, NFS access was rejected.

224946 Erroneous CRITICAL hardware alerts halted filesystem operation or prevented

the filesystem from starting.

227984 Storage migration to active tier caused the file system to panic. The following
message appeared in the ddfs.info log file:
ERROR: MSG-INTRNL-00001: PANIC: ddr/sl/sl_fs.c: sl_fs_load_label: 1955:
Vpart Filesystem vol1 has mismatching member blkset 24 vs. 29.

229658 Panic occurred during cloud cleaning. The following message appeared in the
Alert History:
EVT-FILESYS-00008: Filesystem has encountered an error and is restarting.
The following message appeared in the ddfs.info log:
ERROR: MSG-INTRNL-00001: PANIC: ddr/gc/gc_copy_forward.c:
gc_cf_copy_containers_process: 7869: !((meta->scm_content_type &
ITERATE_MASK_ALL_LP) == 0 && (meta->scm_cmc_type &
CONT_HAS_META) == 0)

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.

DD OS fixed issues 13
Release Notes

Table 6 DD OS 6.1.2.30— General Issues: Fixed

Issue Description
214218 The file system space information is now displayed properly in the alert summary
email due to syntax fix.

224105 Formatting in printf has been modified to honor the percentage sign character
in an alert text.

232321 The user will now have icons instead of buttons to select the operations for
active directory authentication.

Table 7 DD OS 6.1.2.30— Networking Issues: Fixed

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

Table 8 DD OS 6.1.2.30— Platform Issues: Fixed

Issue Description
217194 This release fixes the watchdog timeout issue that caused kernel panics.

217812 This release prunes the DD Boost sample count.

219535 This release fixes upgrade to 6.0.2.20 issues that caused the system to panic
and reboot.

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

224034 This release fixes the automatic iDRAC reset issue that caused the system to
panic if all disks are seen in unknown state.

226007 This release fixes the log increase issue that caused the partition disk to panic.

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

229188 This release fixes the system panic that could occur during a headswap from
smaller system to one with higher capacity.

Table 9 DD OS 6.1.2.30— Replication Issues: Fixed

Issue Description
223699 This releases fixes the MREPL issue that caused the system to panic if the base
file table is large.

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

228552 This release fixes the MTree issue that caused SegFault panics during send file
operations.

14 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 10 DD OS 6.1.2.30— VTL/vDisk/Fibre Channel Protocols Issues: Fixed

Issue Description
208959 This release resolves SCSI target code issues that could cause system panics

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

228772 IBMi BRMS did not recognize the ejection of the tape from the Data Domain
VTL.

Fixed in version 6.1.2.20 - 606786

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

Table 11 DD OS 6.1.2.20— DD Boost Issues: Fixed

Issue Description
221305 This release fixes an issue where the HA status was temporarily degraded until
the next bulk sync.

Table 12 DD OS 6.1.2.20— File System Issues: Fixed

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

221129 This release corrects an issue with repeating folders in .snapshot visible
through CIFS.

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

223779 This release resolves an issue where the CLI response lagged when filesys
clean commands are used while remote_delete thread is trying to open the CP.

Table 13 DD OS 6.1.2.20— Networking Issues: Fixed

Issue Description
62814 This release mitigates the Multiple Vendor TCP Sequence Number
Approximation Vulnerability described in CVE-2004-0230 (PSRC-5950, Qualys
ID 82054).

Fixed in version 6.1.2.10 - 603959

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

DD OS fixed issues 15
Release Notes

Table 14 DD OS 6.1.2.10— File System Issues: fixed

Issue Description
180345 This release fixes the flush interval of 2.5 days which caused dirty pages to
accumulate in the Directory Manager cache.

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.

219040 This release improves garbage collection performance to prevent file system
panic.

219243 Garbage collection performance was enhanced to prevent file system panic.

219489 Space usage and consumption charts will now display last cleaning or data
movement dates to enhance user monitoring.

Table 15 DD OS 6.1.2.10— General Issues: fixed

Issue Description
205497 This release improves the speed of Cloud Recall for customers who recall very
large files with poor locality. Typically, the Cloud Recall performance problem
has been observed with Microsoft Exchange files with the Page Zeroing feature
enabled.

215122 NetMON functionality is now available with this fix.

218083 This release fixes the rd_thread CLI issue.

218548 This release allows for enhanced performance through the use of virtual disks for
data cache in DD OS.

Table 16 DD OS 6.1.2.10— Networking Issues: fixed

Issue Description
215109 The user is now able to download compression states from the DD Boost page.

Table 17 DD OS 6.1.2.10— Platform Issues: fixed

Issue Description
209512 The System Software Manager no longer panics due to the platform issue that
caused PMC to hang.

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

213401 The fix uses correct maximum max_hdbs number for the check

215017 This release fixes the driver's pointer context issue that caused 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.

16 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 18 DD OS 6.1.2.10— Replication Issues: fixed

Issue Description
205089 This release fixes the Mtree issue that caused Mrepl to panic.

Table 19 DD OS 6.1.2.10— VTL Issues: fixed

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.1.2.6 - 600545

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

Table 20 DD OS 6.1.2.6— File System Issues: fixed

Issue Description
216787 This release fixed an issue that prevented PCR from running when the system
capacity was in very full, or very empty conditions.

219243 This release fixes the CM issue that caused the system to panic.

Table 21 DD OS 6.1.2.6— General Issues: fixed

Issue Description
218548 This release fixed an issue that prevented configuration of the cache tier in some
DD3300 systems when upgraded to DD OS 6.1.2.5.

Table 22 DD OS 6.1.2.6— Replication Issues: fixed

Issue Description
219491 This release fixes the issue that caused the system to panic when using MTree
replication with encryption over the wire enabled.

Fixed in version 6.1.2.5-595467

This list contains important changes and fixes that are included with this version of DD
OS.

Table 23 DD OS 6.1.2.5— CIF/NFS Issues: fixed

Issue Description
20084 This release fixes the error caused if the user entered the realm name in
lowercase.

207191 The fix will allow customer to join DD to Active Directory, basically execute cifs
set authentication active-directory command with a non-admin
user.

DD OS fixed issues 17
Release Notes

Table 23 DD OS 6.1.2.5— CIF/NFS Issues: fixed (continued)

Issue Description
164057 This release allows NFS to include MTree quota.

193906 This release addresses the CIFS issue that caused the user option in shared
configuration not to migrate after an upgrade.

194080 This release fixes an issue that prevented nested subfolders in ddvar from being
directly mounted.

196107 This release fixes the timing of the CIFS file deletion process.

200493 This release fixes an issue where SID was incorrectly displayed under the Owner
column.

202911 Active Directory users are now able to login to the Data Domain system
regardless of the hostname length.

205068 This release corrects the NFS from causing a file system restart with the DD VE
Segfault.

206299 During replication, local group members on destination DD will be removed or

added correctly.

206534 Domain join will report “The domain join operation is already in progress if
another join” is issued when another operation is in progress.

Table 24 DD OS 6.1.2.5— Cloud Issues: fixed

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

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

188995 This release enables cloud capacity details to be displayed.

189462 This release introduces cal_io_sync_rw() to handle the UNIX style path.

191671 The data integrity check failure alert was fixed in this release.

198054 This release allows the profile to run without causing the setting system to panic.

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

199266 This release fixes the issue that caused cloud connectivity to panic.

200218 This release fixes issue where IO timeout caused SAS panic.

212601 DD VE on Azure object store may now be setup with this release.

210288 Licensing will provide a new API that will provide original cloud tier capacity.

202504 This release addresses file system locking issues that occurred during an
upgrade.

202652 This release skips deleted archive units during a space stats query.

18 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 24 DD OS 6.1.2.5— Cloud Issues: fixed (continued)

Issue Description
204421 This release addresses cloud object store availability issues.

207643 Cloud unit proxy can now be verified with this release.

208027 This release fixes CREPL issues that caused IO errors on containers.

Table 25 DD OS 6.1.2.5— DD Boost Issues: fixed

Issue Description
188790 This release corrects memory error in the list of AIX DFC devices.

189974 This release fixes the LSU compression issues that caused the system to panic.

192061 This release allows parameter changes from default timeouts.

192549 This release addresses Oracle message sizes.

196691 This release addresses Avamar panics with DD OS 6.1 releases.

199196 This release fixes excessive file system logging during Networker exchange
backups.

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

204176 If NBU Air retries a file copy, existing file copy operation is cleaned up to allow it
to succeed.

209295 Timing increased to prevent file system communication timeout for DD Boost
commands.

207771 This release resolves a memory allocation issue that could occur when connected
with token authentication.

208777 This release addresses DFC backup issues that caused the system to panic.

211158 This release fixes DD Boost plugin issue that caused backups to panic.

Table 26 DD OS 6.1.2.5— File System Issues: fixed

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

100525 This release improves security algorithm.

135440 This release addresses the du-shu command output size.

147538 This release fixes the MTree management issues that caused the file system to
panic.

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

176964 This release fixes the Cloud HMON issue that caused the file system to panic.

179277 This release addresses certificate signing issues.

180321 This release upgrades OpenSSH to version 7.5p1.

182119 This release fixes a file system issue where it incorrectly read two disk groups
are missing following a recent chassis swap.

DD OS fixed issues 19
Release Notes

Table 26 DD OS 6.1.2.5— File System Issues: fixed (continued)

Issue Description
182301 With this release, the CLI can be used to configure the Ciphers and Message
authentication codes that are supported over SSH service.

183731 This release fixes the user access authorization binary issue in the file system.

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

184608 This release fixes the directory manager inline compaction issue in the file
system.

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

185167 This release fixes the segmentation fault in user access authentication.

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

186587 This release fixes the content store issue that caused the system to panic.

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

188559 A new file system PCR was added to improve estimates.

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 Tier cleaning efficiency.

190199 This release fixes an issue with the file system 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.

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

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.

191439 This release fixes the sanitzation issue that caused the file system to panic.

191998 This release addresses SMT network isolation code to prevent net filter busy
issues.

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.

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.

193090 This release fixes BTree code in the directory manager core.

194675 This release no longer captures excessive DM logging messages.

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

20 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 26 DD OS 6.1.2.5— File System Issues: fixed (continued)

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

197364 An issue in the Archiver FMig previously caused the file system to panic.

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

197993 This release fixes SegStore issue that caused ingest panics.

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

199123 The fix in this release checks to ensure the "sed" command used to edit /etc/
services file is successful.

199326 This release addresses timeout based panic of the DDR when the DD Cloud Tier
operations are slow or unavailable.

199409 This release addresses volumes issues due to errors connecting to management
service at localhost.

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

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

200786 GUI issued fixed to allow file system page to be displayed.

202302 Mtree issue was fixed that previously caused DDR to panic.

202898 API fixed to address previous file system panic.

203762 Cloud GC selection adjusted for container sizing.

204057 The system passphrase no longer allows spaces.

204544 The fix in this release allows the DD MC registry upgrade script to add the
needed limited-admin keys to support limited-admin. Due to the fix, user systems
will get the required keys after an upgrade

204601 The user now able to view the background process on cloud unit.

205179 The system now logs the error message from the passive node instead of calling
ha_report_error.

206141 File system expunge issue fixed that previously caused system panic

206274 File system garbage collection issue fixed that previously caused system panic

206850 The fix allows the user to access cloud CP data.

207148 This fix changes the default maximum validation date on self-signed certificates
for CA to 5 years and HOST to 3 years.

207298 This issue is fixed by adding “/.” at the end of destination path.

207582 The cloud segstore now uses page list routines to access scm_cmap.

207599 Replaced cm_cloud_lookup() which is the API used to check for cloud
connectivity with CAL connectivity API

DD OS fixed issues 21
Release Notes

Table 26 DD OS 6.1.2.5— File System Issues: fixed (continued)

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

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

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

210451 The fix allows the host certificate to be imported properly for https 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.

Table 27 DD OS 6.1.2.5— General Issues: fixed

Issue Description
77097 This release addresses the need for improved SMTP support and authentication.

181594 The timeout window for data migration to DD Cloud Tier has increased from 1
sec to 20 seconds.

190600 This release fixes the DD8800 issue which caused the

SSD_SHELF_PRESENT

to be mistakenly reported in ASUP.

192311 This release fixes a DD MC database issue that caused the system to panic.

192478 This release fixed the DD MC issue which caused updated data not to be
displayed from DD VEs.

193953 This release fixes the EOS issue which caused data movement to panic due.

194700 This release fixes the storage relevant command issue that caused the SMS to
hang.

195834 This release allows for the setting of ADPC target temperature using the
registry.

197690 The Data Domain file system now handles RPC race condition without causing
the system to panic.

198894 HA node tests have been fixed with this release.

199141 The fix uses the registry to present the data movement value.

200628 This release ensures filesys validation by addressing User Interface issues.

201133 Fix includes corrected merging code.

201887 This release fixes an issue where NetWorker-ingested data was previously
counted twice.

201910 This release resolves an issue where data-movement could get stuck during early
initialization.

203349 This release fixes an issue where Avamar recall from the cloud fails.

22 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 27 DD OS 6.1.2.5— General Issues: fixed (continued)

Issue Description
203658 This release fixes a DD Cloud Tier issue that caused the system to panic.

206601 This release fixes a false alert issue that caused the system to panic.

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

208339 This release addresses display of historical data with DD Cloud Tier functionality.

208401 This release resolves an issue that could previously result in data movement
failure.

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.

209501 This release addresses a DD MC database issue that caused a system panic.

210041 The session memory is optimized with this release.

210894 With this release, a data movement suspend request is enabled during file
migration.

211272 This release addresses the panic that occurs when an additional IP address is
added to an ifgroup.

Table 28 DD OS 6.1.2.5— Networking Issues: fixed

Issue Description
118168 This release fixes the multipath reset issue that caused the system to panic.

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

184357 This release fixes an IFGroup panic issue in Networking.

193309 This release addresses Segmentation faults with the protocol monitor.

196519 Correct SNMP information is now reported during copy or raid reconstruction.

197110 This release resolves an HMON timeout error 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.

199932 User now receives a message to use static speed setting 1 GB.

205205 This release addresses the HA-pair issue that caused the kernel to panic.

206949 This release fixes the negative value displayed for DD Boost storage unit bytes.

207050 This release integrates new versions of diagnostic tools.

209021 User may now use normal net config <ifname> down command for interface.

209841 The fix handles the error case caused in NIC vendor firmware and avoids kernel
panics.

209952 When the request to bring the interface up on the standby is executed, the
system checks to see if the interface is being enabled and is using DHCP or has a
static address.

DD OS fixed issues 23
Release Notes

Table 29 DD OS 6.1.2.5— Platform Issues: fixed

Issue Description
170477 This release addresses the read performance with Disk Smart Data commands.

176392 This release ensures standby node does not update drive indicators.

179022 This release fixes the synching issue that caused the kernel to panic.

179115 This release fixes the iostat/sys stat reporting for the system manage data.

180011 This release fixes volume panics during an upgrade.

182660 This release addresses system time alerts on the DD6300.

183699 Support bundle scripts were modified due to support bundle collection slowness.

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

185172 This release fixes an issue where the drive FW updatescript signal caused
the SSM waiter process to exit early.

185727 This release addresses slow backup speed issue with disk driver SAS2.

186068 PSNT-enabled systems will now show the correct serial numbers.

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

188134 The power issue that caused the File System to panic was resolved in this
release.

188223 This release addresses the HA issue that caused continuous path alerts.

190070 This release addresses Linux output issues after a successful DD OS upgrade.

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

192705 The default max row is now configurable in the registry.

195872 This release corrects disk failure alert posting.

196863 This release fixes the issue which caused the file system to panic due to drive
performance.

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

198723 This release fixes the issue when using se sms restart from DDSH shell.

201587 This release updates to OpenSSL 1.0.2m per CVE-2017-3736 (OpenSSL

advisory).

201916 This release fixes an issue with DD9800 configuration that could core and cause
a system panic.

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 Output was fixed for the system show stats view sysstat command.

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

204108 This release includes a new upgrade status CLI option to clear upgrade status.

24 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 29 DD OS 6.1.2.5— Platform Issues: fixed (continued)

Issue Description
205201 This release fixes the disk driver issue which caused the kernel to panic.

205571 This release increases the maximum allowed connections for a High Availability
(HA) setup.

206104 This release fixes the core dump command issue which caused the file system to
panic.

212610 The fix in this release allows the user to see the hardware page and error
messages.

Table 30 DD OS 6.1.2.5— Replication Issues: fixed

Issue Description
155421 This release fixes the misleading CREPL recipe error message.

182963 This release fixes the server error in send_segs: permission denied
due to retention lock.
184506 This release fixes the managed file replication history logging issue.

189435 This release fixes an issue with the Replication Prediction graph display. For
more information, see KB article #502793. (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.)

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 fixes an issue that can cause a panic on the destination system of a
MTree replication context that uses Low Bandwidth Optimization. See KB article
#502498 for more information.

195772 This release resolves an issue where MTree replication destination during MRepl
may panic.

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

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

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

199179 This release fixes a segmentation fault in Data Domain File System during AMS
(automatic multi streaming) replication.

199565 In high end systems, a large number of pages can now be queued up at the end
of cache table.

202177 This release fixes the delete request of a nonexistent file that caused the DREPL
to panic.

202370 In this release, BFT optimization check enhances MTree replication performance.

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

203627 This release fixes an issue Repl leaking resclnt_id on err path.

DD OS fixed issues 25
Release Notes

Table 30 DD OS 6.1.2.5— Replication Issues: fixed (continued)

Issue Description
204102 This release resolves an issue where using AMS (automatic multi streaming) and
VSR (virtual Synthetic Replication) may cause MREPL to panic.

204398 This release addressed excessive logging with fm_srepl_recipe_track

messages.

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

208778 This release adds the file's content handle to the list of content handles for
enumeration.

209915 With this fix, the Data Domain system will no longer panic on the MREPL
destination when trying to open the basefile.

211735 The fix validates the recipe basefile only if the file has the recipe attribute.

Table 31 DD OS 6.1.2.5— VTL/vDisk/Fibre Channel Protocols Issues: fixed

Issue Description
104244 The VTL add tape error message has been improved with this release.

143654 This release increases the MTree content maximum to prevent VTL panics.

187680 This release fixes the vdisk service errors which caused the system to panic.

189959 This release fixes the tape copy operation issue that occurred when attempted
from one pool to another.

191424 This release addresses slow UI and CLI performance caused by VTL issues.

193981 This release fixes the incorrect error path handling when requests were being
sent to a disabled vdisk service.

200540 The fix is for the VTL issue that caused the 5.6 to 6.0 upgrade to panic.

204364 This release addresses the import issue that caused the User Interface to panic.

Fixed in version 6.1.1.20 - 594920

This list contains important changes and fixes that are included with this version of DD
OS.

26 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 32 DD OS 6.1.1.20— Platform Issues: fixed

Issue Description
188134 This release fixes an issue with DD2200 and DD2500 systems incorrectly
reported an unsupported power supply, causing the Data Domain File System to
shut down.

Fixed in version 6.1.1.10 - 591041

This list contains important changes and fixes that are included with this version of DD
OS.

Table 33 DD OS 6.1.1.10— CIFS/NFS Issues: fixed

Issue Description
200493 This release fixes an issue where SID was incorrectly displayed under the
Owner column.

Table 34 DD OS 6.1.1.10— DD Boost Issues: fixed

Issue Description
207771 This release resolves a memory allocation issue that could occur when connected
with token authentication.

Table 35 DD OS 6.1.1.10— DD Cloud: fixed

Issue Description
206733 This release updates REST API to reflect proper name for Virtustream profiles.

Table 36 DD OS 6.1.1.10— File System Issues: fixed

Issue Description
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.

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

180321 This release upgrades OpenSSH to version 7.5p1.

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

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

201887 This release fixes an issue where NetWorker-ingested data was previously
counted twice.

202302 This release fixes an issue that could cause a system panic when changing
ownership of an MTree that was a CIFS share.

DD OS fixed issues 27
Release Notes

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

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

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

206274 With this release, dm_attr_lru should be same size as is systemparameter in

dm_max_mtrees, which could otherwise cause the system to panic.

206447 This fix provides cm_used_bytes attribute for cm label.

207582 This release fixes an issue where cloud transfer is disrupted and a system may
panic.

209959 This release fixes an issue with the index having too many duplicates and causing
a system to panic.

Table 37 DD OS 6.1.1.10— General Issues: fixed

Issue Description
201910 This release resolves an issue where data-movement could get stuck during early
initialization

202652 This release skips deleted archive units during a space stats query.

203349 This release fixes an issue where Avamar recall from the cloud fails.

208401 This release resolves an issue that could previously result in data movement
failure.

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

Table 38 DD OS 6.1.1.10— 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 39 DD OS 6.1.1.10— Platform Issues: fixed

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

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

201916 This release fixes an issue with DD9800 configuration that could core and cause
a system panic.

201957 This release fixes an issue where an absent PSU on a DD3300 would not
previously post an alert.

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

28 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

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

Issue Description
205571 This release increases the maximum allowed connections for a High Availability
(HA) setup.

205839 This release resolves an SSD temperature reporting issue.

Table 40 DD OS 6.1.1.10— Replication Issues: fixed

Issue Description
203627 This release fixes an issue Repl leaking resclnt_id on err path.

204102 This release resolves an issue where using AMS (automatic multi streaming) and
VSR (virtual Synthetic Replication) may cause MREPL to panic.

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

209915 With this fix, the Data Domain system will no longer panic on the MREPL
destination when trying to open the basefile.

Table 41 DD OS 6.1.1.10— Security Updates

Issue Description
205292 This release upgraded JRE to version 8u161.

Fixed in version 6.1.1.5 - 582414

This list contains important changes and fixes that are included with this version of DD
OS.

Table 42 DD OS 6.1.1.5— CIFS/NFS Issues: fixed

Issue Description
185923 This release fixes an issue that is encountered with CIFS backups in DD OS
5.7.2.0 and 5.7.4.0 after a DD OS upgrade.

189157 This timing issue previously occurred when there were out of order read
requests while reading from CIFS.

196269 This release handles simultaneous null session requests over smb2 correctly.

Table 43 DD OS 6.1.1.5— 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.

165999 This release fixes a timeout issue on Data Domain systems with Cloud Tier
enabled.

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

DD OS fixed issues 29
Release Notes

Table 43 DD OS 6.1.1.5— File System Issues: fixed (continued)

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

171390 This release resolves an issue with memory allocation panics.

178498 This release limits the space usage in the root to allow space for important logs
and file system functionality.

180345 This release fixes a race condition with low free page, which may cause a system
to 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.

181594 The timeout window for data migration to Cloud Tier has increased from 1 sec to
20 seconds.

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.

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

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

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

186936 This fix verifies whether the system is shutting down before performing the
inline dmck thread, which may otherwise cause a system to panic. For more
information, see KB article #499512.

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

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

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.

189193 This release corrects an observed segfault at dd_fmig_monitor while

suspending data movement.

189904 See KB article #504387 for more information.

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

193302 This release fixes the Data Domain File System with a cloud issue that caused
the 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.

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

30 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 43 DD OS 6.1.1.5— File System Issues: fixed (continued)

Issue Description
195156 This release fixes a race between dmbt_passive_compactor_thread and
dmbt_remove_entry when INTR1 page is empty.

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

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.

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

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.

199288 With this fix, the region values are now correct when adding a Cloud Tier unit
through the GUI for AWS.

200772 This fix corrects a deadlock situation while performing the

fmig_mtree_disable command.

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

Table 44 DD OS 6.1.1.5— General Issues: fixed

Issue Description
183068 This release fixes an RPC scheduling issue.

197099 This release handles expired ELMS licenses on a physical Data Domain system
without causing a system panic.

197690 The Data Domain file system now handles RPC race condition without causing
the system to panic.

199631 Alert email messages are now delivered correctly.

199649 This release resolves an issue where VLAN Interface could not be created.

199722 If a mail server does not send any responses, this release will exit the process
after 60 seconds.

201870 This release fixes a sizing-related computation that occurs during sanitation.

Table 45 DD OS 6.1.1.5— Networking Issues: fixed

Issue Description
181784 This release fixes the net filer issue which caused the system to panic.

184071 Avamar can now be added to systems running DD OS 6.1.

DD OS fixed issues 31
Release Notes

Table 45 DD OS 6.1.1.5— Networking Issues: fixed (continued)

Issue Description
185201 This release resolves an 5.6 to 5.7 upgrade issue that could result in the loss of
gateway, IPS, and MTU.

192022 This release fixes an issue with net filter that could cause an SMS failure
when IPv6 was disabled. See KB article 502730 for more information.

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

198898 This release creates a registry key specifically for SNMP to store the sysName
information.

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 46 DD OS 6.1.1.5— Platform Issues: fixed

Issue Description
183934 This release fixes the platform issue that previously caused the system to panic
due to a half-rotated file (/ddr/hd/hdal.xlog.1).

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

192484 This release resolves an issue with a lingering failed RAID request that could
cause a system to panic and restart.

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

195225 With this release, volume introduces a reassemble retry if a certain error code is
returned from a reassembly.

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

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.

199182 This release fixes various upgrade screen display issues.

200214 Head unit expansions, along with the ability to unfail head unit drives, on DD2200
and DD2500 and similar platforms can now be successfully performed.

201259 crond and cron jobs during a controller upgrade are now in sync with the
correct time zone.

Table 47 DD OS 6.1.1.5— Replication Issues: fixed

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

185622 Storage unit names are now displayed in the GUI as "N/A" after completing
MFR. (Previously displayed as "Unresolved".)

32 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 47 DD OS 6.1.1.5— Replication Issues: fixed (continued)

Issue Description
193510 This release fixes a functional issue with replication show history. It now
correctly logs replication stats in the historical database.

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

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

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.

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

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

Table 48 DD OS 6.1.1.5— 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.

Fixed in version 6.1.1.2 - 578165

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

Table 49 DD OS 6.1.1.2— File System Issue: fixed

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

Table 50 DD OS 6.1.1.2— General Issue: fixed

Issue Description
199622 This release fixes the incorrect link status message.

Fixed in version 6.1.1.1-577055

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

DD OS fixed issues 33
Release Notes

Table 51 DD OS 6.1.1.1— CIF/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.

190472 This release fixes intermittent panics when ingesting data using NFSv4 with the
default NFS options.

Table 52 DD OS 6.1.1.1— DD Boost Issues: fixed

Issue Description
183310 This release corrects the DD Boost handles an NFS_Stale_Handle error during
aSynth 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.

191618 The output for the ddboost storage-unit show compression

<ddboost stu name> command has been corrected.

Table 53 DD OS 6.1.1.1— File System Issues: fixed

Issue Description
137574 This release limits the maximum size of audit.log file. If file size exceeds 70 MB,
the audit.log file is rotated.

148153 The directory manager layout was changed to support 128 bit lookup keys.

167690 The fix adds a check to permit both "_" and "-" conventions when doing
migration pre-check.

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

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

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

34 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 53 DD OS 6.1.1.1— File System Issues: fixed (continued)

Issue Description
180567 This release fixes the issue which caused the active CP page reclaimer to not
reclaim from cloud CP.

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.

183068 This release fixes an RPC scheduling issue.

184079 The fix in this release correctly reads the max_wait registry key so that it will not
cause the HDR to exit.

185920 This fix allows the directory manager to create MUX units in an SS instance, to
allocate streams as it requires.

185940 Getting inode lock for the MTree may race with snapshot create thread and
cause deadlock. To fix this problem, fm_dm1_iget_try to lock the parent inode is
called and readdir, if trylock fails.

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

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

192081 This release fixes the DD Management Center kernel watchdog threshold value
issue with vSphere web client.

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

Table 54 DD OS 6.1.1.1— General Issues: fixed

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

184252 This fix updates the signing certificate to allow DD VE to deploy on vSphere 6.5.

189193 This release fixes an observed segfault at dd_fmig_monitor while suspending

data movement.

190357 Historical charts and topology charts can now be rendered in IE-11.

Table 55 DD OS 6.1.1.1— Networking Issues: fixed

Issue Description
164683 The fix changes the name resolution code in CLI to confirm with GUI code.

181544 Exceeding 64,000 connections in a short interval can cause nf_conntrack table
to get full. When this happens, packets can get dropped leading to back up
failures.

181784 This release fixes the net filer issue which caused the system to panic.

DD OS fixed issues 35
Release Notes

Table 55 DD OS 6.1.1.1— Networking Issues: fixed (continued)

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

185718 This fix causes the SSM to enable the HBA ports more slowly instead of all at
once. This limits the rate of devices being discovered and avoids dropped events
from the kernel to user space.

188056 This release fixes the routing of packets from the wrong interface when multiple
interfaces are on the same subnet.

190493 This release fixes the file system issue that caused the client group to panic.

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

194612 This release fixes the issue that caused the SNMP not to respond on HA standby
node.

Table 56 DD OS 6.1.1.1— Platform Issues: fixed

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

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

180747 This release fixes the firmware upgrade issue which caused the kernel to panic.

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

185559 Fixed an issue that caused unnecessary disk failures and RAID rebuilds on ES20
shelves after upgrading to 6.1.

189332 This fix includes adding system base initialization routine before initializing
sysstats module.

189505 This release fixes the NVRAM vaulting issue which caused the system to stop
responding.

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

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

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.

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

192866 The fix in this release, moves the code earlier in rc.sysinit, so that if an upgrade
fails before the links are updated, using these links to mount secondary partitions
will not mount the wrong disk partitions.

192978 The fix for this release avoids a CPU_HOT/MEM_HOT issue in field.

194355 This fix increases one of the PLR pool's sizes to handle worst-case locality.

36 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 56 DD OS 6.1.1.1— Platform Issues: fixed (continued)

Issue Description
194700 The fix for this release adds the missed unlock operation and removes the
recursive locking.

Table 57 DD OS 6.1.1.1— Replication Issues: fixed

Issue Description
155421 This CREPL fix prevents unnecessary error messages from being shown in the
CLI

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

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 This release fixes an issue where an Invalid UUID error is displayed during
replication after an update to DD OS 6.0.1.x.

188763 MTree recipe replication fix prevents file system panics.

188943 This CREPL fix prevents mishandling in the error path.

190429 The fix includes enabling the troubleshoot code which helps in dumping the segs
to a dump file in the event of a checksum mismatch.

Table 58 DD OS 6.1.1.1— VTL/vDisk/Fibre Channel Protocols Issues: fixed

Issue Description
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.

186195 This release provides the appropriate scsi response so that BRMS can recognize
the tape ejection.

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

192680 This release fixes the vdisk service errors which caused the system to panic.

195782 This release fixes kernel panic by using kmalloc with GFP_ATOMIC which does
not enable IRQ in interrupt context.

DD OS fixed issues 37
Release Notes

Table 58 DD OS 6.1.1.1— VTL/vDisk/Fibre Channel Protocols Issues: fixed (continued)

Issue Description
196525 This release fixes the VTL tape issue which caused ASUP to panic.

Fixed in version 6.1.0.21 - 579789

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

Table 59 Security Updates in DD OS 6.1.0.21

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

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

Table 60 DD OS 6.1.0.21— File System Issues: fixed

Issue Description
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.

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.

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

199302 This release addresses the directory manager excessive logging issue by
increasing the debug level for many log messages.

Table 61 DD OS 6.1.0.21— General Issues: fixed

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

200628 With this release, the GUI does not allow a user to enable encryption without
setting a passphrase.

Table 62 DD OS 6.1.0.21— Networking Issues: fixed

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

Table 63 DD OS 6.1.0.21— Platform Issues: fixed

Issue Description
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.

38 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 63 DD OS 6.1.0.21— Platform Issues: fixed (continued)

Issue Description
192978 This fix corrects the issue of system shutdowns due to incorrect thermal
reporting on the DD9500 and DD9800 systems.

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

Table 64 DD OS 6.1.0.21— Replication Issues: fixed

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

192194 This release fixes an issue that can cause a panic on the destination system of a
MTree replication context that uses Low Bandwidth Optimization. See KB article
#502498 for more information.

193510 This release fixes a functional issue with replication show history . It
now correctly logs replication stats in the historical database.

195772 This release resolves an issue where MTree replication destination during MRepl
may panic.

Table 65 DD OS 6.1.0.21— VTL/vDisk/Fibre Channel Protocols Issues: fixed

Issue Description
186195 This release fixes an issue where previously the IBMi BRMS did not recognize
the ejection of the tape from DD-VTL.

192680 This release fixes an issue with prolonged catalog updates, which cause a
timeout.

196525 This release fixes a VTL tape issue which could cause a system panic during
ASUP generation. The output for the commands vtl tape show all and
vtl tape show all time-display recalled" are removed from
autosupport.

Fixed in version 6.1.0.11 - 571028

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

Table 66 DD OS 6.1.0.11— CIFS/NFS Issues: fixed

Issue Description
193309 This release fixes the CIFS-failed read issue which caused DDFS to panic.

Table 67 DD OS 6.1.0.11— 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.

DD OS fixed issues 39
Release Notes

Table 67 DD OS 6.1.0.11— File System Issues: fixed (continued)

Issue Description
190574 This release fixes an issue which prevented bash access during the data_
upgrade phase of a DD OS upgrade.

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

193980 The enumeration issue during replication that caused the system to panic was
fixed in this release.

Fixed in version 6.1.0.5 - 567091

This list contains important changes and fixes that are included with this version of DD
OS.

Table 68 DD OS 6.1.0.5— CIFS/NFS Issues: 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.

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.

Table 69 DD OS 6.1.0.5— DD Boost Issues: fixed

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

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

170139 The fix allows the system to perform backup using token authentication with
path/permissions configured, which could previously cause 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.

189747 DD Boost connection failures may be observed when using two-way-password

authentication and using multiple connections in parallel.

Table 70 DD OS 6.1.0.5— File System Issues: fixed

Issue Description
141206 This release fixes the issue which caused ER to drop files when the user moved
near-line data (small files) using data-movement.

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

40 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 70 DD OS 6.1.0.5— File System Issues: fixed (continued)

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

147553 This fix supplies Engineering and Support with additional information when
missing segment issues are detected in the field.

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.

157108 This release fixes the user access issue which caused the admin user to go into
bash mode.

157142 This fix ensures that 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.

162035 This release fixes the file system issue in which cloud clean reported
incorrect DD Cloud Tier cleaning status.

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

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 In this release, the slow copy phase of GC should no longer result in slow GC
performance. See KB article# 489268 for more information relating to this issue.

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

165427 In this release, Active Sync is not serialized behind Cloud Sync, which could
otherwise cause 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.

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

166496 This release modifies the behavior of cpm_cp_info_from_handle() to negate

missing segments when Cloud CP is down.

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

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

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

167647 This release eliminates a spurious error message that indicated an MTree was
not successfully created when in the MTree was successfully created.

DD OS fixed issues 41
Release Notes

Table 70 DD OS 6.1.0.5— File System Issues: fixed (continued)

Issue Description
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 correctly updates the "append notify" counters during error
handling.

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

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

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

169571 This release fixes the random IO issue which caused poor performance on
destination MTree.

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

170305 This release fixes the issue which occurred while upgrading from DD OS 5.2 or
previous system to 6.x, 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".

170583 This release fixes the issue in which a CIFS tries to open a MTree with DOC flag
set, which may cause 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 update 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.

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.

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

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

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

182863 In this release, the system administrator can add ssh-keys for security officer if
the username-password based login is disabled.

188507 Active Directory authentication stops working when upgrading to DDOS 5.7 or
higher if the Global Catalog is unreachable. Port 3268 is a new requirement in DD
OS 5.7 and 6.x. Please see KB article #500081 for active directory and KB article
#323297 for firewall ports.

42 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 71 DD OS 6.1.0.5— General Issues: fixed

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

162349 This release fixes the issue in which the DD Boost user option set CLI
command was not available with DD VE.

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

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

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

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

170468 This fix corrects duplicate x-axis labels being shown if data is below 4 for FS ops
and DD Boost connection's real time charts.

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

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

Table 72 DD OS 6.1.0.5— Networking Issue: fixed

Issue Description
19016 This release fixes the networking issue which caused an alert to be issued to the
customer if TCP checksum errors exceed the threshold value.

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 73 DD OS 6.1.0.5— Platform Issues: fixed

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

164473 This release fixes an FW issue with ECC error reporting.

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

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

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

168765 This fix prevents the incorrect alert (EVT-STORAGE-00026) after a Data
Domain system upgrade to 6.x.

169090 This release fixes the issue which caused a Data Domain file system to panic due
to malloc fail.

DD OS fixed issues 43
Release Notes

Table 73 DD OS 6.1.0.5— Platform Issues: fixed (continued)

Issue Description
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.

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

171105 This release fixes the issue in which multiple Data Domain file system threads
open a single file concurrently, causing the Data Domain file system to stop
responding after panic.

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

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

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

185154 This release fixes the version mismatch between head and storage issue which
caused headswap panic.

Table 74 DD OS 6.1.0.5— Replication Issues: fixed

Issue Description
160263 This release fixes the file copy check issue which caused replication to panic.

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

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

166996 This fix checks for the situations when a source is being asked to rollback and
disallows the rollback. Such situations are no longer a risk for a system panic.

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

169636 This change in this release reduces retry tries 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.

170443 This release fixes an issue with synthetic replication, which may cause a system
to panic.

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.

44 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 75 DD OS 6.1.0.5— Security Issues: fixed

Issue Description
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.

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

184166 After upgrading the system to latest 5.7.x or 6.0.x, an administrator CLI is
available to regenerate the certificate authority (CA) and host certificate with
higher key length of 2048. CLI is adminaccess certificate generate
self-signed-cert regenerate-ca.

DD VE fixed issues
This section identifies fixed issues in DD VE.
Also refer to the Data Domain Operating System release notes for the list of fixed issues.

Fixed in DD VE 4.0, Update 3 — DD OS 6.1.2.20

Table 76 DD VE 4.0, Update 3 — 6.1.2.20 Issues: fixed

Issue Description
See DD OS Fixed Issues above

212685 This release fixes an issue where a DD VE virtual console could not be used in
single-user mode.

Fixed in DD VE 4.0 — 6.1.2.5

Table 77 DD VE 4.0— 6.1.2.5 Issues: fixed

Issue Description
See DD OS Fixed Issues above

Fixed in DD VE 3.1 SP1 — 6.1.1.5

Table 78 DD VE 3.1 SP1 — 6.1.1.5 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.

165999 This release fixes a timeout issue on Data Domain systems with Cloud Tier
enabled.

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

171390 This release resolves an issue with memory allocation panics.

DD VE fixed issues 45
Release Notes

Table 78 DD VE 3.1 SP1 — 6.1.1.5 Issues: fixed (continued)

Issue Description
178498 With this release, the btmp.log file is rotated once it reaches 10MB.

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

180567 This release fixes the issue which caused the active CP page reclaimer to not
reclaim from cloud CP.

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.

181594 The timeout window for data migration to Cloud Tier has increased from 1 sec to
20 seconds.

181784 This release fixes the net filer issue which caused the 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.

183068 This release fixes an RPC scheduling issue.

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

184071 Avamar can now be added to systems running DD OS 6.1.

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

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

185622 Storage unit names are now displayed in the GUI as "N/A" after completing
MFR. (This is an update from "Unresolved".)

185923 This release fixes an issue that is encountered with CIFS backups in DD OS
5.7.2.0 and 5.7.4.0 after a DD OS upgrade.

186936 This fix verifies whether the system is shutting down before performing the
inline dmck thread, which may otherwise cause a system to panic. For more
information, see KB article #499512.

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

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

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.

189157 This timing issue previously occurred when there were out of order read
requests while reading from CIFS.

189193 This release corrects an observed segfault at dd_fmig_monitor while

suspending data movement.

189904 See KB article #504387 for more information.

46 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 78 DD VE 3.1 SP1 — 6.1.1.5 Issues: fixed (continued)

Issue Description
192022 This release fixes an issue with net filter that could cause an SMS failure
when IPv6 was disabled. See KB article 502730 for more information.

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

193510 This release fixes a functional issue with replication show history. It now
correctly logs replication stats in the historical database.

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.

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

195156 This release fixes a race between dmbt_passive_compactor_thread and

dmbt_remove_entry when INTR1 page is empty.

195225 With this release, volume introduces a reassemble retry if a certain error code is
returned from a reassembly.

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

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

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

196269 This release handles simultaneous null session requests over smb2 correctly.

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.

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

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

197690 The Data Domain file system now handles RPC race condition without causing
the system to panic.

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

198898 This release creates a registry key specifically for SNMP to store the sysName
information.

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

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

199288 With this fix, the region values are now correct when adding a Cloud Tier unit
through the GUI for AWS.

DD VE fixed issues 47
Release Notes

Table 78 DD VE 3.1 SP1 — 6.1.1.5 Issues: fixed (continued)

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

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

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

199631 Alert email messages are now delivered correctly.

199722 If a mail server does not send any responses, this release will exit the process
after 60 seconds.

200772 This fix corrects a deadlock situation while performing the

fmig_mtree_disable command.

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

Fixed in DD VE 3.1 SP1 — 6.1.1.5

Table 79 DD VE 3.1 SP1 — 6.1.1.5 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.

165999 This release fixes a timeout issue on Data Domain systems with Cloud Tier
enabled.

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

171390 This release resolves an issue with memory allocation panics.

178498 With this release, the btmp.log file is rotated once it reaches 10MB.

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

180567 This release fixes the issue which caused the active CP page reclaimer to not
reclaim from cloud CP.

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.

181594 The timeout window for data migration to Cloud Tier has increased from 1 sec to
20 seconds.

181784 This release fixes the net filer issue which caused the 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.

183068 This release fixes an RPC scheduling issue.

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

48 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 79 DD VE 3.1 SP1 — 6.1.1.5 Issues: fixed (continued)

Issue Description
184071 Avamar can now be added to systems running DD OS 6.1.

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

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

185622 Storage unit names are now displayed in the GUI as "N/A" after completing
MFR. (This is an update from "Unresolved".)

185923 This release fixes an issue that is encountered with CIFS backups in DD OS
5.7.2.0 and 5.7.4.0 after a DD OS upgrade.

186936 This fix verifies whether the system is shutting down before performing the
inline dmck thread, which may otherwise cause a system to panic. For more
information, see KB article #499512.

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

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

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.

189157 This timing issue previously occurred when there were out of order read
requests while reading from CIFS.

189193 This release corrects an observed segfault at dd_fmig_monitor while

suspending data movement.

189904 See KB article #504387 for more information.

192022 This release fixes an issue with net filter that could cause an SMS failure
when IPv6 was disabled. See KB article 502730 for more information.

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

193510 This release fixes a functional issue with replication show history. It now
correctly logs replication stats in the historical database.

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.

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

195156 This release fixes a race between dmbt_passive_compactor_thread and

dmbt_remove_entry when INTR1 page is empty.

195225 With this release, volume introduces a reassemble retry if a certain error code is
returned from a reassembly.

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

DD VE fixed issues 49
Release Notes

Table 79 DD VE 3.1 SP1 — 6.1.1.5 Issues: fixed (continued)

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

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

196269 This release handles simultaneous null session requests over smb2 correctly.

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.

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

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

197690 The Data Domain file system now handles RPC race condition without causing
the system to panic.

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

198898 This release creates a registry key specifically for SNMP to store the sysName
information.

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

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

199288 With this fix, the region values are now correct when adding a Cloud Tier unit
through the GUI for AWS.

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

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

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

199631 Alert email messages are now delivered correctly.

199722 If a mail server does not send any responses, this release will exit the process
after 60 seconds.

200772 This fix corrects a deadlock situation while performing the

fmig_mtree_disable command.

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

50 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Fixed in DD VE 3.1 SP1 — 6.1.1.1 - 577055

Table 80 DD VE 3.1 SP1 — 6.1.1.1- 577055 Issues: fixed

Issue Description
151880 This release contains a fix to enable support for a DH parameter length of 2048
bits in SMS API.

167690 The fix adds a check to permit both "_" and "-" conventions when doing
migration pre-check.

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.

185920 This fix allows the directory manager to create MUX units in a SS instance, to
allocate streams as it requires.

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.

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

191216 This release fixes the Repl init issue which caused the system to panic when over
the wire encryption is enabled and authentication-mode set to two-way.

192194 This release fixes an issue that can cause a panic on the destination system of a
Mtree replication context that uses Low Bandwidth Optimization. See KB article
#502498 for more information.

193510 This release fixes a functional issue with replication show history . It now
correctly logs replication stats in the historical database.

195772 This release resolves an issue where MTree replication destination during MRepl
may panic.

DD Management Center fixed issues

This release of Data Domain Management Center includes many fixed issues, which
are listed here by the specific release in which they were resolved.

Fixed in version 6.1.2.5-595467

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

Table 81 DD Management Center 6.1.2.5 - Fixed

Issue # Description
See DD OS Fixed Issues above.

DD Management Center fixed issues 51

Release Notes

Fixed in version 6.1.1.5-582414

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

Table 82 DD Management Center 6.1.1.5 - Fixed

Issue # Description
184079 This release updates how the max_wait registry key is read. See KB artlce
495307 for additional information.

186785 This release displays the reason for an inability to project capacity in the Capacity
report.

Fixed in version 6.1.0.5-567091

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

Table 83 DD Management Center 6.1.0.5 - Fixed

Issue # Description
174440 This release fixes an issue where only one out of four Data Domain systems show
historical space usage in DD Management Center.

174844 This release clarifies any errors that may be found or occur during an upgrade.

175025 In this release, the sms_cloud api error is now handled correctly on a Data
Domain system that is running a version below DD OS 6.0.

175102 This release contains reserved versioning for system and MTree capacity
statistics.

175592 This release fixes an issue where a vdisk device could only be created in read-only
mode.

175687 This release fixes an DNS resolution error when launching DD Management
Center System Manager

177357 This release fixes an issue with the net route add command that would
otherwise show and log an error.

178996 This release corrects an issue where users with the role of user could not change
their password through DD Management Center.

180206 Data Domain Management Center GUI will no longer report "invalid characters
not allowed" when attempting to add trap host or contact information.

52 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Known issues and limitations

The following lists contain known issues in DD OS, DD VE, and DD Management
Center.

DD OS known issues and limitations

Users should be aware of these known issues in DD OS version 6.1.2.30.

CIFS/NFS known issues

Table 84 CIFS/NFS known issues

Issue Problem Description Workaround/Resolution

191908 Due to a limitation in the current version of To use Active Directory with 6.1.0.4
Likewise in the Data Domain stack, we NFSv4, an NIS server must be and
cannot retrieve the UID and GID for Active configured on the clients and later
Directory users and groups using the the Data Domain system. This
LsaFindObjects() API. NIS server can be hosted on
the Active Directory server
itself, as outlined in the admin
guide.

86682 While you can add conditional auditing to a There is no workaround for 5.2.2.x
file in Windows 2012, the option to add this issue. and
conditional auditing to a file is not available later
on a Data Domain CIFS share volume.

74086 On a Windows Vista or Windows 7 This is a suggested 5.3.x

computer, you may see a "File in workaround. On desktops and
use" or "Filename is locked accessing the files on a later
for editing by username" remote shared folder, modify
message when opening a Microsoft Office the following settings in
document (e.g., Excel or Word file) in a Windows Explorer to disable
remote shared folder in Windows Explorer the Windows functions that
that used the Details view and the Preview cause this behavior:
Pane layout. This is caused by Windows 1. Click Tools > Folder
holding a lock on the files for longer than
Options and select the
normal, which is behavior associated with
View tab.
the Details view and Preview Pane layout.
The cause of this issue is a sharing 2. Uncheck Show pop-up
violation that happens between the description for folder
operating system and the Office and desktop items.
application over a network resource.
3. Uncheck Show preview
handlers in preview
pane.
4. Click Apply and then
OK.
5. Click Organize >
Layout and uncheck
Details pane.

Known issues and limitations 53

Release Notes

Table 84 CIFS/NFS known issues (continued)

Issue Problem Description Workaround/Resolution

6. Click Organize >

Layout and uncheck
Preview pane.

71296 Because DD OS does not support file To resolve this issue, mount 5.2.x
locking (byte-range locks) for NFSv3, the the Data Domain file system and
Network Lock Manager (NLM) service has with the appropriate option later
been disabled starting with DD OS 5.2. that prevents sending of NLM
(This was done to prevent upgrade issues requests to Data Domain
when local clients or scripts are accessing system. That is, the client or
the /data mount point.) This can cause application should not rely on
backup jobs to hang or fail unexpectedly the NLM service on the Data
when the backup application or client Domain system. For Linux
relies on the NLM service on the Data clients, use the -nolock mount
Domain system. 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 There is no workaround for 5.0.1.x
restore) are in progress, do not make this issue. and
configuration changes with either the later
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 85 DD Boost known issues

Issue Problem Description Workaround/Resolution

139304 If a failover occurs in a NetBackup There is no workaround for 5.7.x
environment using DD Boost-over-Fibre this issue. and
Channel, the job will need to be run again. later

DD Cloud Tier known issues

Table 86 DD Cloud known issues

Issue Problem Description Workaround/Resolution

214530 During a system recovery, the index 1. Deploy new DD VE 6.1.2.x
rebuild fails, resulting in an "out of space" instance. and
error message. later
2. Configure DD VE on S3
storage (Using the same
S3 bucket and passphrase

54 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 86 DD Cloud known issues (continued)

Issue Problem Description Workaround/Resolution

used for the original

system).
3. Attach EBS meta storage
(500GB more than for
the original system).
4. Add all EBS volumes to
DD VE on S3 storage, but
do not create file system.
5. Proceed with system
recovery.

214514 In the DD OS 6.1.2.5 release, Data Domain Restart the file system to 6.1.2.x
only supports ECS with version of 3.2.1 or enable the multicopy and
higher. If this recommended practice is not capability. later
followed, and the ESC is upgraded to 3.2.1
or higher version after DD OS 6.1.2.5 is
deployed, the multicopy capability may not
be enabled

208590 Here are two scenarios where DDFS The headswap will be 6.1.2.x
cannot be enabled during a headswap: successful when the DD VE and
reboots after using the later
1. An invalid instance type/configuration
headswap command. Due to
is used for the new head
the wrong instance type, the
2. A valid instance type/configuration is DDFS will not be enabled after
used but it doesn't match the initial boot for DD VE.

1. An alert will be raised and

you will be asked to
change the instance type.
2. Power off the DD VE and
change the instance type
to the correct one.
3. Power on the DD VE, the
DDFS should now load
automatically

169334 When using CLI command cloud clean Run the command with 6.0.x
frequency set <interval>, if <interval> as a number. and
interval is given as a string, the frequency later
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 No workaround available. 6.0.x

restart fmig or GC might take a while to and
start due to cloud unit recovery. Amount later
of time depends on amount of data to
recover, network speed, and other
system-related variables.

DD OS known issues and limitations 55

Release Notes

Table 86 DD Cloud known issues (continued)

Issue Problem Description Workaround/Resolution

168269 The WAN route that is used depends on Set a static route for range of 6.0.x
the source address. Since the source the valid AWS IP in the main and
address is not definitively set (normally routing table. later
done by using bind), 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 6.0.x
retries and timeouts observed with this issue. and
DD9500 and ECS as cloud target. later

151561 Files in the cloud tier can be accessed There is no workaround for 6.0.x
while in the nfs client cache. this issue. and
later

File system known issues

Table 87 File system known issues

Issue Problem Description Workaround/Resolution

215125 Updating an eLicense on the DD VE during Disable the files system or 6.1.2.1
the data ingest or expunge (garbage stop the ingest and garbage and
collection) process may generate a DDFS collection before adding a later
core in the backend. new eLicense on the DD VE.

184580 If the customer loses the log in credential 1. Build new DD VE 6.1.x
for a cloud based DD VE, there is no and
process to reset it. 2. Detach/unmount the EBC later
data volumes from the
"broken" DD VE
3. Configure the new DD VE
4. Attach/mount the EBS
data volumes to the new
DD VE
5. Restart the new DD VE to
detect the new volumes
6. Perform some type of
headswap to import the
new DD VE

171683 DSA-based authentication for Use RSA-based 6.0.0.9

passwordless SSH in not supported. authentication. and
later

162598 When a remote IP with subnet is added to To reproduce, complete this 6.0.x
a tenant-unit, a range of ips becomes process. Pre-requisites and
associated with that tenant-unit. later
l Tenant-unit tu1 belongs
According to mutual exclusion rule for
to tenant t1
remote-ips, tenant-units belonging to

56 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 87 File system known issues (continued)

Issue Problem Description Workaround/Resolution

different tenants should not share remote l Tenant-unit tu2 belongs
ips. But a remote IP belonging to that to tenant t2
subnet range is allowed to be added to
another 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 Perform storage remove of 6.0.x
command requires additional storage in SSDs and storage add of the and
the cache tier. cache SSDs to ensure later
required storage.

150633 Using floating hostname/IP to connect to The solution is to clear the 5.7.0.5
HA system through CLI, if SSH entry in the known host list. 0 and
fingerprints are stored in the known-hosts For more information, see KB later
list of your local shell, then after HA- article# 212538.
failover, you will get a "Host identification"
error. (A floating hostname/IP mapping
was done for the previous node.)

146536 On an HA system if a failover occurs, If you run se sysparam set 5.7.0.5

system parameters that were set using the to change system parameters 0 and
se sysparam command in rare cases on the active node of an HA later
may not be propagated to the surviving pair, run the CLI command
node. filesys restart on the standby
node to make the change take
effect.

General known issues

Table 88 General known issues

Issue Problem Description Workaround/Resolution

216515 In Azure, ending characters are truncated Create hostnames that are no 6.1.2.1
from a hostname when the hostname longer than a maximum length and
exceeds 63 characters in length. of 63 characters. later

DD OS known issues and limitations 57

Release Notes

Table 88 General known issues (continued)

Issue Problem Description Workaround/Resolution

153672 Backup jobs that are run from AIX clients To have the AIX client 5.7.0.51
to HA systems via Fibre Channel do not recognize the new server, run and
survive an HA failover. AIX clients work these two AIX-specific later
the same way on an HA pair as they do on commands on the client:
a single-node system. The AIX driver does
not recognize changes to the fibre
environment once loaded into memory. #rmdev -Rdl DDdfc

#cfmgr

Networking known issues

Table 89 Networking known issues

Issue Problem Description Workaround/Resolution

216158 A display error occurs in rare cases, when If this error is seen, check to 6.1.2.1
two DHCP servers are in the environment see if the link is actually down and
and only on a rockslide network card. This or if it is a net show hardware later
is a display error, the functionality is not issue, then ignore the
broken. message. Or you can run the
CLI again as you would a
timing issue.

97458 IPv6 is not supported on eth0/eth0a for There is no workaround for 5.5.x
the DD160 and DD620 systems including this issue. and
any VLANs created in this interface, but later
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 5.1.x
64969, localhost must be present in order for this issue. and
51635 SNMP traps to be sent out. later

Platform known issues

Table 90 Platform known issues

Issue Problem Description Workaround/Resolution Exists

in
106621 If you are upgrading to a new version of There is no workaround for 5.2.3.1
DD OS that requires you to perform this issue. and
multiple separate upgrades, such as from later
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

58 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 90 Platform known issues

Issue Problem Description Workaround/Resolution Exists

in
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

VTL/vDisk/Fibre Channel Protocols known issues

Table 91 VTL/vDisk/Fibre Channel Protocols known issues

Issue Problem Description Workaround/Resolution

191995 For vDisk added support for retention lock, 1. Only replicate to 6.1 DD 6.1.0.4
images may be deleted on the replication OS Data Domain systems. and
destination before the expiration of those later
images. DD OS 6.0 and earlier releases do 2. Use the replication copy
not support this feature for vDisk. as restore/recovery only,
as RL for vDIsk is not
supported as a feature on
DD OS 6.0.

162990 With Fibre Channel HBA QLE2462 using There is no workaround for 6.0.x
NPIV, when endpoints are disabled and this issue. and
enabled (scsitarget endpoint later
disable all and scsitarget
endpoint enable all), the commands
complete successfully but sometimes
some endpoints status may be offline
because of an issue in the Qlogic
Firmware.

DD VE known issues and limitations

This section identifies known and open issues in DD VE. Refer to the Data Domain
Operating System release notes for the additional known and open issues.

Table 92 Known issues in DD VE 3.1

Issue Problem description Workaround

number
137646 In the VMware vSphere web client, There is no workaround for this issue.
DD VE version number shows as X.Y
instead of the full version number
with the build number.

DD VE known issues and limitations 59

Release Notes

Table 92 Known issues in DD VE 3.1 (continued)

Issue Problem description Workaround

number
138073 When upgrading to virtual machine Upgrade to vSphere client 5.5 update 2 or
compatibility hardware version 10 on virtual machine compatibility hardware
vSphere client 5.5, the DD VE virtual version 11 on vSphere client 6.0.
machine settings cannot be edited
from the vSphere client.

152592 If virtual devices are removed from There is no workaround for this issue.
the DD VE, running the deployment
assessment tool at a later time may
fail because the system is looking for
devices that no longer exist.

158021 The system may panic if an RSA DPM There is no workaround for this issue.
Client certificate is within 15 days of
expiring.

157083 To use the "vserver" command, you 1. For HKCR/CLSID/{clsid} and

have to make sure that the WBEM HKLM/SOFTWARE/Classes/CLSID/
Scripting Locator COM server has {clsid}, make sure the credential
been registered on your Windows you are using has the "full control"
Server. Since starting with Windows permission
7 and Windows Server 2008 R2 most
of these registry keys have the 2. Execute "regedit" in order to start the
"TrustedInstaller" set as owner and registry editor
only that user has full access to them, 3. Create an AppID value under HKCR
when we try to register it \CLSID\{clsid} which contains
automatically there is an "Access the same value as the CLSID HKCR
denied" error, so you may have to \CLSID\{clsid} AppID =
register the COM server by yourself. {appid value}
4. Create an AppID key under HKCR
\AppID HKCR\AppID\{appid}
5. Under HKCR\AppID\{appid},create
the following values: (Default) =
DllSurrogate = The {clsid} is
{76a64158-
cb41-11d1-8b02-00600806d9b6}

158318 Hyper-V uses "Virtual Machine For CPU reservation in Hyper-V, the
Reserve" to specify the minimum minimum setting is calculated as follows: If
CPU reserve of a virtual machine. the host processor number is hp and the
speed is hs GHz, the virtual processor
number is vp and the speed is vs GHz. The
reserve percentage is R. To set the CPU
on Hyper-V, vp * R * hs = vp * vs, so R =
vs/hs. The "Virtual Machine Reserve"
setting must be larger than this value.

159447 On Hyper-V platform, ddve- 1. Right click on powershell and select

installer.ps1 is run in administrator Run as administrator, then map the
elevated session because of one drive. Example: net use z: \
known issue of Windows in elevated

60 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 92 Known issues in DD VE 3.1 (continued)

Issue Problem description Workaround

number
session. The drive mapped outside of \osdev-ucs31d.datadomain.com
elevated session will be invisible to \c$ /USER:osdev
ddve-installer.ps1 \administrator Abcd!234
2. Run ddve-installer.ps1 in the same
powershell session.

160942 1. Microsoft System Center Virtual The workaround is to use the ID in

Machine Manager (SCVMM) increments of three.
does not support CPU
reservation, so the virtual
machine reserve value of a DD VE
instance deployed by ddve-
installer-sc.ps1 is 0 instead of
100.
2. User cannot create the same DD
VE name in SCVMM. When the
same DD VE name is used for
multiple instances, it is hard to
locate a particular instance.

162623 In Hyper-V environments, if the DD To resolve this issue, create a new 10 GB

VE NVRAM disk is removed, the DD disk and add it to the DD VE instance then
VE instance cannot detect the DD VE reboot the system. The new disk must be
data disk(s). attached to the first slot of the first SCSI
controller.

165964 The vserver set host command l If the Hyper-V host is joined to a
requires a different format for the domain, specify the username with
username depending on whether or the format
not the Hyper-V host is joined to a <domainuser>@<domain>.
domain.
l If the Hyper-V host is not joined to a
domain, specify the username with
the format
administrator@localhost.

169140 The disk benchmark start command There is no workaround for this issue.
increments the benchmark ID by
increments of 3 instead of by
increments of 1.

168991 DD VE will not boot when more than For DD VE, the additional controller should
12 virtual disks are added. be set to paravirtual SCSI (to ensure SCSI
is the correct type). When more than one
controller is used, please make sure that
disk 0:0 is set as the boot device in VM
BIOS setting.

179112 With SRIOV enabled for an instance If SRIOV is enabled on a AWS system and
in AWS, interface defaults to using dhcp is configured on an interface on DD
AWS jumbo frame which is 9001. VE the MTU of the interface will be set to

DD VE known issues and limitations 61

Release Notes

Table 92 Known issues in DD VE 3.1 (continued)

Issue Problem description Workaround

number
9001 by driver. The user can set this back
to whatever was previously set, but having
it at 9001 should not cause a problem.
UDP packets are never more than 9000
and TCP negotiates to something lower
during connection. Either way, the MTU at
9001 is OK for that specific network path.

179638 Due to the nature of how AWS vNIC The network interface names or their
handles IP addresses, any interface associated IP addresses get jumbled if you
(including alias interface) on the DD remove a vNIC that is in between other
VE that is statically assigned may not vNICs. For example, if you have a DD VE
be reachable if a vNIC is removed with 3 interfaces: ethV0 ethV1 ethV2 and
from DD VE. This is because AWS you remove ethV1 from the hypervisor
binds IP addresses to the vNICs. (environment) side, ethV2 becomes ethV1.
As a result, any static configuration done
on the deleted ethV1 interface will still
appear on the NIC that is renamed to
ethV1.

179964 This DD VE issue causes the file DD VE file system should be gracefully
system to panic. shutdown before changing the memory
configurations to avoid file system panic.
Avoid shutting done the DD VE VM from
vCenter.

180133 The DD VE instance may fail to If following message is found in the alert -
connect to the AWS metadata server. "Cause=Configuration invalid, instance
type - could not connect to metadata
server!" it indicates that the DD VE
instance fails to connect to the AWS
metadata server. The correct action
should be checking the networking
configuration and make sure there is a
gateway for the instance to communicate
with the internet.

181484 Exhausting boundary limits in terms Customer should follow best practices
of stream counts will cause when deploying DD VEs in the cloud
performance degradation, file system (AWS/Azure).
panics, and DD VE becomes unstable

181708 The wrong message is given when No Workaround

the DD VE memory configuration is
incorrect. The files system displays
"File system is coming up" and hangs.

185557 In some cases, after cleaning is The shutdown error can usually be safely
stopped or aborted during select ignored in this case. The user should issue
phase, the file system may not be the command again. Commands that fail
able to shutdown cleanly. An alert due to this shutdown error, usually
may be raised, such as "The succeed when issued again.
filesystem failed to shutdown cleanly.

62 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 92 Known issues in DD VE 3.1 (continued)

Issue Problem description Workaround

number
This issue can also affect other CLIs
that trigger "filesystem disable"
command. For example, "system
upgrade" command may return error
"**** Upgrade failed: file system
shutdown error."

188149 If the system has already been Workaround is to reboot or wait 24 hours.
configured to use license server and
already checked out some served
licenses, after the system upgrade,
those licenses may go into grace
period and some unexpected alerts
may be generated. Users can first run
"telnet <license-server-ip> <license-
server-port> to verify the connection
between the DD VE and the license
server. If the connection is good,
users can wait for 24 hours to check
if the licenses become "Served"
again.

189747 DD Boost connection failures may be Turn off two-way password

observed when using two-way- authentication.
password authentication and using
multiple connections in parallel.

191982 When DD VE is deployed with a 1. Use a short hostname (with a

specific DNS-specific setup, Azure maximum length of 12 characters)
will default with a 51-character when you initially deploy.
hostname.
2. If you did not use a short hostname at
initial deployment, change the
hostname (using a shorter length) and
generate a new certificate.

192308 When DD VE is deployed in Azure, Azure requires the use of an SMTP relay
the DD VE instance cannot send to send emails to external domains. The
support emails to an external domain. Microsoft Azure Support Team Blog post
Sending E-Mail from Azure Compute
Resource to External Domains provides
more information.

194219 Due to a KVM issue with NFS By default on NFS storage, a thin
storage, the user is unable to add provisioned disk will be created.
disks using the script provided in the Deployment script will have option (-p) to
build. specify the provisioning type. This option
works only on NFS storage.

201157 During the deployment of DD VE in Skip the network configuration in the

Azure, the hostname will be config wizard first. You can use commands
configured as the VM's name and to do your network configuration manually
DHCP will be enabled on the NIC by later.

DD VE known issues and limitations 63

Release Notes

Table 92 Known issues in DD VE 3.1 (continued)

Issue Problem description Workaround

number
default. If you reconfig the network in
config wizard, the hostname will be
reset as localhost.

201301 When configuring ATOS on DD VE, There is no workaround.

verify that the maximum length of the
bucket name (for AWS) or the
container name (for Azure) does not
exceed 48 characters. Setup will not
complete if the names exceed 48
characters.

201377 The user is unable to login to DD VE Add following step during the AD domain
via the GUI using active directory joining: net set domainname <name>
credentials and is locked out of Data after net set dns <ip> in domain
Domain. joining steps.

203810 If a system encounters metadata The system may be recovered by adding

storage full situation before hitting additional metadata storage to the cloud
the cloud-capacity full condition, the tier and then bringing up the file system:
file system will panic.
l storage add tier cloud <dev>
l filesys enable
l run filesys show space to ensure the
system is configured with
recommended metadata for the
physical capacity on the cloud-tier (all
the cloud-units together)
l add additional metadata capacity to
reach the recommended limits if
needed

204558 If the ESRS host is renamed or due to Follow ESRS registration procedures and
DNS resolution issues, the ability of if the registration fails, validate that the
the ESRS registration process to ESRS short and FQDN hostnames have
complete successfully from the Data proper forward and reverse lookups. In the
Domain may be affected. case of the ESRS host being renamed
after installation, the host certificate may
no longer match the host name. If this is
the case, contact support for assistance in
discovering the certificate name and
approach for resolution.

N/A DD Boost hard stream limits are only There is no workaround for this limitation.
enforced with the DD Boost plug-in
for Open Storage versions 3.2 and
higher.

N/A Data may continue to get encrypted The workaround is to restart the Data
after deleting the evaluation Domain File System (DDFS) on the DD VE
encryption license. instance.

64 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 92 Known issues in DD VE 3.1 (continued)

Issue Problem description Workaround

number
N/A Taking VMware snapshots of the DD There is no workaround for this limitation.
VE virtual machine is not supported.

N/A VMware vCenter still prompts to Do not install VMware tools when
install VMware tools even though DD prompted by vCenter.
VE uses a different set of virtual
machine tools.

N/A DD VE does not support SMT. When There is no workaround for this limitation.
a DD VE instance is replicating data
to a Data Domain system with SMT,
the security mode of the destination
tenant-unit cannot be set to strict.

N/A DD VE does not support instant There is no workaround for this limitation.
access because it will not meet the
IOPS requirement to support this
feature based on the DD VE
configuration requirements.

N/A Issues accessing DD VE instances The workaround is to re-apply the license

where the license is in the grace after purchasing a DD VE capacity license.
period.

N/A Workloads with a large number of There is no workaround for this limitation.
small files may impact DD VE
performance and file system cleaning.

N/A Running a DD VE instance disrupts To avoid this issue, manually specify an

the resource slot size calculations upper limit for the CPU and memory
required for VMware vSphere high reservations in vSphere. The ESXi and
availability. vCenter Server Documentation available on
the VMware website (https://
www.vmware.com/support/pubs/)
provides more information.

DD Management Center known issues and limitations

Table 93 DD Management Center known issues

Issue # Problem Description Workaround/Resolution

204989 Exception may be encountered while creating The user may login interactively
DDMC on Azure on Windows 10 with the latest by changing sample script from
Azure powershell toolset. "cred = New-Object -
TypeName pscredential -
ArgumentList $userName,
$pass" to "$cred = New-
Object -TypeName
pscredential -
ArgumentList $userName".

DD Management Center known issues and limitations 65

Release Notes

Table 93 DD Management Center known issues (continued)

Issue # Problem Description Workaround/Resolution

204558 If the ESRS host is renamed or due to DNS Follow ESRS registration
resolution issues, the ability of the ESRS procedures and if the registration
registration process to complete successfully fails, validate that the ESRS short
from the Data Domain may be affected. and FQDN hostnames have
proper forward and reverse
lookups. In the case of the ESRS
host being renamed after
installation, the host certificate
may no longer match the host
name. If this is the case, contact
support for assistance in
discovering the certificate name
and approach for resolution.

203354 DD Management Center may run low on Delete core files.

available capacity in /ddr/var/cores.

201507 Upgrade dialog box and Jobs page show status Upgrade may or may not have
of upgrade jobs. Upgrade job waits for 30 succeeded. If upgrade was
minutes for system to restart and reconnect to successful, inventory page will
same network address. The job is marked as display the new serial number
failed 30 minutes has passed. after about 30 minutes since DD
Management Center collects
configuration data from Data
Domain systems in 15 minute
interval.

182029 IPv6 gateway is not supported on Amazon Web There is no workaround.

Services.

181053 Adding a Data Domain system or DD VE running Allow weak ciphers on DD

an earlier version of DD OS will initially fail Management Center through the
during the SSL handshake due to removal of adminaccess option set
weak ciphers by default in newer DD cipher-list command so SSL
Management Center version. handshake happens between
earlier version of Data Domain
systems and DD Management
Center. #adminaccess
option set cipher-list
"ALL:!ADH:!EXPORT56:!
EXPORT40:RC4+RSA:+HIGH:!
MEDIUM:!LOW:!
SSLv2:+EXP@STRENGTH"

178963 After upgrading from 1.4.5.2 to 2.0.0.1, DD Open the compatibility view
Management Center GUI returns a blank white settings dialog box and clear the
screen after logging in via IE11. selection option for showing
intranet sites in compatibility
view.

161657 Launching Data Domain System Manager may Log in to DD Management Center
fail with the error Invalid user as admin.
"<username>" for a system running DD OS
5.7 with Extended Retention.

66 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 93 DD Management Center known issues (continued)

Issue # Problem Description Workaround/Resolution

133919 In the following situations, you may not be able The new data is visible in the
to select the most recent data point in a chart: chart, but you cannot select the
actual data point. In both cases,
1. You adjust the visible range of the chart by
to see the new data, update the
clicking and dragging within the chart.
range of the chart by moving the
When dragged back to show recent data,
navigator bar at the top of the
you cannot select the most recent data
chart.
point.
2. An auto-refresh has occurred, and a new
data point has been added to the chart.

122835 Report generation fails when the max report Older reports can be pruned to
limit of 500 is reached. allow user to generate current
reports.

114592 During an upgrade, you may get the error: This error message can be safely
Unknown registry ignored. This group does not exist
key:group.upgrade.skip_ver_chec on DD Management Center.
k.
89982 If you browse to the Data Domain Replication There is no workaround.
page and click the Lag button to open the filter
and then press Backspace on the keyboard, the
navigation occurs as expected, but the filter
stays open.

77129 You cannot log in to the DD Management The workaround is to log in using
Center if the /ddr/var/ partition (also known the CLI or else wait 5–10 minutes
as /ddvar) is full, or nearly full, and the before logging in with the GUI.
monitored Data Domain systems use several (For information on how to free
different DD OS versions. up space on the /ddr/var/
partition, see the Data Domain
Operating System Administration
Guide for the correct version of
the DD OS.)

DD OS and DD VE environment and system requirements

In order for DD OS 6.1.2.30 and DD VE 4.0 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.

DD OS and DD VE environment and system requirements 67

Release Notes

Supported systems
DD OS 6.1.2.30 is supported on the following Data Domain systems, running DD OS
5.7 or later, and Data Domain Virtual Editions (DD VE) versions:
l Series: DD160, DD620, DD640, DD670, DD860, DD890, DD990, DD2200, DD2500,
DD3300, DD4200, DD4500, DD6300, DD6800, DD7200, DD9300, DD9500, and
DD9800
l Series with the Data Domain Extended Retention software option: DD860, DD990,
DD4200, DD4500, DD6800, DD7200, DD9300, DD9500, and DD9800
l Virtual Edition versions: DD VE 2.0 (RPM upgrade), DD VE 3.0, DD VE 3.1, and DD
VE 4.0.

Note

The Global Deduplication Array (GDA) is not supported in DD OS 5.5 and later.

Supported virtualization platforms

DD VE is supported on the following virtualization platforms:
l VMware ESXi: Versions 5.5, 6.0, and 6.5.
l Microsoft Hyper-V: 2012 R2 and 2016.
l Amazon Web Services (AWS)
l Azure

Supported browsers
The following browsers are supported for use with the Data Domain System Manager:

Table 94 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.

Supported Flash versions

The latest version of Flash is recommended for use with the Data Domain System
Manager.

68 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

DD Management Center environment and system

requirements
For compatibility with this release of DD Management Center, make sure your DD
Management Center system and client system tools meet the following environment
and system requirements.

Supported Data Domain Systems

Data Domain Management Center 6.1 supports management of the following Data
Domain systems, running DD OS 5.7 or later, and Data Domain Virtual Editions (DD
VE):
l The DD160, DD620, DD640, DD670, DD860, DD890, DD990, DD2200, DD2500,
DD3300, DD4200, DD4500, DD6300, DD6800, DD7200, DD9300, DD9500, and
DD9800
l Virtual Edition Versions: DD VE 2.0, DD VE 3.0, and DD VE 4.0.

Note

The DD3300 should not be added and managed by DD Management Center releases
prior to 6.1.1.1. If a DD3300 is managed by DD Management Center 2.0.x/6.0.x/6.1.0,
the following errors might be encountered:
l The DD3300 may show as a normal Data Domain system when launching the Data
Domain System Manager (DDSM), but the hardware pages show exceptions.
l The DD3300 may display as DD VE and the license pages will not work to launch
DDSM.

Supported ESXi versions

The following VMware ESXi versions are supported:
l ESXi 5.1
l ESXi 5.5
l ESXi 6.0
l ESXi 6.5

Supported cloud infrastructures

The following cloud platforms and environments are supported:
l Amazon Web Servicex (AWS)
l Microsoft Azure

Supported Hyper-V versions

The following Hyper-V versions are supported:
l Hyper-V for Windows Server 2012 R2

DD Management Center environment and system requirements 69

Release Notes

l Hyper-V on Windows Server 2016

Supported browsers
The following browsers are supported:

Table 95 Supported browsers

Microsoft Windows 7, 8, and 10 Apple OS X

Microsoft Internet Explorer 11 --

Microsoft Edge (only on Windows 10) --

Google Chrome Google Chrome

Mozilla Firefox 30 or higher Mozilla Firefox 30 and higher

Other browser versions may also work; these particular versions have been validated.

Showing a prompt dialog in Internet Explorer

To enable file downloads to show a prompt dialog in Internet Explorer, it is
recommended that the Security Zone, in which the Data Domain Management Center
host name or IP address belongs, has the Automatic prompting for file downloads
option set to Enabled for that Security Zone.
Procedure
1. In Internet Explorer, select Tools > Internet Options to see the Internet
Options dialog.
2. Select the Security tab, then select the security zone that applies to Data
Domain Management Center.
3. Select the Custom level... button to open the Security Settings dialog, then
scroll to the Downloads section.
4. For the Automatic prompting for downloads option, select the Enabled
button, then select OK.
5. If a prompt appears asking if you are sure you want to change the settings for
this security zone, select Yes.
6. Select OK again to exit the Internet Options dialog.

Required Flash versions

Adobe Flash is not required.
However, if you launch DD System Manager from DD Management Center, Flash is
needed to view DD System Manager charts. The most current version is
recommended.

Software media, organization, and files

Learn about software media, organization, and files required for 6.1.2.30.
Required update
We recommend that you keep your Data Domain system up to date by upgrading to
the latest software version.

70 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

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.1
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 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 a Software License:

l A new system running DD OS 6.1 (except DD2200)
l Existing systems upgraded to DD OS 6.1 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.

Software License Central will facilitate electronic licensing for Data Domain systems
through the Software Licensing Central (SLC) Portal
Ensure that you have the following:
1. License Authorization Code (LAC)-The LAC is sent by email from us.
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 ID (virtual systems).
3. License file downloaded from the Software Licensing Central site.

Note

When you obtain the original license file name, do not enter the comma in the license
file name. DD OS will not accept the name if the comma is used.

Obtaining and installing product licenses 71

Release Notes

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

72 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Note

The Initial License Configuration option appears when a DD VE is launched for the first
time. The user may configure the license here or wait and choose to configure from
Licenses Page later.

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

Using the Served License Model for DD VE

Results
l The Served Licensing Model for DD VE provides the solution for managing
licensing for DD VE deployment.
l You retrieve the license from the Software Licensing Central (SLC) portal and load
the license into the license server software (the hardware server is not provided).
l You download the License Server installers from Support.

Obtaining and installing product licenses 73

Release Notes

Note

The licensing served model is not supported on physical Data Domain systems, for DD
VE only.

You will deploy the DD VE capacity licensing and configure the DD VE to talk to the
license server. Using a CLI, you determine how much capacity to deploy. This capacity
is specified within the DD VE which checks out the amount specified in addition to
including Replication, Boost, and Encryption options. The DD VE also automatically
checks out feature licenses when checking out the capacity.

Note

1. If you have issues deploying or troubleshooting the license server, contact Global
Services to submit a Service Request (via phone, chat, or web site) for "License
Server".
2. If you have issues with DD VE, contact Data Domain Support who will utilize
Service Center tools to address your issue.

The Results page will confirm the license was successfully installed.
License Server (Common License Server Platforms)
l The physical server to run the common license server software is provided by
customer.
l Supported on Windows and Linux Platforms
n Windows 2008 (32 and 64 bit), Windows 2012 (64 bit)
n Linux Red Hat Enterprise Linux 6.x , 7.x; SuSE Linux Enterprise Server 10.x,11.x,
12.x

74 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

n eLicensing Common Platform

Install and upgrade

Learn how to install and upgrade DD Operating System, DD Virtual Edition, and DD
Management Center.

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 license. If you
are not applying new features, then you can use DD OS 6.1 or 6.1.1.x 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 68, 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.1

Only Data Domain systems running DD OS 5.7.x and 6.0 can upgrade directly to DD
OS 6.1. This restriction is due to the RPM signing. Typically when upgrading DD OS,
we only support the ability to upgrade up to two release families at a time (for
example, 5.4 to 5.6, or 5.5 to 5.7, and so forth). In order to upgrade to release 6.1
from a release family earlier than 5.7, you need to upgrade in steps. See the latest 5.4,
5.5, 5.6, 5.7 release notes for upgrade instructions as appropriate for the version the
system is running for exact upgrade steps. The most current release notes for all
versions of DD OS can be found on the Online Support site.

Install and upgrade 75

Release Notes

Note

DD OS 6.0 is the next release after DD OS 5.7.

If the upgrade plan calls for multiple successive upgrades (for example, from 5.1 to 5.4
to 5.6 and then to 6.1), 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.7.1.x or later, download the 6.1 upgrade file from the
support download site, and follow the upgrade instructions, as described in Upgrading
to DD OS version 6.1.2.30 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.1:
l When upgrading to a DD OS 6.1, the upgrade will not proceed if LUN numbers
greater than 255 and initiators are present in the same group. The upgrade will
proceed once the LUN numbers greater than 255 have been removed from the
identified groups or one or more initiators are removed from the identified group. It
is necessary to remove (at an operating system level) any of the VTL devices from
the initiators that are 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 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 Ensure 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
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 the 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 the environment. If you know that the SE

76 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

has overridden registry parameters, contact the support provider or visit us online
at the Online Support site before upgrading to 6.1.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 Do not attempt to power off the system while the upgrade process is running.
l For an HA system, ensure 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.)
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:
# net show
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

77
Release Notes

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.
# 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.7.x or 6.0.x can upgrade
directly to 6.1. 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.

78 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

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

79
Release Notes

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

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.1
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 5.7 to 6.0 and then 6.0 to 6.1, 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
you want to upgrade. Consult the following publications, which are available on the
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.
l 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."
Procedure
1. Download the upgrade file for DD OS 6.1.2.30- 615547 from the appropriate
download or support site.
2. Store the file, 6.1.2.30- 615547.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

80 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

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.1.2.30,

a. Log out of the Data Domain CLI.

b. Log in to the Data Domain System Manager 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.

c. Click the name of the host system you are upgrading in the Navigation pane.
d. Select Maintenance > System.
e. From the Upgrade Packages Available on this Data Domain System list,
select the checkbox of the image to use for the upgrade.
f. Select Perform System Upgrade.
g. The Upgrade System dialog box appears.
h. Verify the version of the target image (the upgrade image) is 6.1.2.30-
615547 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.

81
Release Notes

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
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.1.2.30 using the CLI, issue
the command: (For an HA system, issue the command on the active node.)
system upgrade start 6.1.2.30- 615547.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.1.2.30- 615547.rpm

The general effects of upgrading the Data Domain system to DD OS 6.1.2.30 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.1.2.30-
615547.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
Online Support site.

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 (Secure Remote Services VE) gateway. This change requires a
reconfiguration of the Data Domain system to ConnectEMC after the upgrade.

Note

ConnectEMC only works with Service Remote Services VE (V3) and can not send
emails with older versions of Service Remote Services or on it s own. If ConnectEMC
has been used with previous releases of DD OS (e.g., 5.7 or 5.6), the Service Remote
Services VE server configuration will need to be re-entered as it was removed during
the upgrade process due to the to technology upgrade.

82 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Note

If an older Service Remote Services gateway is being used, the Service Remote
Services 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.

Install and upgrade

Learn how to install and upgrade DD VE 4.0
Upgrading DD VE 4.0
The DD VE 4.0 uses DD OS 6.1.2.5 (To upgrade DD VE 3.1 to DD VE 4.0, the user
needs to use RPM upgrade of DD OS to DD OS 6.1.2.5 level.) Please refer to the Data
Domain Operating System 6.1.2.5 Administration Guide and the Data Domain Virtual
Edition 4.0 Installation and Administration Guide for additional information.

Note

DD VE 3.1 can be upgraded to DD VE 4.0 by carrying out DD OS 6.1.2.5 RPM upgrade.

Upgrading DD Management Center

You can upgrade directly to Data Domain Management Center 6.1 only from a system
running DD Management Center 1.4.5 or 2.x.

Note

The DD Management Center release family directly after 2.0 is 6.1; there are no 3.x,
4.x, or 5.x versions. Also, DD Management Center 2.0 is the release directly after
1.4.5. There are no DD Management Center 1.5 - 1.9 release families.

To upgrade to DD Management Center 6.1 from a release earlier than 1.4.5, you will
need to upgrade in steps. DD Management Center only supports upgrading by up to
two release families at a time (1.1 to 1.2 or 1.3; 1.2 to 1.3 or 1.4; 1.3 to 1.4 or 1.4.5; 1.4.5
to 2.0 or 6.1).
For the exact upgrade steps, see the DD Management Center Installation and
Administration Guide for your specific release, which can be found on the online
support site.

Install and upgrade 83

Release Notes

DD Management Center version support matrix

Table 96 DD Management Center version support matrix, DD OS 5.4 - 5.6

DDMC DD OS release: level of support Supported Supported Supported

Release browsersa ESXi versions Hyper-V
5.4 5.5.0 5.5.1 5.6

DDMC 1.1 [base no support no support no support l Microsoft l ESXi 4.1 no support
release] for new for new Windows XP Pro
supports features in features in
l ESXi 5.0
– IE 8, Mozilla
all features 5.5.0 & 5.5.1 & Firefox 15 & l ESXi 5.1
higher higher higher, Google
Chrome
l Microsoft
Windows 7 – IE
9, Mozilla
Firefox 15 &
higher, Google
Chrome
l Apple OS X –
Mozilla Firefox
15 & higher,
Google Chrome

DDMC 1.2 supports [base no support no support l Microsoft l ESXi 5.0 no support
all features release] for new for new Windows – IE 9,
supports all features in features in
l ESXi 5.1
Mozilla Firefox
features 5.5.1 & 5.6 & 30 & higher, l ESXi 5.5
higher higher Google Chrome
l Apple OS X –
Mozilla Firefox
30 & higher,
Google Chrome

DDMC 1.3 supports supports all supports all [base l Microsoft l ESXi 5.0 no support
all features features features release] Windows – IE 9,
supports
l ESXi 5.1
10, 11; Mozilla
all features Firefox 30 & l ESXi 5.5
higher; Google
Chrome
l Apple OS X –
Mozilla Firefox
30 & higher,
Google Chrome

DDMC 1.4 no support supports all supports all supports l Microsoft l ESXi 5.1 no support
features features all features Windows – IE 9, l ESXi 5.5
10, 11; Mozilla
Firefox 30 & l ESXi 6.0
higher; Google
Chrome

84 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Table 96 DD Management Center version support matrix, DD OS 5.4 - 5.6 (continued)

DDMC DD OS release: level of support Supported Supported Supported

Release browsersa ESXi versions Hyper-V
5.4 5.5.0 5.5.1 5.6

l Apple OS X –
Mozilla Firefox
30 & higher,
Google Chrome

DDMC no support supports all supports all supports l Microsoft l ESXi 5.1 no support
1.4.5b features features all features Windows – IE 9, l ESXi 5.5
10, 11; Mozilla
Firefox 30 & l ESXi 6.0
higher; Google
Chrome
l Apple OS X –
Mozilla Firefox
30 & higher,
Google Chrome

DDMC no support no support no support supports l Microsoft l ESXi 5.1 Windows

2.0 all features Windows – IE11, Server 2012 R2.
l ESXi 5.5
Mozilla Firefox
30 & higher; l ESXi 6.0
Google Chrome
l Microsoft Edge
(only on
Windows 10)
l Apple OS X –
Mozilla Firefox
30 & higher,
Google Chrome

a. Other browser versions may also work; these particular versions have been validated.
b. SMT tenant unit creation is not supported for DD VE 2.0. DD VE 2.0 instances are filtered from the Select Host System
page in the Create Tenant Unit wizard.

Table 97 DD Management Center version support matrix, DD OS 5.7 - 6.1

DDMC DD OS release: level of support Supported Supported Supported

Release browsersa ESXi versions Hyper-V
5.7 6.0 6.1

DDMC 1.4 [base release] no support for no support for l Microsoft l ESXi 5.1 no support
all features in new features new features in Windows – IE 9,
DD OS 5.7.0.x in 6.0 & higher 6.1 & higher
l ESXi 5.5
10, 11; Mozilla
supported. Firefox 30 & l ESXi 6.0
(new features higher; Google
in 5.7.1 not Chrome
supported)
l Apple OS X –
Mozilla Firefox 30

DD Management Center version support matrix 85

Release Notes

Table 97 DD Management Center version support matrix, DD OS 5.7 - 6.1 (continued)

DDMC DD OS release: level of support Supported Supported Supported

Release browsersa ESXi versions Hyper-V
5.7 6.0 6.1

& higher, Google

Chrome

DDMC [base release] no support for no support for l Microsoft l ESXi 5.1 no support
1.4.5b supports all new features new features in Windows – IE 9,
features in 6.0 & higher 6.1 & higher
l ESXi 5.5
10, 11; Mozilla
Firefox 30 & l ESXi 6.0
higher; Google
Chrome
l Apple OS X –
Mozilla Firefox 30
& higher, Google
Chrome

DDMC 2.0 supports all [base release] no support for l Microsoft l ESXi 5.1 Windows Server
features supports all new features in Windows – IE11, 2012 R2.
features 6.1 & higher
l ESXi 5.5
Mozilla Firefox 30
& higher; Google l ESXi 6.0
Chrome
l Microsoft Edge
(only on Windows
10)
l Apple OS X –
Mozilla Firefox 30
& higher, Google
Chrome

DDMC no support for supports all [base release] l Microsoft l ESXi 5.1 Windows Server
6.1c DD OS 5.7 features supports all Windows – IE11, 2012 R2.
earlier than features
l ESXi 5.5
Mozilla Firefox 30
5.7.4.0 & higher; Google l ESXi 6.0
Chrome
l Microsoft Edge
(only on Windows
10)
l Apple OS X –
Mozilla Firefox 30
& higher, Google
Chrome

a. Other browser versions may also work; these particular versions have been validated.
b. SMT tenant unit creation is not supported for DD VE 2.0. DD VE 2.0 instances are filtered from the Select Host System
page in the Create Tenant Unit wizard.
c. The DD Management Center release family directly after 2.0 is 6.1; there are no 3.x, 4.x, or 5.x versions.

DD MC 6.1 and later are unable to manage DD running DD OS 5.7 earlier than 5.7.4.0. See KB #518510 for additional
information.

86 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

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

Additional Resources 87
Release Notes

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

88 Data Domain Operating System, Data Domain Virtual Edition 4.0 Update 4, and Data Domain Management
Center 6.1.2.30 Release Notes
 Release Notes

Copyright © 2019 Dell Inc. or its subsidiaries. All rights reserved.

Published February 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 89