Docu53897 Data Domain Operating System Version 5.4.3.0 Release Notes Directed Availability

RELEASE NOTES
EMC
DD OS
Release number 5.4.3.0
EMC Data Domain Operating System
Release Notes
302-001-063
REV. 02
July, 2014
Always check the appropriate EMC support site for the latest revision of this document
before proceeding. Any printed or CD-based version of this document may be out of date.
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications. Please send your opinions of this document to
DPAD.Doc.Feedback@emc.com.
u
Revision History......................................................................................................... 2
u
New Features in 5.4....................................................................................................2
u
Command Changes in Version 5.4............................................................................16
u
Changes in DD OS Version 5.4 Management Information Base (MIB)........................ 26
u
Changes in DD OS Version 5.4 System Events.......................................................... 28
u
Fixed Issues............................................................................................................. 31
u
Environment and System Requirements................................................................... 66
u
Known Issues and Limitations..................................................................................67
u
Viewing Documents on the EMC Online Support Site................................................ 74
u
Open Source Software..............................................................................................74
u
DD OS Version 5.4.3.0 Upgrade Instructions............................................................ 75
u
Troubleshooting and Getting Help............................................................................ 79
Revision History
The following table presents the revision history of this document.
Table 1
Revision Date Description
01 June 17, 2014 Initial publication.
02 July 1, 2014 Added new known issues discovered since Revision 02;
corrected list of fixed bugs in DD OS 5.4.1.0.
New Features in 5.4
This version of DD OS offers new systems and software enhancements.
New Midrange Systems
The DD OS 5.4 release introduces four new systems to consolidate backup and archive
workloads for medium and high-end enterprises.
DD7200 System
Positioned below the DD990 in the high-end of the EMC Data Domain product line, the
new DD7200 system includes the following features:
u
Performance up to 26.0 TB/hr for aggregate writes using DD Boost.
u
Performance up to 11.9 TB/hr for aggregate writes using NFS.
u
External expansion up to 428 TB usable capacity.
u
External expansion up to 1.7 PB usable capacity with DD Extended Retention software
option.
u
Increased stream counts for backup and archiving workloads:
l
Up to 540 concurrent backup write streams.
l
Up to 150 concurrent backup read streams.
l
Up to 540 destination replication streams.
l
Up to 270 source replication streams.
l
Consolidate replication from up to 270 remote sites.
u
4U chassis, fits industry standard racks.
u
Dual-socket, 8-core Intel Xeon Sandy Bridge processors.
u
Two memory configurations:
l
Entry memory of 128 GB, supports up to 285 TB usable capacity.
l
Expanded memory of 256 GB, supports up to 428 TB usable capacity.
l
Memory upgrade option available.
u
Redundant, hot-swap 1+1 power units, 200-240 V~.
u
Uses EMC IO modules for optional IO connectivity instead of PCIe cards.
RELEASE NOTES
2 EMC DD OS 5.4.3.0 RELEASE NOTES
u
Two quad-port 6 Gb/s Serial Attached SCSI II (SAS) IO modules for external storage.
u
Connectivity (four SAS IO modules with DD Extended Retention).
u
One NVRAM IO module with 4 GB memory and remote battery backup.
u
The Management module provides a LAN management port, serial port and USB port.
u
Increased connectivity with support for up to six optional IO modules:
l
Up to four dual-port optical 10 Gbit Ethernet IO modules with LC interfaces.
l
Up to four dual-port direct-attach (DA) copper 10 Gbit Ethernet IO modules with
SFP+ interfaces.
l
Up to four quad-port copper 1 Gbit Ethernet IO modules.
l
Up to four combo 1 Gbit Ethernet IO modules, 2 ports optical + 2 ports copper.
l
Up to four dual-port 8 Gbit Fibre Channel IO modules for VTL or DD Boost.
u
External expansion using ES30 shelves with 3 TB or 2 TB SAS drives:
l
Minimum of 3 shelves for valid configuration, of any capacity.
l
Supports up to 20 shelves for active tier, not to exceed 428 TB usable.
l
Supports up to 56 shelves with DD Extended Retention, not to exceed 1.7 PB
usable.
u
Supports ES30 SATA shelves with 3 TB, 2 TB or 1 TB drives from controller upgrade.
u
Supports ES20 SATA shelves with 2 TB or 1 TB drives from controller upgrade.
u
Available as factory-configured solution in Data Domain rack with ES30 SAS shelves.
u
Available pre-configured from factory as integrated solution with Avamar Data Store.
DD4500 System
Positioned below the DD7200 in the EMC Data Domain product line, the new midrange
DD4500 system includes the following features:
u
u
u
u
External expansion up to 1.1 PB usable capacity with DD Extended Retention software
option.
u
l
l
l
l
l
u
u
u
One memory configuration of 192 GB.
u
u
u
EMC Data Domain Operating System Release Notes
New Midrange Systems 3
u
u
u
u
l
l
SFP+ interfaces.
l
l
l
u
l
Minimum of 2 shelves for valid configuration, of any capacity.
l
l
Supports up to 40 shelves with DD Extended Retention, not to exceed 1.1 PB
usable.
DD4200 System
u
u
u
u
External expansion up to 570 TB usable capacity with DD Extended Retention
software option.
u
Stream counts for DD4200 configurations with minimum of 2 shelves of any drive
capacity:
l
l
l
l
l
u
u
u
One memory configuration of 128 GB.
u
u
u
u
u
u
u
RELEASE NOTES
l
l
SFP+ interfaces.
l
l
l
u
l
l
Supports up to 32 shelves with DD Extended Retention, not to exceed 570 TB
usable.
u
Supports ES30 SATA shelves with 3 TB, 2 TB or 1 TB drives from controller upgrade.
u
Supports ES20 SATA shelves with 2 TB or 1 TB drives from controller upgrade.
u
u
DD2500 System
u
u
u
External expansion up to 133 TB usable capacity using ES30 SAS shelves with 3 TB
drives.
u
l
l
l
l
l
u
u
Single-socket, 8-core Intel Xeon Sandy Bridge processors.
u
Two system capacity configurations available pre-configured from factory:
l
Seven 3 TB SAS HDDs, provides 11.2 TB usable capacity, one RAID6 group.
l
Twelve 3 TB SAS HDDs, provides 25.8 TB usable capacity, one RAID6 group.
l
Upgrade option available with five 3 TB SAS HDDs as second RAID6 group.
u
Two memory configurations:
l
Entry memory of 32 GB, supports up to 51 TB usable capacity.
l
Expanded memory of 64 GB, supports up to 133 TB usable capacity.
l
Memory upgrade option available.
u
Redundant, hot-swap 1+1 power units, 100-120 / 200-240 V~.
u
u
New Midrange Systems 5
u
Standard IO on motherboard includes serial port, USB port, four 1 Gbit Ethernet RJ45
ports, and two 10GBase-T Ethernet RJ45 ports.
u
Increased connectivity with support for up to three optional IO modules:
l
Up to three dual-port optical 10 Gbit Ethernet IO modules with LC interfaces.
l
Up to three dual-port direct-attach (DA) copper 10 Gbit Ethernet IO modules with
SFP+ interfaces.
l
Up to three quad-port copper 1 Gbit Ethernet IO modules.
l
Up to three combo 1 Gbit Ethernet IO modules, 2 ports optical + 2 ports copper.
l
Up to three dual-port 8 Gbit Fibre Channel IO modules for VTL or DD Boost.
u
One optional quad-port 6 Gb/s Serial Attached SCSI II (SAS) IO module for external
storage connectivity (uses reserved slot; does not require one of three optional IO
slots).
u
l
u
No support for ES30 or ES20 SATA shelves.
u
u
DD990 Enhancements
u
ES30 Expansion Shelf with 3TB SATA drives for the DD990:
l
Supported on DD990 platforms only.
Applies to both active tier and retention tier when the DD Extended Retention
software option is installed and configured on the DD990 system.
l
15 x 3TB SATA 7200 rpm drives, 45 TB raw capacity.
l
ES30 shelves with 3TB SATA drives can be mixed with 1TB and 2TB ES30 shelves
on same DD990 SAS chain.
l
DD990 and ES30 shelves with 3TB SATA drive can be pre-configured in rack or
configured without a rack.
l
A valid DD990 configuration with or without the DD Extended Retention software
option requires a minimum of four (4) shelves for the active tier, regardless of
shelf capacity.
l
A minimum of one shelf is required for the retention tier, if system includes a
retention tier.
u
Improved scalability by 50% for DD990 with DD Extended Retention software option:
l
Using 3TB SATA drives, the total system now supports 2.5 PB raw or 2.0 PB
usable.
Increase in capacity applies only for the retention tier.
No change to maximum capacity for the active tier remains 570 TB usable.
l
No change in the maximum number of ES30 expansion shelves remains at 56.
ES30 Expansion Shelf with SAS Drives
The ES30 Expansion Shelf is now available with SAS drives for external storage
expansion featuring:
RELEASE NOTES
u
Serial Attached SCSI (SAS) 2.0 interface on controllers.
u
Two drive choices:
l
SAS (6 Gb/s) 3 TB, 7200 RPM.
l
SAS (6 Gb/s) 2 TB, 7200 RPM.
u
New SAS cables are needed to connect to Data Domain systems:
l
To connect new ES30 SAS shelves and existing ES30 SATA shelves to DD7200,
DD4500, DD4200 and DD2500, cables will require a mini-SAS connector on one
end to connect to ES30 controller ports, and a mini-SAS-HD connector on the
other end to connect to the SAS IO Module in the Data Domain system. These
cables are available in 1, 2, 3, and 5M lengths.
l
To connect ES20 SATA shelves to DD7200, DD4500 and DD4200, cables will
require an Infiniband-style connector on one end to connect to ES20 controller
ports, and a mini-SAS HD connector on the other end to connect to the SAS IO
Module in the Data Domain system. These cables are available in 1, 2, and 5M
lengths.
u
No difference in power consumption or performance compared to ES30 SATA shelves.
u
Supported only on DD7200, DD4500, DD4200 and DD2500 with DD OS 5.4.
u
Not supported on previous generation Data Domain systems.
Software Features
This version of DD OS offers a wide range of important software enhancements.
SMB (Server Message Block) Signing
This topic describes a new feature introduced in version 5.4.1.0 of DD OS.
SMB (Server Message Block) signing is a security mechanism that improves the security
of the SMB protocol. When enabled, it is possible for clients that support SMB signing to
connect, although it is also possible for clients that do not support SMB signing to
connect. When SMB signing is required, both computers in the SMB connection must
support SMB signing, and the SMB connection will not be successful if one computer
does not support SMB signing.
Note
This version of DD OS implements the SMB1 protocol.
NOTICE
SMB signing is disabled by default for performance reasons. When enabled, this feature
can cause throughput performance drops of up to 29 percent for reads and up to 50
percent for writes. Individual system performance will vary.
On the DD OS version where it is supported, you can configure SMB signing using the
server signing CIFS option. There are three possible values for server signing: disabled,
auto, and mandatory:
u
When server signing is set to disabled, SMB signing is disabled. This is the default.
u
When server signing is set to auto, SMB signing is offered but not enforced.
u
When server signing is set to mandatory, SMB signing is required. Both computers in
the SMB connection must have SMB signing enabled.
You can use these CLI commands to configure SMB signing:
Software Features 7
cifs option set "server signing" auto
Purpose: Sets server signing to automatic.
cifs option set "server signing" mandatory
Purpose: Sets server signing to mandatory.
cifs option reset "server signing"
Purpose: Resets server signing to the default (disabled).
As a best practice, whenever you want to change the SMB signing options, first disable
and then enable (restart) the CIFS service using the following CLI commands:
cifs disable
cifs enable
You can also use the System Manager interface to display whether the SMB server
signing option is disabled or set to auto or mandatory. To view this setting in the
interface, navigate to: Data Management > CIFS > Configuration tab. In the Options area,
find the value for the server signing option.
Figure 1 SMB Signing in the System Manager
Replication Enhancements
u
Supports MTree replication and data migration to the retention tier on the same NFS,
CIFS, VTL or NDMP MTree to enable DR protection for long-term retention data.
l
Data migration policies from active tier to retention tier are configured
independently on the source and destination systems.
RELEASE NOTES
l
Supports one-way and bi-directional replication topologies between Data Domain
systems with DD Extended Retention software option.
l
If the source system has DD Extended Retention enabled, then the destination
must also have DD Extended Retention software option enabled.
u
Supports MTree replication for archive data locked with DD Retention Lock
Compliance, enabling flexible disaster recovery configurations for Data Domain
systems with backup and compliance archive data.
u
Supports replication of the retention period for user-created snapshots via MTree
replication to ensure that snapshots are retained for the same period on both source
and destination MTrees.
l
User-created snapshots replicated in DD OS 5.4 will retain the source snapshot
retention period. Snapshots replicated in prior releases will retain the 1-year
retention period.
u
Supports collection, directory and MTree replication over IPv6 networks, allowing
customers to take advantage of the vast IPv6 address space.
l
Supports simultaneous replication over IPv6 and IPv4 networks.
u
Configurable replication lag alert threshold for each Data Domain system.
l
Default setting is 24 hours.
Inter-Release Replication
u
With Data Domain Operating System (DD OS) 5.4, the following inter-release
combinations are supported for Directory and MTree replication:
l
DD OS 5.1 to DD OS 5.4 and vice versa (not possible when using IPv6).
l
DD OS 5.2 to DD OS 5.4 and vice versa (not possible when using IPv6).
l
DD OS 5.3 to DD OS 5.4 and vice versa (possible with IPv6).
l
DD OS 5.4 to DD OS 5.4 (possible with IPv6).
u
Collection replication requires both the source and destination Data Domain systems
to be running DD OS 5.4
Enhancements for Archiving Use Cases on Data Domain Systems
u
Fast file creation rates for small (~100 KB) files over CIFS with a new case-insensitive
file name lookup and a new Directory Name Lookup Cache (DNLC) system cache.
l
Archive file ingest rates of up to ~30 files/sec per single MTree per single CIFS
connection.
l
Archive storage data migration rates of up to 1TB/day to a Data Domain system.
l
Allows for support of Symantec Enterprise Vault (EV) savesets and seamless
integration for direct archive on Data Domain systems.
l
Faster archive rates for EV use cases, such as mailbox archive, journal archive,
and PST migrations.
u
Various file system improvements for enhanced consolidation of backup and archive
data on a Data Domain system.
l
MTree replication support for DD Retention Lock Compliance-enabled MTrees.
l
Heuristics-based stream management for archive data to facilitate optimal
utilization of streams in presence of backup workload.
Software Features 9
l
Improved the cleaning (GC) process such that all archive data stored in addition to
the backup data on the same Data Domain system will result in a minimal
increase in the overall time taken by the cleaning operation.
u
CIFS improvements:
l
Support for maintaining file creation time.
l
Better characterization and offline analysis through improved and enhanced CIFS
operations listing in ASUPs (autosupport reports).
u
New archive applications and partners have been qualified and certified with this
release. Refer to the Data Domain Archive Product Compatibility Guide for the complete
list of archive partner/application added with this release.
Data Domain ArchiveStore Replaces Data Domain Nearline License
u
New software license called Data Domain ArchiveStore replaces the existing Data
Domain Nearline license for tracking traditional archive-related use cases (such as
file archive, email archive, content/ECM archive, or database archive) on all Data
Domain systems.
l
Selectable license option in DxP/CxP (no-cost license).
l
Data Domain ArchiveStore license can be deployed on all the current shipping and
new Data Domain systems irrespective of any other Data Domain software
licenses.
l
The new Data Domain ArchiveStore licenses replace existing Data Domain
Nearline (NL) and Data Domain Backup-Nearline (BNL) licenses. After upgrading to
DD OS 5.4, any NEARLINE (NL or BNL) licenses will be displayed as ARCHIVESTORE
licenses.
Data Domain Extended Retention Software Enhancements
u
Supports space reclamation on retention tier.
l
Enables space to be reused or reclaimed after the deletion of old backup data.
l
Space reclamation is a continuously running background process that can be
suspended, resumed, or stopped via the CLI or from within the Data Domain
System Manager GUI.
l
Space reclamation automatically suspends itself while higher-priority processes
like Data Movement to Retention Tier or filesys clean are running, and it
resumes after the higher-priority processes complete.
u
Supports NDMP-based backups via NDMP protocol to Data Domain systems with Data
Domain Extended Retention software option.
u
Supports expanded MTree Replication functionality to enable DR protection of long-
term retention data in retention tier ingested via NFS, CIFS, VTL and/or NDMP.
l
Mtree replication is now supported for MTrees with extended retention migration
policies.
File System Enhancements
u
Increased number of concurrently accessible MTrees; supports up to 32 concurrently
accessible (active) MTrees on selected high end platforms as indicated in this table:
RELEASE NOTES
Table 2 Accessible MTrees
Platforms Currently Accessible MTrees
DD OS 5.2 DD OS 5.3 DD OS 5.4
DD4200/DD4500/DD7200
a
32
DD990/DD890/DD880 14 32 32
All other platforms 14 14 14
a. These systems are not supported in DD OS 5.2 or 5.3.
u
No change in the 100 maximum number of MTrees that can be created.
u
Active MTrees now visible for easy reporting using new active MTree column added to
system show performance command.
CIFS File System Enhancements
u
Significant improvement in small file creation rate over CIFS.
u
Full support for file creation time stamp over CIFS.
u
Uses case-insensitive file name support in the Data Domain file system.
System Management Enhancements
u
Protocol enhancements:
l
Support for DD Boost over Fibre Channel.
l
Support for NetBackup Auto Image Replication (AIR).
l
Support for the emulated i2000 Tape Library Changer and LTO-4 drive types.
u
Expanded browser support:
l
Expanded to include Internet Explorer 9 on Windows 7 and Google Chrome on
Windows and Mac OS.
u
Security enhancements:
l
Use of Secure FTP (FTPS) or Secure Copy Protocol (SCP) for transporting system log
files and core files to EMC support. Also used for uploading certificates.
Note
This feature is for downloading system information (logs, autosupports, support
bundles) and uploading system upgrade files. These protocols cannot be used to
access backup data.
l
Improved certificate signing via SHA1 to support customer specific certificate
authorities (CAs).
u
Extended Retention enhancement:
l
Configure and monitor space reclamation on systems with DD Extended Retention
software option.
l
Configure and monitor MTree replication between systems with or without DD
Extended Retention software option.
u
Alert and logging enhancements:
l
New alerts for enhanced network supportability, including alerts for invalid
network card and duplicate IP addresses.
Software Features 11
l
Improved clarity in alert and log messages, including corrective actions where
appropriate.
l
Deprecation of alert messages that are no longer generated.
u
System configuration and support enhancements:
l
Expanded network performance statistics to display all configured ethernet ports.
l
Enhanced capabilities of support bundle to transport over HTTPS, with
modified syntax; see support on page 19 for more information.
u
SNMP enhancements:
l
Traps are consistently generated for all alerts, with relevant details included in
trap text.
l
Support for additional MIB objects including systemUser, systemLicense,
ddboostOptions, snmpTrapHosts and filesysStatusMessage to support extensible
management and application integration.
Enterprise Security Enhancements
u
Enables the use of external signed certificates.
l
Provides the ability to securely import or delete an externally created and signed
host certificate.
l
Provides the ability to import or delete a host public key after the Data Domain
generated Certificate Signing Request is signed by an external certificate authority
(CA).
l
Provides the ability to securely import or delete an externally created certificate
authority (CA) certificate.
l
Upgrades the hash function used in the algorithm for authentication of the
certificate from MD5 to the more secure SHA1.
l
Enables the use of Secure FTP (FTPS) or Secure Copy Protocol (SCP) for
downloading system log files and core files to a local PC, uploading release
update RPM files, and uploading certificates.
Note
This feature is for downloading system information (logs, autosupports, support
bundles) and uploading system upgrade files. These protocols cannot be used to
access backup data.
Oracle Optimized Deduplication
u
Introduces new functionality for Oracle 11g that allows the database administrator to
use RMAN multiplexing. When enabled, the following are in place:
l
Improves deduplication efficiency in Oracle 11g deployments if using Oracle
multiplexing.
l
The deduplication ratio returns to similar levels experienced without multiplexing.
Actual deduplication improvement will depend on the block size used. The
biggest improvement is achieved using the Oracle 8K or 16K block sizes;
deduplication ratio improvements will be smaller with larger block sizes.
Note
The Oracle 4K or 32K block sizes are not supported for RMAN multiplexing.
RELEASE NOTES
u
These benefits apply to the following backup scenarios:
l
Oracle RMAN backups of Oracle databases directly to a Data Domain system using
either CIFS or NFS protocols are supported.
l
DD Boost for Oracle RMAN 1.2.
l
Data Domain is dedicated to the Oracle workload only.
u
Implementation guidelines:
l
Multiplexing must be disabled for any Oracle client or backup application that is
not supported; set FILESPERSET=1 and MAXOPENFILES=1.
l
The first full backup created after you enable this feature can significantly
increase the amount of storage used inside the Data Domain system; ensure that
sufficient space is available.
l
As a general rule, ensure that the maximum storage used by old data is no more
than 30% of total space available. This should accommodate the first full backup
after enabling advanced Oracle deduplication. Be sure that the system is sized
appropriately for the desired ingest rate and retention periods.
l
Deduplication rates will return to optimal levels after the first full backup and with
every subsequent backup after application-optimized compression for Oracle is
enabled.
Note
These enhancements are more apparent with Oracle RMAN than with other backup
applications. Also, the throughput improvements become more apparent over time, not
necessarily immediately after upgrading.
DD Boost Enhancements
u
DD Boost over Fibre Channel (FC)
l
Supports DD Boost over Fibre Channel (FC) enabling disk-based simplicity in FC
environments.
FC is used as a transport, and once transport is established, everything else is
transparent to the application including features and constructs of DD Boost.
DD Boost features supported over FC include aggregation, failover without
dependency on client multi-pathing software, distributed segment processing,
and managed file replication over Ethernet.
l
Clients: For supported clients, see the EMC DD Boost Compatibility Guide at the
EMC Data Domain support portal.
l
Host HBAs: Emulex LPe 11002/4GB, Emulex LPe 1205/8GB,QLogic 2562/8GB,
QLogic 2462/4GB.
l
Fibre Channel Switches: Brocade 6505, Brocade 6510, Brocade 300, Brocade
5100, Brocade 5300 and Cisco 9100 Series Multi Layer Fabric switches.
l
DD Boost over FC provides simplified management over access groups.
l
DD Boost over FC allows co-existence with VTL infrastructure. See deployment
guides for new installations and transitions from VTL deployments.
u
Supports enhanced Symantec NetBackup optimized synthetics (virtual synthetics).
l
Full backup after 8-10 cycles of virtual fulls are no longer needed for Data Domain
systems with memory larger than 4GB, which include these models:
DD140, DD160, DD565, DD580, DD610, DD620, DD630, DD640, DD660, DD690,
DD670, DD860, DD880, DD890, and DD990.
l
No change to requirement for full backup after 8-10 cycles of virtual fulls for
systems with smaller than 4GB memory which include these models:
DD120, DD510, and DD530.
u
Supports backing up an application/media server to a remotely located Data Domain
system under the following application and network characteristics:
l
Applications: EMC NetWorker and Symantec NetBackup.
l
Network characteristics:
Network Speed: 100 Mb to 10 Gb Ethernet (full duplex).
Round Trip Time (RTT): Up to 5 ms.
Bandwidth: Unrestricted bandwidth for the above network speed.
Packet Loss: < 0.001% including packet fragmentation.
u
Supports Symantec NetBackup Auto Image Replication (AIR), which provides the
ability to automatically manage the replication of a deduplicated backup image from
one NetBackup master server domain to another.
l
Support for AIR results in faster time to DR for critical backup images, automatic
cataloging and significantly improved RTO between two different NetBackup
domains. It will also simplify connectivity as there is no more need for local media
server to connect to both sides; the communication with second site happens
remotely.
l
Supports a point-to-point replication configuration.
u
Supports Symantec NetBackup 7.5.0.4 Accelerator for file system workloads with low
change rates.
l
Supports virtual synthetic full backups on the Data Domain system.
Note
In versions of NetBackup prior to 7.5.0.4, jobs may fail with a message such as the
following:
11/07/2012 11:58:35 - Critical bptm (pid=9739)
A portion of data to be included from a previous backup
(backupid = ostqa-linux2_1351870224, offset = 661288960,
length = 36352) has incorrect checksum (calculated checksum
from backup image faf2aff1392269d36db7dbcc211f3d97b3f526ed,
expected checksum 2345ea1603b4cb4ae2c29e5f6a9353e7832faee6)
The workaround for this problem is to upgrade to NetBackup 7.5.0.4 or later.
u
Data Domain virtual synthetic backups are supported with EMC NetWorker 8.1 and
EMC Avamar 7.0.
u
All the new features of DD Boost over FC and most of the features of NBU AIR can be
managed using the DD System Manager GUI.
u
For supported configurations, see the EMC DD Boost Compatibility Guide at the EMC
Data Domain support portal.
Networking Enhancements
This version of DD OS includes the following enhanced networking features.
IPv6 Support for Replication
u
IPv6 support is added for directory replication, collection replication and MTree
replication. This allows users to take advantage of the vast address space available
with IPv6. Managed file replication over IPv6 networks is not supported in this
release.
RELEASE NOTES
u
IPv6 is not supported for backup protocols in this release.
u
IPv6 support can be configured using the CLI. Configuring IPv6 addresses in the DD
System Manager (formerly Enterprise Manager) GUI is not currently supported.
u
Both the source and destination system must be configured with IPv6.
u
A single Data Domain system can be configured with both IPv4 and IPv6, thereby
allowing some replication traffic to flow over IPv4 networks (if one of the sites does
not have IPv6 capabilities) and other replication traffic to flow over IPv6 networks.
New Operations to Enhance Network Supportability
u
An alert indicating the presence of an invalid network card is added in this release. If
an invalid network card is detected, an alert is sent; however, ongoing operations are
not suspended. This check is always enabled and cannot be disabled. Because the
use of an unsupported network card can result in unexpected errors, the alert
provides a recommendation to remove the invalid card.
u
The net show stats detailed command provides more complete information
than in previous releases.
u
The congestion monitor is now enabled by default. To adjust and configure the
congestion monitor, use the net congestion-check command.
VTL Enhancements
u
Expanded tape library emulations for open systems to support ADIC i2000 tape
library emulation.
u
Expanded tape drive emulations for open systems environments to support the
following:
l
HP LTO-3 tape drive emulation.
l
HP LTO-4 tape drive emulation.
l
IBM LTO-4 tape drive emulation.
u
Expanded tape drive emulation for IBM i environments using IBM LTO-4 tape drive
support emulation.
u
Ability to perform a complete IBM i installation from Data Domain VTL, eliminating the
need for the IBM Software Distribution Media DVD (also known as IBM i system
recovery IPL Type D from tape).
u
Ability to assign VTL LUN 0 from multiple target ports for greater deployment
flexibility.
u
Improved scalability by supporting 1024 initiators and 2048 access groups.
u
Enhanced capability to track tape location history.
Data Domain Encryption Enhancements
u
Supports local encryption key management for DD Encryption of data at rest.
l
Enables local key management with key rotation with the same key types and
states; up to 254 keys allowed.
l
Configured and managed through either the CLI or the DD System Manager GUI.
l
Supports a secure key import and export function via CLI using either SCP or SFTP
to enable customers to store their keys safely in an external location.
l
Included with DD Encryption license.
u
Supports the co-existence of multiple key management options for DD Encryption on
the same DD system enabling the customer flexible migration to and from the other
types of encryption key management.
l
Supports default local key management, basic static encryption key, and RSA
DPM external key manager.
l
If local key management is used and the user upgrades to a RSA DPM
environment at a later time, the local keys will not be visible to RSA DPM and
those keys created prior to the upgrade to DPM will have to be managed locally on
the Data Domain system.
Command Changes in Version 5.4
Refer to the EMC DD OS Command Reference Guide for details on how to use the DD OS 5.4
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.
New Command
scsitarget
The scsitarget command includes a full set of options for managing a SCSI target
subsystem configuration on a single-node Data Domain system and on systems licensed
for Extended Retention. The scsitarget command is not supported on Global
Deduplication Arrays (GDAs).
The SCSI target subsystem configuration comprises several SCSI target entities:
u
services (VTL and DD Boost)
u
transports (Fibre Channel)
u
endpoints (virtual ports that map to system addresses that are Fibre Channel
interfaces)
u
logical devices
u
host initiators
u
access groups
These are the options used with the scsitarget command:
u
device
u
disable
u
enable
u
endpoint
u
group
u
initiator
u
persistent-reservation
u
reset
u
service
RELEASE NOTES
u
show
u
status
u
trace
u
transport
See the EMC DD OS Command Reference Guide for more information about using the
scsitarget command and its associated options.
Command OptionsNew Arguments
adminaccess
adminaccess certificate generate cert-signing-request [key-
strength {1024bit | 2048bit | 4096bit}] [country country-code]
[state state] [city city] [org-name organization-name] [org-
unit organization-unit] [common-name common-name]
Purpose: Increase manageability for SUB CA certificates.
adminaccess ftp add host-list
adminaccess ftp del host-list
adminaccess ftp option reset [session-timeout]
adminaccess ftp option set session-timeout timeout-in-secs
adminaccess ftp option show
adminaccess ftps add host-list
adminaccess ftps del host-list
adminaccess ftps option reset [session-timeout]
adminaccess ftps option set session-timeout timeout-in-secs
adminaccess ftps option show
adminaccess http add host-list
adminaccess http del host-list
adminaccess ssh add host-list
adminaccess ssh del host-list
adminaccess telnet add host-list
adminaccess telnet delete host-list
Purpose: Provide increased granularity for administering protocols.
archive
archive space-reclamation resume
archive space-reclamation start
archive space-reclamation stop
archive space-reclamation suspend
Purpose: Manage the execution of long-running space-reclamation operations with
the DD Extended Retention software option.
archive space-reclamation status
archive space-reclamation status-detailed
Purpose: Monitor the status of the processes deleting obsolete archived data.
cifs
cifs reset stats
Purpose: Ability to reset CIFS statistics.
Command OptionsNew Arguments 17
ddboost
ddboost association create local-storage-unit {replicate-to |
replicate-from} remote-hostname remote-storage-unit
ddboost association destroy local-storage-unit {replicate-to |
replicate-from} remote-hostname remote-storage-unit
ddboost association show [local-storage-unit]
ddboost event show [local-storage-unit]
Purpose: Command options to support NetBackup AIR functionality.
ddboost fc dfc-server-name reset
ddboost fc dfc-server-name set server-name
ddboost fc dfc-server-name show
ddboost fc dump start logfile-id logfile-id[formatted] [snaplen
bytes] [logfile-count-limit count] [logfile-size-limit bytes]
[virtual-connection virtual-connection-id] [client-hostname
hostname] [initiator initiator] [target-endpoint endpoint]
[destination-tcp-port tcp-port]
ddboost fc dump status
ddboost fc dump stop
ddboost fc group add group-name initiator initiator-spec
ddboost fc group add group-name device-set [count count]
[endpoint {all | none | endpoint-list}]
ddboost fc group create group-name
ddboost fc group del group-name initiator initiator-spec
ddboost fc group del group-name device device-set {count count
| all }
ddboost fc group destroy group-name
ddboost fc group modify group-name device-set [count count]
[endpoint {all | none | endpoint-list}]
ddboost fc group rename src-group-name dst-group-name
ddboost fc group show detailed group-spec [initiator initiator-
spec]
ddboost fc show detailed-stats
ddboost fc group show list [group-spec] [initiator initiator-
spec]
ddboost fc show stats [endpoint endpoint-spec] [initiator
initiator-spec] [interval interval] [count count]
ddboost fc status
ddboost fc trace disable [component {all | component-list}]
ddboost fc trace enable [component {all | component-list}]
[level {all | high | medium | low}]
ddboost fc trace show [component {all | component-list}]
ddboost fc trace show [component {all | component-list}]
ddboost option set fc {enabled | disabled}
Purpose: Support DDBoost services via Fibre Channel Transport.
enclosure
enclosure show chassis [enclosure]
enclosure show cpus [enclosure]
enclosure show io-cards [enclosure]
enclosure show memory [enclosure]
enclosure show nvram [enclosure]
Purpose: Display enhanced hardware information. With the exception of
enclosure show nvram, output includes VPD (Vital Product Data) when
commands are run on newer models.
RELEASE NOTES
filesys
filesys encryption embedded-key-manager keys create
filesys encryption embedded-key-manager reset key-rotation-
policy
filesys encryption embedded-key-manager set key-rotation-policy
{months | none}
filesys encryption embedded-key-manager show
filesys encryption keys export
Purpose: Support embedded Data Domain Key Manager.
filesys option set app-optimized-compression {oracle1 | none}
Purpose: Handle Oracle markers for increased compression.
replication
replication modify destination ipversion {ipv4 | ipv6}
Purpose: Support IPv6.
replication option set default-sync-alert-threshold value
Purpose: Support setting default threshold (in hours) for replication lag alert.
support
support bundle create {files-only file-list | traces-only}
[and-upload [transport {http | https}]]
support bundle create default [with-files file-list] [and-
upload [transport {http | https}]]
support bundle list
support bundle upload bundle-name [transport {http | https}]
Purpose: Create and upload support bundles securely.
system
system passphrase change
system passphrase set
system retention-lock compliance configure
system retention-lock compliance enable
system retention-lock compliance status
Purpose: Stricter adherence to security requirements for passphrases and Retention
Lock Compliance.
system upgrade status
Purpose: To view the current status of a DD OS upgrade.
system show managing-system
Purpose: View the Data Domain Management Center (DDMC) that is managing this
Data Domain system.
vtl
vtl rename src-vtl dst-vtl
Purpose: Rename an existing Virtual Tape Library.
vtl show stats [port {port-list | all}] [interval secs] [count
count]
Purpose: Replacement command option for vtl port show.
Command OptionsNew Arguments 19
vtl tape history delete
vtl tape history disable
vtl tape history enable
vtl tape history show barcode [pool pool] [start-time
MMDDhhmm[[CC]YY]] [end-time MMDDhhmm[[CC]YY]]
vtl tape history status
Purpose: Displays tape location history to support VTL debugging when required.
Command OptionsNew Arguments in DD OS 5.4.1.0
archive data-movement
archive data-movement schedule set {never | days days time time
[every2wks]} [no-clean]
Adds the no-clean option. When you set the schedule for data movement, the file
system is normally cleaned after data movement is completed. To prevent this
normal cleaning, specify the no-clean option.
filesys archive
filesys archive unit unseal [archive-unit-name]
Unseals the last sealed unit and only works when there is no target unit. This
command can only be run when the file system is offline. Requires admin-role
privileges.
Command OptionsModified Arguments
adminaccess
adminaccess certificate delete {imported-host | imported-ca |
support-bundle-ca | subject subject-name | fingerprint
fingerprint}
adminaccess certificate show [detailed] [host | imported-host |
ca | imported-ca | support-bundle-ca | cert-signing-request]
Details: Argument added for supporting bundled CA certificates: support-bundle-ca.
adminaccess certificate import {host | ca} [file file-name]
Details: Argument for password removed. Argument for file name added.
adminaccess disable {http | https | ftp | ftps | telnet | ssh |
scp | all}
adminaccess enable {http | https | ftp | ftps | telnet | ssh |
scp | all}
Details: Arguments added for SCP and FTPS.
alerts
alerts notify-list add group-name {[class class-list [severity
severity]] [emails email-addr-list] }
alerts notify-list del group-name {[class class-list] [emails
email-addr-list]}
alerts notify-list show [group group-name | email email-addr]
Details: Previously optional arguments for sending targeted ASUP, alerts and emails
from the Data Domain Systems to EMC servers are now required. (Note braces.)
RELEASE NOTES
archive
archive data-movement schedule set {never | days days time time
[every 2wks]}
Details: Argument added to support bi-weekly data movement to the retention tier
with the DD Extended Retention software option [every 2wks].
archive report generate file-location filename
Details: Argument added to specify the location of the report.
autosupport
autosupport set subject-tag tag
autosupport reset subject-tag
autosupport show subject-tag
Details: Specifying the subject-tag enables users to bypass filtering software that
may inadvertently block email delivery of autosupport reports and alerts. Subject
tags cannot exceed 64 characters.
autosupport reset {alert-summary | asup-detailed}
autosupport test {alert-summary | asup-detailed | email email-
addr}
Details: Argument support-notified removed. See support chapter in the EMC DD
OS Command Reference Guide for more information.
ddboost
ddboost option reset {distributed-segment-processing | virtual-
synthetics | fc}
ddboost option show [distributed-segment-processing | virtual-
synthetics | fc]
Details: Argument added for Fibre Channel (fc).
enclosure
enclosure show all [enclosure]
enclosure show powersupply [enclosure]
enclosure show controllers [enclosure]
Details: Display enclosure-specific information.
filesys
filesys clean set schedule {never | daily time | day(s) time |
biweekly day time | monthly day(s) time}
Details: Arguments rearranged and new arguments added to provide granular file
system cleaning schedule. Argument added to support a biweekly file system
cleaning schedule.
filesys option reset {local-compression-type | low-bw-optim |
marker-type | report-replica-as-writable | global-compression-
type | staging-reserve | staging-clean | staging-delete-suspend
| compute-segfeatures | app-optimized-compression}
filesys option show {local-compression-type | low-bw-optim |
marker-type | report-replica-as-writable | global-compression-
type | staging-reserve | staging-clean | staging-delete-suspend
| compute-segfeatures | app-optimized-compression}
Details: Arguments added for compute-segfeatures and app-optimized-compression
(that is, Oracle compression).
Command OptionsModified Arguments 21
ipmi
ipmi user add user
ipmi user change user
ipmi remote console ipmi-target ipaddr | hostname user user
ipmi remote power {on | off | cycle | status} ipmi-target
ipaddr | hostname user user
Details: Argument for password removed.
ndmpd
ndmpd user add user name
ndmpd user modify user name
Details: Argument for password removed.
net
net aggregate modify virtual-ifname [mode {roundrobin |
balanced hash {xor-L2 | xor-L3L4 | xor-L2L3} | lacp hash {xor-
L2 | xor-L3L4 |xor-L2L3} [rate {fast | slow}]}] [up {time |
default}] [down {time | default}]
Details: Argument for physical interface name removed.
replication
replication add source source destination destination [low-bw-
optim {enabled | disabled}] [encryption {enabled | disabled}]
[propagate-retention-lock {enabled | disabled}] [ipversion
{ipv4 | ipv6}]
Details: Arguments added for IPv4 and IPv6.
replication option reset {bandwidth | delay | listen-port |
default-sync-alert-threshold}
Details: Argument added for setting default threshold for replication lag alert.
replication sync [and-verify] [destination]
Details: Argument added for verifying collection replication synchronization (not
directory or MTree replication synchronization).
route
route del [ipversion {ipv4 | ipv6}] route spec
Details: Arguments added to indicate IP version and route specification.
snmp
snmp show config [version {v2c | v3}]
snmp show trap-hosts [version {v2c | v3}]
Details: SNMP supports versions v2C and v3.
vtl
vtl debug disable [component {all | user | default | component-
list}]
vtl debug enable [component {all | user | default | component-
list}] [level {high | medium | low}] [timeout {never | timeout
mins}]
vtl debug show [component {all | user | default | component-
list}]
Details: Argument for kernel removed.
RELEASE NOTES
Command OptionsModified Output
adminaccess
adminaccess certificate delete {imported-host | imported-ca |
support-bundle-ca | subject subject-name | fingerprint
fingerprint}
Details: Output warns user when deleting a certificate.
adminaccess disable ssh
Details: Output includes warning that disabling ssh also results in disabling scp.
adminaccess show
Details: Output displays information on all protocols.
archive
archive data-movement status
Details: Phase 0 is added to output to indicate data movement is initializing.
Summary information is now included in new Status-After Completion section
following Phase 5.
archive data-movement watch
Details: Users can now view overall data-movement status during each phase. For
example, if the user runs the command during Phase 3 of the data-movement
process, output for Phases 1, 2, and 3 is shown.
archive show config
Details: Output includes Space Reclamation status.
autosupport
autosupport reset all
autosupport show all
Details: Output now includes subject tags set by user.
cifs
cifs show stats
cifs show detailed-stats
Details: Includes the number of active and total CIFS connections, file opens, and
other CIFS operations. Provides information to identify performance bottlenecks.
ddboost
ddboost show connections
Details: Changed heading Interfaces to Interface. Values for Status field are
enabled, disabled, or blank if not in a group. For Fibre Channel, output displays n/a
for Group Name, blank for Status, and DDBOOST_FC for Interface.
ddboost show histogram
ddboost show stats
Details: Output includes details on NetBackup AIR functionality.
Command OptionsModified Output 23
enclosure
enclosure show all
Details: Output for system enclosures now shows VPD (Vital Product Data)
information on the system controller components in addition to the information
displayed prior to DD OS 5.3. (The system controller component VPD information
follows the information displayed prior to DD OS 5.3.)
Note
VPD information applies only to DD7200, DD4500, DD4200, and DD2500 systems.
enclosure show memory
Details: Output in Speed (MHz) column now includes current and maximum speeds.
Size column now includes Mibs in heading. Changes apply when command is run
on the latest Data Domain systems. Changes do not apply to systems DD990 and
earlier.
enclosure show powersupply
Details: Power modules in Description column are now identified alphabetically
instead of numerically. Changes apply when command is run on the latest Data
Domain systems. Output includes power supply VPD (Vital Product Data)
information (when available) in addition to power supply status. Changes do not
apply to systems DD990 and earlier.
filesys
filesys disable
Details: Output provides warning before disabling the file system.
filesys encryption embedded-key-manager show
filesys encryption embedded-key-manager set key-rotation-policy
none
Details: Enhanced output such as type of key in use, last rotation time, etc.
filesys encryption show
Details: Output includes additional detail.
filesys option show
Details: Output displays compute-segfeatures option.
filesys restart
Details: Output provides warning before disabling the file system.
ntp
ntp enable
Details: Output displays warning message for time synchronization when joining
domain.
replication
replication add source source destination destination [low-bw-
optim {enabled | disabled}] [encryption {enabled | disabled}]
[propagate-retention-lock {enabled | disabled}] [ipversion
{ipv4 | ipv6}]
Details: Output includes a warning that the destination must be an Extended
Retention system, when an MTree replication context is configured on an Extended
Retention system.
RELEASE NOTES
system
system show all
system show performance
system show serialno detailed
Details: Output now includes service tag information. Service tag information is set
during the manufacturing process and remains unchanged during a headswap or
head upgrade. Service tag information always remains with the head, not with the
shelf. Changes apply when command is run on the latest Data Domain systems.
Changes do not apply to systems DD990 and earlier.
system show stats
Details: Output includes new indicators, Container Verification (I) and Data
Verification (V). Output also displays active mtree count. Added new columns in, out,
getattr, setattr, create, readdir, read and write to cifs view. Added cifs in and cifs out
to default/iostat view. Removed nfs load, wait in, wait out (only) from default/iostat
view and cifs view.
system show ports
Details: References to VTL replaced by FC-Tgt, indicating use by VTL and DD Boost.
system upgrade status
Details: Output displays additional information on upgrade status.
vtl
vtl drive del vtl drive drive number [count num-to-del]
Details: Output displays number of drives deleted.
Command OptionsModified Output in DD OS 5.4.1.0
ddboost file-replication
ddboost file-replication show detailed history
ddboost file-replication show detailed file-history
ddboost file-replication show stats
Adds a new column (Post-synthetic-optim) to the output of these commands,
which provide statistics for replication that is optimized by the virtual synthetics
feature.
system retention-lock
system retention-lock compliance status
Adds a new line of output: Accumulated clock variance shows the
accumulated system clock skew.
Command OptionsRemoved
adminaccess add {ftp | telnet | ssh | http | https} host-list
adminaccess delete {ftp | telnet | ssh | http | https} host-
list
cluster add
cluster create
Details: Users can no longer add or create a Global Deduplication Array. Remaining
cluster commands are unchanged in this version.
Command OptionsModified Output in DD OS 5.4.1.0 25
Command OptionsDeprecated
cifs option reset ntfs-acls
cifs option set ntfs-acls enabled
cifs option set ntfs-acls disabled
disk rescan [enclosure-id.disk-id]
Changes in DD OS Version 5.4 Management Information Base
(MIB)
Table 3 Added MIB Objects
MIB Object Type OID
bMCFailure Node 1.3.6.1.4.1.19746.2.0.7000
ddboostOptions Node 1.3.6.1.4.1.19746.1.12.9
ddboostOptionsIndex Column 1.3.6.1.4.1.19746.1.12.9.1.1.1
ddboostOptionsName Column 1.3.6.1.4.1.19746.1.12.9.1.1.2
ddboostOptionsStatus Column 1.3.6.1.4.1.19746.1.12.9.1.1.3
ddms Node 1.3.6.1.4.1.19746.1.19
driveMixType Node 1.3.6.1.4.1.19746.2.0.7002
fileSystemStatusMessage Scalar 1.3.6.1.4.1.19746.1.3.1.4
managedSystem Node 1.3.6.1.4.1.19746.1.19.1
managedSystemCDSyncTime Column 1.3.6.1.4.1.19746.1.19.1.1.1.8
managedSystemDDOSVersion Column 1.3.6.1.4.1.19746.1.19.1.1.1.6
managedSystemHDSyncTime Column 1.3.6.1.4.1.19746.1.19.1.1.1.7
managedSystemHostname Column 1.3.6.1.4.1.19746.1.19.1.1.1.2
managedSystemIndex Column 1.3.6.1.4.1.19746.1.19.1.1.1.1
managedSystemSerial Column 1.3.6.1.4.1.19746.1.19.1.1.1.3
managedSystemState Column 1.3.6.1.4.1.19746.1.19.1.1.1.4
managedSystemStatus Column 1.3.6.1.4.1.19746.1.19.1.1.1.5
snmpTrapHost Node 1.3.6.1.4.1.19746.1.18.3
snmpTrapHostsIndex Column 1.3.6.1.4.1.19746.1.18.3.1.1.1
snmpTrapHostsName Column 1.3.6.1.4.1.19746.1.18.3.1.1.2
snmpTrapHostsVersion Column 1.3.6.1.4.1.19746.1.18.3.1.1.3
systemCapacityLicense Node 1.3.6.1.4.1.19746.1.13.4.2
systemCapacityLicenseCapacity Column 1.3.6.1.4.1.19746.1.13.4.2.1.1.5
systemCapacityLicenseFeature Column 1.3.6.1.4.1.19746.1.13.4.2.1.1.3
systemCapacityLicenseIndex Column 1.3.6.1.4.1.19746.1.13.4.2.1.1.1
RELEASE NOTES
Table 3 Added MIB Objects (continued)
MIB Object Type OID
systemCapacityLicenseKey Column 1.3.6.1.4.1.19746.1.13.4.2.1.1.2
systemCapacityLicenseModel Column 1.3.6.1.4.1.19746.1.13.4.2.1.1.4
systemLicense Node 1.3.6.1.4.1.19746.1.13.4
systemLicenseFeature Column 1.3.6.1.4.1.19746.1.13.4.1.1.3
systemLicenseIndex Column 1.3.6.1.4.1.19746.1.13.4.1.1.1
systemLicenseKey Column 1.3.6.1.4.1.19746.1.13.4.1.1.2
systemUser Node 1.3.6.1.4.1.19746.1.13.5
systemUserIndex Column 1.3.6.1.4.1.19746.1.13.5.1.1.1
systemUserName Column 1.3.6.1.4.1.19746.1.13.5.1.1.2
systemUserRole Column 1.3.6.1.4.1.19746.1.13.5.1.1.4
systemUserStatus Column 1.3.6.1.4.1.19746.1.13.5.1.1.5
systemUserUID Column 1.3.6.1.4.1.19746.1.13.5.1.1.3
tcpZeroWindowAlert Node 1.3.6.1.4.1.19746.2.0.6101
unsupportedDriveModel Node 1.3.6.1.4.1.19746.2.0.7001
Table 4 Modified MIB Objects
MIB Object Type OID Comments
artMigrationScheduleSchedule Column 1.3.6.1.4.1.19746.1.14.2.1.1.2 Description field changed
artMigrationScheduleStatus Column 1.3.6.1.4.1.19746.1.14.2.1.1.3 Data type changed from
DDMibInteger32TC to
DDMibStatusTC
fileSystemOptionsName Column 1.3.6.1.4.1.19746.1.3.4.1.1.2 Description field changed
interfaceConnectivityDown Node 1.3.6.1.4.1.19746.2.0.6009 Added ifDescr information
interfaceConnectivityIntermittent Node 1.3.6.1.4.1.19746.2.0.6010 Added ifDescr information
interfaceConnectivityUpAndRunning Node 1.3.6.1.4.1.19746.2.0.6020 Added ifDescr information
interfaceMisconfiguration Node 1.3.6.1.4.1.19746.2.0.6011 Added ifDescr information
Note
No MIB objects were deprecated or deleted in this version of DD OS.
Changes in DD OS Version 5.4 Management Information Base (MIB) 27
Changes in DD OS Version 5.4 System Events
Table 5 Added System Events
Event ID Event Name
EVT-DIMM-00003 DIMM failure
EVT-ENCRYPTION-00005 Encryption key export failed
EVT-ENVIRONMENT-00024 Fan Fault
EVT-ENVIRONMENT-00025 Power Supply Input fault
EVT-ENVIRONMENT-00026 Power Supply failure
EVT-ENVIRONMENT-00027 Power Supply Absent
EVT-ENVIRONMENT-00028 Unsupported AC voltage
EVT-ENVIRONMENT-00029 Component fault
EVT-ENVIRONMENT-00030 Component inserted
EVT-ENVIRONMENT-00031 Component failure
EVT-ENVIRONMENT-00032 System Controller failure
EVT-ENVIRONMENT-00033 Chassis failure
EVT-ENVIRONMENT-00034 Forced Controller Shutdown
EVT-ENVIRONMENT-00035 System reset
EVT-ENVIRONMENT-00036 Enclosure High Temp
EVT-ENVIRONMENT-00037 Unsupported system type
EVT-ENVIRONMENT-00039 BMC Failure
EVT-LICENSE-00001 License Expiring
EVT-LICENSE-00002 License Expired
EVT-NETM-00005 DuplicateAddressDetection
EVT-NETM-00006 InvalidNICSlot
EVT-NETM-00007 UnsupportedNIC
EVT-NETM-00008 Tcp Zero Window Alert
EVT-NVRAM-00201 NvramHWAlert
EVT-NVRAM-00202 NvramBattAlert
EVT-NVRAM-00203 NvramEnvAlert
EVT-NVRAM-00204 NvramCondAlert
EVT-NVRAM-00205 NvramEventHWAlert
EVT-REPL-00008 MissingCreplUnits
EVT-SAS-03803 SASHBAFailure
EVT-SAS-03804 SASHBAErrors
RELEASE NOTES
Table 5 Added System Events (continued)
Event ID Event Name
EVT-SAS-03805 UnsupportedSASDevice
EVT-SCSTGTD-00001 SCSITGTFCLinkOffline
EVT-SCSTGTD-00002 SCSITGTFCLinkOscillations
EVT-SCSTGTD-00003 SCSITGTFCLinkOnline
EVT-SCSTGTD-00004 SCSITGTInvalidRegistry
EVT-SECURITY-00004 ExpiredHostCertificate
EVT-SREC-00001 SpaceReclRestartFailed
EVT-SREC-00002 SpaceReclMissingUnit
EVT-SREC-00003 SpaceReclUnitReclaimed
EVT-SREC-00004 SpaceReclError
EVT-STORAGE-00016 DiskEndOfLife
EVT-STORAGE-00017 MultipleDiskReadErrors
EVT-STORAGE-00018 Unsupported Drive Model
EVT-STORAGE-00019 Drive Mix Type
EVT-VTL-00004 TapeReposition
EVT-UPGRADE-00002 UpgradeFailure
EVT-UPGRADE-00003 UpgradeCompleted
Table 6 Modified System Events
Event ID Event Name Changed Fields
EVT-DIMM-00003 DIMM Failure Additional Information
EVT-ENCRYPTION-00003 Encryption key table full Description & Action
EVT-ENVIRONMENT-00003 Legacy Power Supply Warning Class
EVT-ENVIRONMENT-00004 Legacy Fan Warning Class
EVT-ENVIRONMENT-00005 Power Supply Warning Class
EVT-ENVIRONMENT-00006 Fan Warning Class
EVT-ENVIRONMENT-00007 Voltage Warning Class
EVT-ENVIRONMENT-00008 Power Warning Class
EVT-ENVIRONMENT-00009 Correct ECC Warning Class
EVT-ENVIRONMENT-00010 Non Thresh Warning Class
EVT-ENVIRONMENT-00011 Processor Warning Class
EVT-ENVIRONMENT-00013 Incorrect ECC Warning Class
Changes in DD OS Version 5.4 System Events 29
Table 6 Modified System Events (continued)
Event ID Event Name Changed Fields
EVT-ENVIRONMENT-00021 Abnormal shutdown Class
EVT-ENVIRONMENT-00035 System Reset Severity
EVT-ENVIRONMENT-00037 Unsupported System Type Message
EVT-FMIG-00001 File Migration Error Message
EVT-NVRAM-00009 NvramBatteryLowChargeAlert Message, Class, Description & Action
EVT-SPACE-00003 SpaceOver80Percent Description & Action
EVT-SPACE-00004 SpaceOver90Percent Description & Action
EVT-STORAGE-00002 DiskFailure Class
EVT-STORAGE-00004 DiskTemperatureShutdown SNMP trap-oid
Table 7 Deprecated System Events
Event ID Event Name
EVT-FILESYS-00003 DDGC Failed in shutdown
EVT-FILESYS-00005 DDFS Not Cleanly Shutdown
EVT-FILESYS-00006 DDGC Failed1
EVT-NVRAM-00004 NvramBoardTempAlert
EVT-NVRAM-00005 NvramBoardVoltageAlert
EVT-NVRAM-00006 NvramBatteryTempAlert
EVT-NVRAM-00007 NvramBatteryVoltageAlert
EVT-NVRAM-00008 NvramBatteryChargeAlert
EVT-NVRAM-00010 NvramBatteryGaugeAlert
EVT-NVRAM-00011 NvramBatteryDetectAlert
EVT-NVRAM-00012 NvramBatteryChargeDisableAlert
EVT-NVRAM-00013 NvramCorrectMemAlert
EVT-NVRAM-00014 NvramUncorrectMemAlert
EVT-NVRAM-00015 NvramPCIeAlert
EVT-NVRAM-00016 NvramCPUAlert
EVT-NVRAM-00017 NvramBatteryPowerDisableAlert
EVT-NVRAM-00018 NvramReadOnlyAlert
EVT-NVRAM-00019 NvramReadOnlyAlert
RELEASE NOTES
Table 7 Deprecated System Events (continued)
Event ID Event Name
EVT-NVRAM-00020 NvramWrongModelAlert
EVT-NVRAM-00021 NvramWrongModelAlert
EVT-NVRAM-00022 NvramLinkSpeedAlert
EVT-NVRAM-00023 NvramLinkWidthAlert
EVT-NVRAM-00024 NvramGetInfoAlert
EVT-NVRAM-00025 NvramTargetLinkSpeedAlert
EVT-NVRAM-00026 NvramWrongCountAlert
EVT-NVRAM-00027 NvramMixAlert
EVT-VTL-00001 VTLFCLinkOffline
EVT-VTL-00002 VTLFCLinkOscillations
EVT-VTL-00003 VTLFCLinkOnline
Note
The deprecated NVRAM and VTL events listed in the Deprecated System Events table
have been replaced by new events.
Fixed Issues
This release of DD OS, 5.4.3.0-436446, includes a number of fixed issues. The release
also includes fixed issues from prior releases in the DD OS 5.4 feature family.
Fixed in Version 5.4.3.0-436446
This topic lists important changes and fixes made to this version of DD OS.
Table 8 DD OS 5.4.3.0DD Boost Issues: Fixed
Bug # Description
107995 Fixed an issue where a packet that was malformed in transit caused a file system
panic during decompression.
108386 Fixed the issue in which Backup Exec 2012 duplicate jobs could fail for backups
that were sent directly from Backup Exec 2012 to the Data Domain system.
110464 Fixed the issue in which an inventory of the Data Domain device by Backup Exec
could fail due to an incorrect error code.
111191 Fixed the issue in which the number of ifgroup clients could not be increased above
a maximum of 256.
115522 Fixed the issue in which some zero-length files that were used as event semaphores
were deleted prematurely, which could cause some files to be omitted from a
backup catalog.
Fixed Issues 31
Table 9 DD OS 5.4.3.0File System Issues: Fixed
Bug # Description
78040 Fixed the issue in which a Data Domain system reported incorrect MTree and
compression statistics due to double accounting for raw bytes on references and
segments.
92919 Fixed the issue in which consecutive markers were merged in an incoming data
stream, and when the merged markers exceeded a certain byte length, then a zero-
size segment reference resulted, causing the file system to crash. This issue only
occurred when Oracle application optimization is enabled.
94286 Fixed the issue in which Data Domain system performance could degrade because
some opaque entries created for snapshots on systems with MTree replication were
not deleted as expected on the replica, and the accumulation these stale opaque
entries affected system performance.
104408 Fixed the issue in which opening a spanning file could result in a file system panic
due to a health monitor timeout on a Data Domain system with the Extended
Retention software option enabled.
104919 Fixed the issue in which users could not authenticate with CIFS following an
upgrade to DD OS 5.4.0.7.
106315 Fixed the issue in which backups could fail due to resource contention with space
reclamation processes.
107665 Fixed the issue in which a DD2500 system was not correctly tuned, which caused
resulted in memory issues and a file system panic.
108380 Fixed the issue in which a Data Domain system, after recently running garbage
collection, experienced timeouts for several NFS or DD Boost remote procedure
calls at an increasing rate. The RPC timeouts followed a situation in which the file
verification process verified files in the ASUP without capturing the correct
timestamp. The problem usually disappeared after a system panic and restart.
108749 Fixed the issue in which users belonging to an Active Directory Domain whose
NETBIOS name is not unique in the Active Directory forest could not authenticate.
109657 Fixed the issue in which a CIFS group name or a CIFS group member's username
containing the $ character followed by two non-hex characters could cause
operations involving either of those names, including logins, to fail.
110535 Fixed the issue in which a Data Domain system with the Extended Retention
software option enabled could panic during archive data movement if the write
stream count for ingest exceeded the maximum supported by the system.
113664 Fixed the issue in which a Data Domain system could panic with NetBackup AIR
because of anomalies introduced on the wire into requests to close a file.
Table 10 DD OS 5.4.3.0General Issues: Fixed
Bug # Description
107386 Fixed the issue in which an improperly functioning mail server could cause SNMP
traps for alerts not to be sent to the Data Domain system. This fix ensures that
SNMP traps are independent of mail server functionality.
RELEASE NOTES
Table 10 DD OS 5.4.3.0General Issues: Fixed (continued)
Bug # Description
108678 Fixed the issue in which a Data Domain system running DD OS version 5.2.2.4 could
become unresponsive to RPC services queries, requiring a hard reboot to restore
functionality.
Table 11 DD OS 5.4.3.0Networking Issues: Fixed
Bug # Description
110344 Fixed the issue in which two NFS mounts performed at identical times for same
export could result, very rarely, in one of the mounts failing with an authentication
failed error.
Table 12 DD OS 5.4.3.0Platform Issues: Fixed
Bug # Description
106547 Fixed the issue in which a DD2500 system could generate false high-temperature
alerts.
106897 Fixed the issue in which a Data Domain system's boot partitions could be cleared
when the system reboots after a system controller disk failure.
107734 Fixed the issue in which a disk drive's serial number check initiated by a host bus
adapter's reset could time out, causing the HBA reset to incur deadlock. The
probability of this issue occurring was low.
109239 Fixed the issue in which a Data Domain system could become unusable after the
root file system became completely full because an oversized file was created in /
tmp.
109640 Fixed the issue in which an AC power cycle of a DD160 appliance could cause the
system's IPMI LAN settings to disappear.
111843 Fixed the issue in which a cache could be flushed unnecessarily. Prior to this fix,
the system could generate partial containers because of this issue, which could
consume extra space due to internal fragmentation of data. Also, the increased I/O
caused by these conditions could lead to timeouts.
Table 13 DD OS 5.4.3.0Replication Issues: Fixed
Bug # Description
84122 Fixed the issue in which the file system could fail because of a panic that occurred
when filecopy tasks were not properly aborted.
Table 14 DD OS 5.4.3.0VTL Issues: Fixed
Bug # Description
109633 Fixed the issue with duplicate LUNs (0-7) on HP-UX 11.11 and 11.23 client
platforms when VSA is enabled. This issue could create virtual tape drive
Fixed in Version 5.4.3.0-436446 33
Bug # Description
accessibility issues within a Data Domain VTL environment and could also result in
unexpected changes to data located on the associated virtual tape cartridges
(VTCs).
Bug # Description
111191 Fixed the issue in which the number of ifgroup clients could not be increased above
a maximum of 256.
111898 Fixed the issue in which customers whose media servers reported their domain
name as none. As a result of this fix, their media servers now report either the
fully qualified domain name or simply the short name.
Bug # Description
111843 Fixed the issue in which a cache could be flushed unnecessarily. Prior to this fix,
the system could generate partial containers because of this issue, which could
consume extra space due to internal fragmentation of data. Also, the increased I/O
caused by these conditions could lead to timeouts.
Bug # Description
111077 Fixed the issue in which, when incorrect remote procedure call arguments were
received by the replica system in a replication pair, a success message and not an
error message was sent to the source system.
Bug # Description
108749 Fixed the issue in which users belonging to an Active Directory Domain whose
NETBIOS name is not unique in the Active Directory forest could not authenticate.
RELEASE NOTES
Bug # Description
108678 Fixed the issue in which a Data Domain system running DD OS version 5.2.2.4 could
become unresponsive to RPC services queries, requiring a hard reboot to restore
functionality.
Bug # Description
105326 Fixed the issue in which a Data Domain system could panic due to an RPC timeout
that occurred due to an excess of files awaiting processing.
106249 Fixed the issue in which NetBackup Automatic Image Replication jobs failed due to
an image metadata (_IM) file error when the fragment file(s) (_F1, _F2, ...) took
longer than 10 minutes to complete. The Knowledge Base article 95090 contains
further details.
107015 Fixed the issue in which DDBoost over Fibre Channel failed to start when invalid
endpoints were present on the Data Domain system.
Bug # Description
81531 Fixed the issue in which a Data Domain system with NFS_LOG_IMMEDIATE_SIZE
set to 64k and using small writes was not able to recover from any previous Data
Domain file system panic, with the added result that backup jobs affected by the
panic needed to be re-done.
86411 Fixed the issue in which the Data Domain file system was using only 1GB of
contiguous memory heap, which leads to memory fragmentation inside the file
system in the long term because the libc allocator did not scale optimally with
non-contagious memory. This fix reduces memory fragmentation in the file system's
virtual memory space and helps the file system run longer.
98162 Fixed the issue in which a race condition between garbage collection enumeration
and segment processing could lead to a Data Domain file system panic.
100254 Fixed the issue in which the Data Domain file system could panic when overwriting
backup files with densely populated markers.
102307 Fixed the issue in which a DD Boost virtual synthetics backup by means of an
Avamar high-generation backup or a NetBackup Accelerator rescan backup could
fail during the ingest phase with error 5048 (indicating a limit on t0 segment
references in a t1 segment) or sometimes, incorrectly, with error 5044 (indicating
that the file system is read-only).
102547 Fixed the issue in which the Data Domain file system crashed due to a problem
encountered with MTree replication of backups optimized by the virtual synthetics
feature between Data Domain systems with different DD OS families.
Table 21 DD OS 5.4.2.0File System Issues: Fixed (continued)
Bug # Description
102830 Fixed the issue in which the filesys destroy and-zero operation produced
operation timeout errors and provided no progress indicators when executed on a
Data Domain system with the Extended Retention software option enabled.
102988 Fixed the issue in which the number of managed file replication jobs could exceed
the maximum allowed filecopy streams. Because of this error condition, data-
movement processes could fail to start and could handle the error improperly. The
improper error handling could cause a memory leak that in turn caused a file
system panic during a file system shutdown.
104641 Fixed the issue in which the filesys verify resume command may not in
some cases resume its scrubbing function.
104672 Fixed the issue in which the file system of a Data Domain system that had been
upgraded to DD OS version 5.4.0.7 could panic continuously.
104676 Fixed the issue in which certain types of write workloads could exhibit degraded
performance.
104821 Fixed the issue in which the Data Domain file system could panic due to a race
condition between two threads that negatively affected a backup job.
105111 Fixed the issue in which a mismatch in the number of segments read during delta
replication from a source Data Domain system running DD OS version 5.3 or newer
to a destination Data Domain system running a version of DD OS older than 5.3
destabilized the file system on the source system and caused repeated file system
panics.
105121 Fixed the issue in which users could unintentionally create anomalies by enabling
Extended Retention on a Data Domain system using the System Manager GUI even
if encryption had previously been used on the system. The Extended Retention
software option cannot be enabled on a Data Domain system if the system has
used encryption previously; all encrypted data needs to be cleared of encryption,
and all encryption settings need to be removed before the Extended Retention
software option can be enabled.
105503 Fixed the issue in which the Data Domain file system dumped core because of an
error in the system registry.
107213 Fixed the issue in which a Data Domain system user with user or backup-
operator roles was unable to run the replication sync command.
108927 Fixed the issue in which the DD OS file system could panic when using MTree
replication from a Data Domain source system running DD OS 5.4.1.x or 5.4.0.x to a
destination system running DD OS 5.1.x where no MTree quota was set on the
source system.
Bug # Description
103731 Fixed the issue in which the Replication Summary Report in the System Manager
GUI displayed a misleading label for the Y-axis in the summary chart of the report.
The Y-axis is now correctly labeled as Network Bytes (MiB) instead of Network
In&Out (Mbps).
RELEASE NOTES
Bug # Description
105933 Fixed the issue in which users could not add a Data Domain system in the
Enterprise Manager if the registry keys were missing or in some other anomalous
state.
Bug # Description
93458 Fixed the issue in which the DD OS filesystem could panic because the Data
Domain system failed to attach a shared memory segment. This could occur for a
variety of reasons. As a result of this fix, an error message is logged, and there is no
filesystem panic.
95983 Fixed the issue in which Data Domain file system could panic if a colon character (:)
is present in any field of an NFS rmtab entry.
100269 Fixed the issue in which the output of the ddboost file-replication show
stats command and the contents of the ddboostFileReplicationStatsTable object
(.1.3.6.1.4.1.19746.1.12.5.1 ) were not consistent.
100352 Fixed the issue in which an unresolved symbolic link led to an asynchronous RPC
timeout, which in turn caused a Data Domain file system panic.
102419 Fixed the issue in which DD Boost looked up and opened streams that NFS had just
closed, which in turn caused NFS to close the streams again. This could happen
repeatedly and could cause performance stalls.
105014 Fixed the issue in which an NFS remote procedure call could become delayed and
ultimately cause a file system panic. The delay could occur if a large number of
streams needs to be flushed at the same time the RPC is being processed.
105408 Fixed the issue in which the Data Domain file system panicked when an
autosupport job ran the filesys show detailed-stats command.
105620 Fixed the issue in which a soft lock could cause a system panic after upgrading a
Data Domain system to DD OS 5.4.0.8.
Bug # Description
77396 Fixed the issue in which a Data Domain system controller upgrade could not be
performed on a system where the expansion shelf was at a level of DD OS
preceding than the head. For example, if the head was at DD OS 5.4 but the
expansion shelf was at DD OS 5.2, the controller could not be upgraded. In the
current feature family (DD OS 5.5), the upgrade can proceed.
88664 Implemented a process to reduce IO latency and to avoid file system slowdowns by
placing an upper limit on the number of retries executed for IO that completed with
an error.
95405 Fixed the issue in which Data Domain systems became unusable if the log directory
(/ddr/var/log/debug/cifs) was accidentally deleted. The log directory is
automatically recreated on the next system boot.
Table 24 DD OS 5.4.2.0Platform Issues: Fixed (continued)
Bug # Description
96692 Fixed the issue which caused a segmentation fault in SMS and a general protection
fault in SNMP.
98970 Fixed the issue in which a DIMM error message did not include the correct DIMM
location.
100849 Fixed the issue in which some DD640, DD670, DD860, and DD890 platforms report
spurious environmental alerts (such as voltage threshold, chassis temperature
threshold, or fan speed) in the storage controller chassis. This platform firmware
issue was first addressed with a DD OS change in releases 5.1.4.0, 5.2.3.0, 5.3.1.0
and later major releases. However, that previous change did not completely
address the problem.
103139 Fixed the issue in which the process that generates autosupport reports could enter
an infinite loop, which could overtake most of the CPU resources, necessitating a
system reboot to restore normal operations. This issue occurred only with PCIe
hardware problems.
103153 Fixed the issue in which historical database pruning failed because of insufficient
space on the participation in which to perform some of the pruning operations.
104609 Fixed the issue in which garbage collection enumeration, an initial phase of system
cleaning, could become suspended, causing significant performance degradation.
This issue only affected Data Domain systems that used virtual synthetics.
104869 Fixed the issue in which a Data Domain system unexpectedly rebooted after disk
reconstruction.
105341 Fixed the issue in which a DD120, DD510, or DD530 model system could issue a
spurious core dump capability alert when the system's core dump capability was
not impaired.
107119 Fixed the issue in which the System Management Service could run out of memory,
possibly causing a system crash, followed by a system restart.
Bug # Description
97005 Fixed the issue in which system cleaning (garbage collection) could incur a
significant performance reduction if a replication context is broken during the
cleaning process. The fix resolves an situation that the broken replication context
left open, causing the system cleaning slowdown.
100752 Fixed the issue in which a delayed file deletion in a replication pair led to an
asynchronous RPC timeout, which in turn caused a Data Domain file system panic.
102465 Fixed the issue in which space reclamation could stall on a Data Domain system
with collection replication configured if the system crashed during garbage
collection.
103650 Fixed the issue in which a Data Domain system could become unresponsive
because too many active replication contexts overloaded System Management
Services with status requests that by default required locks.
RELEASE NOTES
Table 25 DD OS 5.4.2.0Replication Issues: Fixed (continued)
Bug # Description
104007 Fixed the issue in which MTree replication and synchronization would occur without
incident, and snapshots that should have been deleted could remain, even though
the Data Domain system considered the snapshots to be expired.
104071 Fixed the issue in which the Data Domain file system could panic when a
NetBackup Auto-Image Replication (AIR) operation tried to create a file on an MTree
replication destination.
105045 Fixed the issue in which directory replication failed between two Data Domain
systems because of a mismatch between encryption settings on the two systems.
106815 Fixed the issue in which a Data Domain system using managed file replication with
replication throttling could hang, panic, or exhibit slowed performance.
107664 Fixed the issue affecting MTree Replication where the source Data Domain system
has the Extended Retention software option enabled. A panic could occur on the
destination Data Domain system because the format of a file on the source system
has undergone a change due to the file's migration to the Retention tier.
Bug # Description
103414 Fixed the issue in which is was not possible to delete a VTL pool from the Enterprise
Manager GUI, while it was possible from the DD OS command line interface.
105109 Fixed the issue in which users could not use the DD System Manager (GUI) to select
and configure an endpoint for Fibre Channel access group devices if the endpoint
had previously been renamed.
105927 Fixed the issue in which a VTL upgrade (as part of a DD OS upgrade) failed because
non-existent Fibre Channel ports existed in the VTL configuration. A port could
become non-existent if its configuration changed, such as by replacing a Fibre
Channel interface with an Ethernet interface. The upgrade process now checks for
non-existent VTL ports and disallows the upgrade if non-existent ports are detected.
Bug # Description
102307 Fixed the issue in which a DD Boost virtual synthetics backup by means of an
Avamar high-generation backup or a NetBackup Accelerator rescan backup could
fail during the ingest phase with error 5048 (indicating a limit on t0 segment
references in a t1 segment) or sometimes, incorrectly, with error 5044 (indicating
that the file system is read-only).
Bug # Description
105014 Fixed the issue in which an NFS remote procedure call could become delayed and
ultimately cause a file system panic. The delay could occur if a large number of
streams need to be flushed at the same time the RPC is being processed.
Bug # Description
104609 Fixed the issue in which garbage collection enumeration, an initial phase of system
cleaning, could become suspended, causing significant performance degradation.
This issue only affected Data Domain systems that used virtual synthetics.
Bug # Description
93670 Fixed the issue in which the ddboost status, ddboost show user-name
and ddboost show connections commands could fail with an error
containing the RPC error=12 message if the number of DD Boost clients
exceeded 100. This error did not adversely impact any backup, restore, or
replication operations.
95869 Fixed the issue that affected adding and managing DD Boost clients. As a result of
this fix, all clients will report fully qualified domain names (FQDN) when reporting
the host name to the Data Domain system. Customers who configured individual
client names for ddboost access or ddboost ifgroup will need to modify
their configuration to include the FQDN of the clients. However, this enhancement
allows easier configuration if *.domainname satisfies the needed configuration.
Be aware that clients are expected to be configured for domain name support,
based on client platform type. Windows clients are expected to be configured with a
domain name in the registry. To perform this configuration, click Start > Run, open
regedit, and look for this entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
\Parameters\Domain
99178 Fixed the issue in which a Data Domain source system could panic if a NetBackup
Auto Image Replication (AIR) job was cancelled.
101027 Fixed the issue in which users could not add DD Boost clients to an ifgroup using
wildcard characters. As a result of this fix, the clients administered IP is used to
select the ifgroup group when a client name match cannot be found. This requires
RELEASE NOTES
Table 30 DD OS 5.4.1.0DD Boost Issues: Fixed (continued)
Bug # Description
the administered IP to be configured in an ifgroup, and that the client named * is
not configured for any group.
102160 Fixed the issue in which a user could not restore from a DD Boost-created backup or
found that applications were unable to use a restored file without clear symptoms
or reasons for the failure. Although there have been no reported field instances of
this issue, systems exceeding the maximum number of device stream count limit
during a DD Boost writes + Managed File Replication could create this condition. If
the Data Domain system did not experience stream exhaustion, there is no impact.
Bug # Description
74236 Provided new support to unseal a sealed archive unit. The capability is delivered in
a new CLI: filesys archive unit unseal [archive-unit-name]. The command
unseals the last sealed unit and only works when there is no target unit. This
command can only be run when the file system is offline.
81838 Fixed the issue in which garbage collection processes could not completely remove
dead data in situations in which "dead" data is uniformly distributed across
containers.
83601 Fixed the issue in which system timeouts related to heartbeat events were not
properly logged, which made such timeouts difficult to analyze or to debug.
85214 Fixed the issue in which a transient missing segment during collection replication
could cause a core dump on the destination Data Domain system.
86621 Fixed the issue in which the filesys verify status CLI operation could fail
when encountering the scrub IDLE state
88035 Fixed the issue that affected the act of monitoring Data Domain's global
compression frequently (more than once per hour) in systems experiencing a high
level of system activity. This issue, if encountered, manifested itself with the Data
Domain file system reporting a timeout error. Users monitoring Data Domain's
global compression using either Data Domain's filesys show compression
CLI command or BRM 1.0 were more susceptible to this error.
89163 Fixed the issue in which certain VTL environments could experience delayed tape
mounts because of delays updating the registry copy on the first shelf of disk
drives. The increased delay is the result of disabling disk caching. When the time
required to update the shelf copies rose to certain levels, VTL would restart. By
performing shelf updates asynchronously, these delays are reduced and restarts
are eliminated.
89359 Fixed the issue in which the filesys show compression command did not list the
files in subfolders.
89729 Fixed the issue in which the Data Domain file system could panic when low-bw-
optim is enabled during replication or DD Boost, or both. The panic is due to a race
condition occurring within the sketch cache when the container is in a sealed state.
Bug # Description
90825 Fixed the issue in which a Data Domain source system configured as a single node
could panic when replicating a file with a hole greater than 1TB in size to a
destination system that has Extended Retention software configured.
90919 Fixed the issue in which the DD OS file system could panic in rare corner cases if
the number of MTrees created is large and the usage patterns lead to many cache
evictions. The panic was due to a return code that is now properly handled.
91348 Fixed the issue in which the Data Domain file system could not be re-enabled after
a power outage that negatively impacted collection partition metadata.
92337 Fixed the issue in which many DD OS file system operations could fail if the user
specified the atime of their file (explicitly or implicitly) to be less than (current time
MINUS 12 hours). In this case an error was be returned from the file system for the
affected file operation. With this fix the user can use any atime (explicitly or
implicitly) to be less than current time, the file operation will succeed, and no error
is returned.
92390 Fixed the issue in which a resource client memory leak could occur in the DD OS file
system. This leak could occur when a file is opened and then a file sync takes place
before the file is used in its expected workflow. This issue could arise when Avamar
was performing a VM backup.
92679 Fixed the issue in which a user with the admin role was permitted to change the
sysadmin user password without having to supply the sysadmin user
password.
93023 Fixed the issue in which backups and restorations with DD Boost could not be
performed on a DD160 system unless the backup write streams and backup read
streams parameters had been set manually in the system registry.
93297 Fixed the issue in which the Data Domain file system could panic due to a transient
missing segment during garbage collection's enumeration phase.
93344 Fixed the issue in which a deadlock could occur while logging messages on
retention-locked MTrees, resulting in timeout and panic.
94008 Fixed the issue in which an incorrect filehandle-to-path conversion could result in
panic during rmdir (remove directory) operations.
94046 Fixed the issue in which system performance could degrade when copying files into
a Retention Lock (governance or compliance) MTree, regardless of the locking
status.
94089 Fixed the issue in which the DD OS file system could fail to be disabled normally,
which could have side-effects, such as causing a Data Domain system upgrade
process to fail.
94330 Fixed the issue in which the DD OS file system fingerprint database could fail in
certain uncommon situations. Typically the file system created a container with too
many identical fingerprints because the total number of concurrent backup streams
exceeded the limit for the Data Domain system, and many concurrent writes with
identical segments occurred at the Data Domain system at or about the same time.
In this situation, the number of identical fingerprints could exceed a threshold that
caused the fingerprint database to fail.
RELEASE NOTES
Bug # Description
94864 Fixed the issue in which replication contexts could not be created on a destination
Data Domain system because the file system on the destination system was
temporarily unavailable.
95422 Introduced forward-looking changes that decrease the amount of time required to
upgrade a Data Domain system from a previous DD OS release.
95821 Fixed the issue in which a transient missing segment over a DD Boost stream on a
Data Domain system with the Extended Retention software option could cause the
DD OS file system to panic.
96774 Fixed the issue in which the process of replicating virtual synthetic files from a
single-node Data Domain system (source) to a Data Domain system with the
Extended Retention software option (destination) could cause the Data Domain file
system on the destination to crash.
97188 Fixed the issue in which a Data Domain system running workloads continually at or
near maximum stream count limits could experience DD OS file system panics due
to limits on stream resources.
97304 Fixed the issue in which some Data Domain systems with particular RAM and
NVRAM configurations lacked the correct configuration parameters for backup read
and write streams. These parameters have been corrected. These are the affected
configurations:
l
DD160, 4GB RAM, 1GB NVRAM
l
l
l
98411 Fixed the issue in which certain threads were not exiting normally in the ssick and
cmck tools, which preventing these tools from shutting down.
99136 Fixed the issue in which the copy phase of a data-movement fast-seeding process
unnecessarily scanned an entire active unit.
102099 Fixed the issue in which a process called container recipe cooking for collection
replication for collections created in pre-5.3 versions of DD OS experienced higher
failure rates due to a format change for containers introduced in version 5.3.
Containers are now written to the destination Data Domain system in the format of
the DD OS version in which they were originally created, which eliminates the
elevated failure rate experienced by some users.
102151 Fixed an issue occurring with virtual synthetics in which a relatively small extent
from the end of the base file that is greater than 2 GB in length is included to offset
0 of the new file.
102202 Fixed the issue in which certain operations could detect as present a file that did
not exist.
103342 Fixed the issue in which data ingestion during replication with the low bandwidth
optimization feature enabled could encounter a panic due to a race condition,
which could recur.
Bug # Description
103988 Fixed the issue in which a panic could occur after Data Domain system that had
been configured as a collection replication destination was restarted as a
standalone system and encountered a missing segment problem.
Bug # Description
81283 Fixed the issue in which NFS latency statistics returned by the system show
performance operation incorrectly showed zero values.
92527 Fixed the issue in which the GUI for the Data Domain System Manager displayed the
former product name.
96805 Fixed the issue in which NFS mounts via UDP (User Datagram Protocol) could be
prevented because the UDP remote procedure call service was incorrectly closed.
97145 Updated the Initial Configuration Wizard to remove references to the Data Domain
GDA (Global Deduplication Array) system.
97220 Fixed the issue in which the Data Domain Enterprise Manager GUI hid the
compression ratio label displayed in the File System box on the Status >
Summary screen when the compression ratio was reported by the Data Domain
system to be zero.
98306 Fixed the issue in which contention during memory allocation could cause a file
system panic because memory was not pre-allocated for certain components.
98467 Fixed the issue in which a formatting change to the Data Domain system alerts
notification list caused the list to became unusable after upgrading from DD OS
5.1.4.0 to 5.3.x or later.
102209 Fixed the issue in which the DD OS file system could dump core with segmentation
violations due to invalid references to file system internal data structures.
Bug # Description
82640 Fixed the issue in which, if an interface was down before the system was rebooted,
there would be no VLANs associated with the interface when the system came back
up, even if the interface had any associated VLANs before the reboot.
87048 Fixed the issue in which slow performance on directory reads in CIFS or NFS could
result in degraded performance of small file creation in CIFS, which ultimately
affected NetWorker, SQL, and other CIFS backup applications that use small files
(transaction logs).
91496 Fixed the issue in which the Data Domain file system could panic due to slow
memory allocation on a system under a heavy processing load.
92194 Fixed the issue in which the VLANs on top of virtual interfaces could not be viewed
with the ddboost show connections command and therefore were not
available for use with ifgroups.
RELEASE NOTES
Table 33 DD OS 5.4.1.0Networking Issues: Fixed (continued)
Bug # Description
93458 Eliminated the DD OS file system panic that could affect a Data Domain system
when it failed to attach a shared memory segment. If the Data Domain system
experiences a shared memory segment failure, an error message is now logged,
and there is no file system panic.
95047 Fixed the issue in which the SNMP daemon failed because more enclosures were
attached to the Data Domain system than the value of MAX_ENCLOSURES defined
in SNMP, causing an array overflow.
96192 Fixed the issue in which a DNS retry timeout could cause a panic.
96310 Fixed the issue in which registry removal occurred concurrently with the process of
interface port renaming during booting, and a second system reboot after the
network registries were removed caused all the registry entries to be lost. The fix
prevents this particular combination of events from occurring.
98219 Updated rpc.mountd to a version that repairs a security vulnerability.
98632 Fixed the issue in which a Data Domain system configured with a failover interface
and a VLAN interface on top of the failover interface could run out of memory,
leading to a system crash.
99120 Fixed the issue in which system performance could slow because memory allocated
for certain modules caused delays in allocating memory for other modules.
99324 Fixed the issue in which mount points for all existing hosts could go stale if a new
NFS client is added using the Enterprise Manager GUI. (The issue did not occur
when adding the NFS client using the CLI.)
Bug # Description
85026 Fixed an issue in the SAS host bus adapter firmware that could send excessive
device reset messages to external shelf drives, which in turn could cause one or
more shelf drives to become absent and cause a DD OS file system failure.
85035 Fixed the issue in which a Data Domain system could hang and reboot after
continuous link reset commands were sent to a specified phy that is
connected to a disk.
85876 Fixed the issue that could generate false cabling and path alerts as well as cause
the enclosure show topology operation to fail.
88346 Fixed the issue in which an alert for a failed DIMM in slot 1B or slot 2A may call out
the incorrect DIMM slot. This issue could affect DD140, DD160, DD610, DD620, or
DD630 models.
90999 Fixed the issue in which EMC Data Domain software licenses could be invalidated
following an upgrade from DD OS 5.2.1.0 to 5.2.2.0 due to WWNN and WWPN
changes.
91692 Fixed the issue in which it was possible to run a second DD OS upgrade on a Data
Domain system before the first upgrade had completed.
Bug # Description
92996 Fixed an issue in the shelf firmware that could automatically disable the SAS
connection between the SAS expander and the disk drives when the host bus
adapter sends excessive device reset messages to the drives, which in turn could
cause one or more shelf drives to become absent and cause a DD OS file system
failure.
94164 Fixed the issue in which the system show stats iostat command could
occasionally fail to display hyphen (-) characters in the output to indicate that the
system was busy and unable to retrieve recent data.
95006 Fixed the issue in which the Enterprise Manager GUI incorrectly reported that a
DIMM's temperature was orange (indicating a system warning) when a temperature
for the DIMM was actually unavailable.
95519 Fixed the issue in which a disk drive removal occurring immediately after the disk
drive was added could occasionally cause a Data Domain system to hang due to a
race condition.
96182 Fixed the issue in which a DD620 appliance could undergo an unexpected system
reboot caused when a Host Bus Adapter driver could hang during a port reset,
triggering a timeout that led to the reboot.
96273 Fixed the issue in which the root directory of a Data Domain system could become
filled when copying an RPM file to /ddvar/releases due to a missing symbolic link.
98825 Fixed the issue in which a DD OS upgrade performed via the Enterprise Manager GUI
could time out, killing the upgrade process, because of more work for required for
certain upgrades.
99861 Fixed an issue that caused DD OS file system heart monitor to panic because a file
system request was in an endless retry loop. As a result of this fix, after a few
unsuccessful retries the disk reporting errors are removed, and the file system
request is serviced, and then the file system request is retired as a degraded
operation.
100275 Fixed the issue in which a multiple-step upgrade from DD OS 4.8.x or earlier to DD
OS 5.4.0.4 or 5.4.0.5 could fail and cause data problems if some particular
conditions were present, such as if the Data Domain system has ES20 expansion
shelves. It could result that the RAID could not be reassembled, the DD OS file
system could not boot, and multiple drives could become unknown or classified as
foreign or spare. For more information, consult KB article 94621 at the EMC Data
Domain Support Portal.
101333 Fixed the issue in which a kernel panic could occur if a disk drive fails to clean up
any pending commands after the device drive is reset.
RELEASE NOTES
Bug # Description
84157 Fixed the issue in which network connectivity interruptions during replication in a
cascaded topology could caused the replication process to panic.
84517 Fixed the issue in which an Error state could incorrectly be reported after creating
a replication context when the more appropriate state was Uninitialized. This
could occur when there was data in the source Data Domain system, and the
replication pair was created with an initial state Error and an initial state
description Uninitialized.. Now the state matches the state description.
87359 Fixed the issue in which the Data Domain system could panic if certain
combinations of file system operations, such as a race conditions caused by
renaming and closing a file, are replayed on the server side.
90300 Fixed the issue in which a Data Domain destination system could panic on
detecting a checksum mismatch when opening a file during replication.
94309 Fixed the issue in which the deletion of symbolic links on a source Data Domain
system with an MTree replication context could cause a panic on the destination
Data Domain system with the MTree replication context.
97804 Fixed the issue in which the Data Domain system continued to allocate streams to
replication filecopy operations after the maximum stream count had been reached.
100680 Fixed the issue that could occur after data in pools were converted to data in
MTrees. Data could possibly be lost after the conversion if the converted MTree
replication does not work. At the least, data could become unavailable on the
destination system while the MTree replication is being initialized.
100892 Fixed the issue in which directory, MTree, or managed file replication from a Data
Domain system to a system with both Extended Retention software and encryption
enabled over the wire could cause a system panic at the destination due to a DIA
(Data Invulnerability Architecture) assertion. Because of this assertion, metadata
associated with the data being replicated over the encrypted wire is missing. The
metadata (segment features) allows the deduplicated data ingested on the
source system to be replicated to and read by a system with Extended Retention
software. Without this metadata, the replicated data could become inconsistent.
The fix allows segment features to be replicated to a Data Domain system with
Extended Retention software when encryption over the wire is enabled.
Bug # Description
61122 Fixed the issue in which a virtual tape cartridge could be adversely affected
because of timeouts in read and write. A deferred error related to the timeout now
prevents those adverse effects.
90436 Fixed the issue in which IBM i and other systems would not work with tape libraries
because they detected a conflict when a tape appeared in a CAP (cartridge access
port) location.
90826 Fixed the issue in which VTL could improperly discard the last set of data buffered
for a particular cartridge if the Data Domain file system somehow became unable to
ingest the data, such as when the file system is full, timing out, or shutting down.
Table 36 DD OS 5.4.1.0VTL Issues: Fixed (continued)
Bug # Description
91012 Fixed the issue with SCSI 3 Persistent Reservation handling, which caused Tivoli
Storage Manager to continuously encounter reservation conflicts after Register and
Ignore service actions so that Tivoli Storage Manager was not able to access VTL
devices.
95674 Fixed the issue in which an upgrade from DD OS 5.1 or 5.2 to DD OS 5.3 or later
failed if any VTL initiator aliases were set to any of the Data Domain system's
WWPNs (World Wide Port Names).
96794 Added support for Compatible Reservation Handling (CRH) in DD OS 5.4.1.0.
102942 Fixed the issue in which memory anomalies could cause a panic when more than
512 ports were logged into the target system.
Bug # Description
102160 Fixed the issue in which a user could not restore from a DD Boost-created backup or
found that applications were unable to use a restored file without clear symptoms
or reasons for the failure. Although there have been no reported field instances of
this issue, systems exceeding the maximum number of device stream count limit
during a DD Boost writes + Managed File Replication could create this condition. If
the Data Domain system did not experience stream exhaustion, there is no impact.
Bug # Description
92390 Fixed the issue in which a resource client memory leak could occur in the DD OS file
system. This leak could occur when a file is opened and then a file sync takes place
before the file is used in its expected workflow. This issue could arise when Avamar
was performing a VM backup.
102151 Fixed an issue occurring with virtual synthetics in which a relatively small extent
from the end of the base file that is greater than 2 GB in length is included to offset
0 of the new file.
RELEASE NOTES
Bug # Description
95674 Fixed the issue in which an upgrade from DD OS 5.1 or 5.2 to DD OS 5.3 or later
failed if any VTL initiator aliases were set to any of the Data Domain system's
WWPNs (World Wide Port Names).
Bug # Description
98632 Fixed the issue in which a Data Domain system configured with a failover interface
and a VLAN interface on top of the failover interface could run out of memory,
leading to a system crash.
Bug # Description
100275 Fixed the issue in which a multiple-step upgrade from DD OS 4.8.x or earlier to DD
OS 5.4.0.4 or 5.4.0.5 could fail and cause data problems if some particular
conditions were present, such as if the Data Domain system has ES20 expansion
shelves. It could result that the RAID could not be reassembled, the DD OS file
system could not boot, and multiple drives could become unknown or classified as
foreign or spare. For more information, consult KB article 94621 at the EMC Data
Domain Support Portal.
Bug # Description
99178 Fixed the issue in which a Data Domain source system could panic if a NetBackup
Auto Image Replication (AIR) job was cancelled.
Bug # Description
96774 Fixed the issue in which the process of replicating virtual synthetic files from a
single-node Data Domain system (source) to a Data Domain system with the
Extended Retention software option (destination) could cause the Data Domain file
system on the destination to crash.
Bug # Description
98411 Fixed the issue in which certain threads were not exiting normally in the ssick and
cmck tools, which preventing these tools from shutting down.
Bug # Description
93458 Fixed the issue in which the DD OS file system could panic because the Data
Domain system failed to attach a shared memory segment. This could occur for a
variety of reasons. As a result of this fix, an error message is logged, and there is no
file system panic.
Bug # Description
98825 Fixed the issue in which a DD OS upgrade performed via the Enterprise Manager GUI
could time out, killing the upgrade process, because of more work for required for
certain upgrades.
Bug # Description
87359 Fixed the issue in which the Data Domain system could panic if certain
combinations of file system operations, such as a race conditions caused by
renaming and closing a file, are replayed on the server side.
90300 Fixed the issue in which a Data Domain destination system could panic on
detecting a checksum mismatch when opening a file during replication.
Bug # Description
90826 Fixed the issue in which VTL could improperly discard the last set of data buffered
for a particular cartridge if the Data Domain file system somehow became unable to
ingest the data, such as when the file system is full, timing out, or shutting down.
RELEASE NOTES
Bug # Description
87860 Fixed the issue in which the DD OS file system could dump core due to incorrect
status applied to pages being removed, which caused a root page checksum
mismatch .
89163 Fixed the issue in which certain VTL environments could experience delayed tape
mounts because of delays updating the registry copy on the first shelf of disk
drives. The increased delay is the result of disabling disk caching. When the time
required to update the shelf copies rose to certain levels, VTL would restart. By
performing shelf updates asynchronously, these delays are reduced and restarts
are eliminated.
90825 Fixed the issue in which a Data Domain source system configured as a single node
could panic when replicating a file with a hole greater than 1TB in size to a
destination system that has Extended Retention software configured.
90919 Fixed the issue in which the DD OS file system could panic in rare corner cases if
the number of MTrees created is large and the usage patterns lead to many cache
evictions. The panic was due to a return code that is now properly handled.
91348 Fixed the issue in which the Data Domain file system could not be re-enabled after
a power outage that negatively impacted collection partition metadata.
93023 Fixed the issue in which some incorrect system settings for backup read streams
and backup write streams could prevent a DD160 system from performing backups
through DD Boost.
93297 Fixed the issue in which the Data Domain file system could panic due to a transient
missing segment during garbage collection's enumeration phase.
93344 Fixed the issue in which a deadlock could occur while logging messages on
retention-locked MTrees, resulting in timeout and panic.
94008 Fixed the issue in which an incorrect filehandle-to-path conversion could result in
panic during rmdir (remove directory) operations.
94046 Fixed the issue in which system performance could degrade when copying files into
a Retention Lock (governance or compliance) MTree, regardless of the locking
status.
95422 Introduced changes that decrease the amount of time required to upgrade a Data
Domain system from a previous DD OS release to 5.4.
Bug # Description
92527 Fixed the issue in which the GUI for the Data Domain System Manager displayed the
former product name.
Bug # Description
85035 Fixed the issue in which a Data Domain system could hang and reboot after
continuous link reset commands were sent to a specified phy that is
connected to a disk.
92194 Fixed the issue in which the VLANs on top of virtual interfaces could not be viewed
with the ddboost show connections and therefore were not available for use
with ifgroups.
95047 Fixed the issue in which the SNMP daemon failed because more enclosures were
attached to the Data Domain system than the value of MAX_ENCLOSURES defined
in SNMP, causing an array overflow.
Bug # Description
Bug # Description
84157 Fixed the issue in which network connectivity interruptions during replication in a
cascaded topology could caused the replication process to panic.
94309 Fixed the issue in which the deletion of symbolic links on a source Data Domain
system with an MTree replication context could cause a panic on the destination
Data Domain system with the MTree replication context.
Bug # Description
94089 Fixed the issue in which the DD OS file system could fail to be disabled normally,
which could have side-effects, such as causing a Data Domain system upgrade
process to fail.
94864 Fixed the issue in which replication contexts could not be created on a destination
Data Domain system because the file system on the destination system was
temporarily unavailable.
RELEASE NOTES
Bug # Description
67323 Fixed the issue in which users needed to run the filesys restart command in
order to kill a file replication process that was in progress. Users can now use the
ddboost disable command for this purpose.
74879 Fixed the issue in which write stream counts for DD Boost did not appear correctly
in the output of the system show performance CLI operation.
75783 Fixed the issue in which an asynchronous remote procedure call took too long
because the file name resolution function timed out.
77667 Fixed the issue in which the DD Boost plug-in would crash when used to restore
data from a retention tier that was added after another retention tier was deleted
but the file system was not restarted.
81486 Fixed the issue in which the ddboost file-replication show active
operation incorrectly displayed not only Auto Image Replication (AIR) jobs that had
completed but also standard filecopy jobs that failed even after they had been
stopped.
87303 Fixed the issue in which a Data Domain system could panic if a file delete occurs as
part of a catalog cleanup while the file is being closed.
Bug # Description
51044 Fixed the issue in which an IBM iSeries system's initial program load (IPL) from a
VTL tape failed. The symptom displayed to the user may be that the IPL process
hangs with SRC: C500E200 (LIC system hardware initialization). With this DD OS
version, IBM i IPL type D recovery from tape is supported, eliminating the step in the
process that requires the use of DVD. If necessary, contact EMC Data Domain
Customer Support to activate the IBM i D-IPL from tape feature in DD OS 5.2.2.x.
63538 Fixed the issue in which L1 sharing was enabled by default, which could result in
problematic locality.
68784 Implemented various enhancements that increase the performance of fast-seeding
and data ingestion operations.
69275 Fixed the issue in which the file system in a Data Domain system with virtual
synthetics could fail and time out.
72998 Fixed the issue of lock contention that could arise when blockmap lookups were
performed over sparse ranges in the container set. Container set iteration could
take a long time if there was sparseness in the logical container IDs. This in turn
could slow certain operations like garbage collection, index merge, or collection
replication. This change removes lock contention and manages sparse ranges
within container set iteration code, thus improving performance.
Bug # Description
74814 Fixed the issue in which incorrect data on a drive could result in unexpected mount
and umount actions that prevented the Data Domain file system from starting.
75578 Fixed the issue in which the DD OS file system could panic on an opt-dup
replication source system during garbage collection.
75674 Fixed the issue in which the archive report generate file-location operation
aborted with a broken pipe error.
75758 Improved the routines governing write operations so that many small and out-of-
order disk writes performed in a Data Domain system with Extended Retention or in
a Global Deduplication Array no longer risk causing a system failure.
76136 Fixed the issue in which an incorrect data alignment could cause a memory leak.
76489 Fixed the issue in which some users were not able to authenticate to CIFS shares on
a Data Domain system via hostname.
76506 Fixed the issue in which the garbage collection process could negatively affect data
ingestion due to resource contention.
76581 Fixed the issue in which an excessive number of logins from monitoring
applications, such as the EMC DataProtection Advisor software, could cause the
wtmp file of login records to grow, fill up /root, and lead to system downtime.
76586 Fixed the issue in which the DD OS file system could time out due to a contentious
lock situation by redesigning the lock to make it fair.
76710 Fixed the issue in which a Data Domain system inappropriately truncated the
NetBIOS name of a domain.
76859 Fixed the issue in which lock contention could lead to a timeout for NFS remote
procedure calls.
76925 Fixed the issue in which a System Management Service (SMS) memory leak could
lead to an SMS core dump.
77028 Fixed the issue in which an error could occur when performing a very large seek
operation larger than the maximum file size.
77677 Fixed the issue in which the DD OS file system could panic and not come up due to
running out of space in the retention tier during space reclamation on a retention
unit.
77688 Fixed the issue in which the Data Domain file system could panic due to a race
condition that occurred when ejecting an MTree.
78109 Fixed the issue in which a Data Domain file system could panic when a new shelf is
added to the system with very little (around 2%) free space. In general, it is
advisable to add storage without filling the Data Domain system completely.
78322 Clarified the error message regarding the user's inability to destroy certain file
systems. It now reads: The filesystem cannot be destroyed
because the following MTrees have retention locks
enabled.
78764 Fixed the issue in which the Data Domain file system restarted in response to a
volume does not exist error.
RELEASE NOTES
Bug # Description
78795 Fixed the issue where users could set the CIFS admin access groups dd admin
group1/2 and dd user group1/2 to a specific domain user. These admin access
groups can now be set to a specific domain group only, and domain users who are
members of the set domain group will have appropriate admin access.
79477 Fixed the issue in which garbage collection performance could be compromised
because it used only half of the available CPUs in the system.
79585 Fixed the issue in which multiple file operations on the same file by different
threads on a Data Domain system running under high processing loads could cause
a system deadlock leading to a panic.
79720 Fixed the issue in which the space statistics of each new retention unit were not
initialized before using the retention unit, which could cause unexpected space
statistics to appear in the System Manager.
79802 Fixed the issue in which VTL timeouts could occur because of heavy IO workload on
the ext3 file system, which competed for resources with software logging functions.
This fix optimizes the logging logic to avoid this resource contention.
79807 Fixed the issue in which an index rebuild performed as part of a system controller
upgrade could take a long time without being visible, which could lead users to
cancel the rebuild process unintentionally, which required further intervention by
EMC Data Domain Support.
80081 Fixed the issue in which a Data Domain system's file system could panic due to lock
released on a NULL pointer. Now the Data Domain system returns an error message
about the NULL pointer, enabling the user to address the issue and avoid the panic.
80138 Fixed the issue in which join domain operations for some CIFS users failed due to
the lack of a valid signature.
80244 Fixed the issue in sketch computation that caused system panics during container
verification.
80753 Fixed the issue in which the Solaris tar command, executed over NFS on an archive
stored on a Data Domain system, did not restore the correct time stamps to the files
in the archive.
81059 Fixed the issue in which a Data Domain system could time out during a shutdown
process.
81117 Fixed the issue in which incorrect values for garbage collection progress
percentages in pre-enumeration and enumeration processes could be reported.
81339 Fixed the issue in which a Data Domain file system restart did not restart an index
merge that was previously underway, causing an index out of space condition.
81408 Improved the performance of fastcopy operations.
82008 Fixed the issue in which a Data Domain system could panic twice if the backup
workload consisted of mixed writes of different sizes, some smaller than 64K, and
again during the NVRAM log replay.
82713 Fixed the issue in which a Data Domain system's file system could panic when
attempting to replace a particular type file on a replication destination. This type of
file is routinely created by some backup applications. The application estimates the
file's size but writes no data to the file. The file with zero data was then replicated
Bug # Description
to a Data Domain destination system. If in a subsequent backup the application
wrote data to the file and the file with the new data was replicated to the
destination system, this action could cause the panic.
83605 Implemented new routines designed to improve the performance of database
backup operations involving overwrites and CBT (change block tracking) that occur
concurrently with other traditional backup activities.
83683 Fixed the issue in which the DD OS file system could panic due to a race condition
between the compaction thread and the deletion thread that was flushing the page.
83802 Fixed the issue in which the garbage collection performance could degrade
significantly, and when the garbage collection is running, some backup jobs could
time out due to slower ingest performance.
83993 Fixed the issue in which running space reclamation on a Data Domain system that
was converted from a single node configuration to an Extended Retention system
could result in a system panic.
84412 Fixed the issue in which a file transfer over NFS share could cause a system panic.
84748 Fixed the issue where if one of the 12 values on the Data Management > File
System Summary tab was an outlier with a very small value, then that smaller
unit would be used to represent all of the values. This could have unexpected
consequences.
85309 Fixed the issue in which NT LAN Manager authentication could periodically fail.
85567 Fixed the issue in which the time of a file being copied to the Data Domain system's
CIFS share was not retained.
86013 Fixed the issue in which the DD OS file system could fail during NetWorker and
Avamar backups because an asynchronous remote procedure call took too long.
86264 Fixed the issue in which a Data Domain system could panic when a users workload
had repeated set_size operations on unsynced files and internal resource counts
were not updated correctly.
86533 Fixed the issue in which the DD OS file system could restart unexpectedly
overwhelmed with IO requests.
86754 Fixed the issue in which a user in the dd admin group could not gain
administrative access to a Data Domain system due to an incorrect calculation of
groups to which a user belongs.
87010 Fixed the issue in which the Samba server daemon could panic on the Data Domain
system.
87655 Fixed the issue in which space usage traps would not be received when file system
usage exceeded 95-100 per cent.
87805 Fixed the issue in which users were prevented from accessing CIFS shares with the
share path /data/col1.
87965 Fixed the issue seen when executing the filesys enable command, in which the DD
OS file system could dump core, returning this error: There was a problem
bringing up the filesystem.
RELEASE NOTES
Bug # Description
88298 Fixed the issue in which the DD OS file system could panic, issuing the following
message during virtual synthetics backups:
"ddr/cs/cs_v0.c: cs_t0_batch_resegment_prep: 16145: !(dirty_size
> 0)")
Virtual synthetics backups now proceed normally as a result of this fix.
88371 Fixed the issue in which the performance of collection replication could
occasionally lag, degrading or, infrequently, stopping completely.
88437 Fixed the issue in which users could not use an NFS client to create files on the Data
Domain system with names including EUC-JP and SJIS character encodings.
88543 Fixed the issue in which the throughput performance of CIFS overwrite backups
degraded.
88578 Fixed the issue in which container replication could stall if invalid containers on the
destination system were missed during the search.
88735 Fixed an issue affecting extended retention systems running space reclamation
operations. If a replication break occurred, or if a resync was performed, a panic
could occur, depending on the stage of space reclamation processing.
88883 Fixed the issue in which a segmentation fault could occur if the /ddr/var/log/
debug/cifs directory was not present.
89723 Fixed the issue in which administrative users were not able to log in to the Data
Domain system after an upgrade to DD OS 5.2.2.0.
90270 Fixed the issue in which filecopy performance degraded after upgrading a
system to DD OS 5.2.2.0.
90315 Fixed the issue in which a transient missing segment error was reported on a Data
Domain system with Extended Retention software. This was a misleading error
message and was not cause for concern. The transient missing segment error no
longer appears.
91137 Fixed an issue by optimizing the statistics-gathering process to eliminate an extra
iteration inside file system. The fix insures that all statistics are gathered in a single
iteration, instead of two, and reduces unnecessary delay and resource contention
that could result in timeouts.
Bug # Description
43348 Fixed a variety of issues related to charts in the Stats tab of the DD System
Manager. The charts in the Stats tab under Status have been updated to utilize
Flash technology. This provides additional enhancements such as the ability to
hide and show graphs, enable and disable series, and view data point information
for additional details.
50838 Added new options to the autosupport CLI command to enable users to change
the subject line of an autosupport (ASUP) report. Details of the autosupport
set subject-tag, autosupport set subject-tag, and autosupport
Bug # Description
set subject-tag commands appear in the EMC Data Domain Operating System
Command Reference Guide.
67821 Fixed the issue in which the information returned by the user show detailed
operation included incorrect data in the password last changed field when
viewed in the Enterprise Manager, although the data was correct when viewed in
the CLI.
76194 Fixed the issue in the DD System Manager (formerly Enterprise Manager) in which
pressing Esc or Enter while a dialog is loading could either close or resubmit the
dialog, which could have unintended consequences, depending on which dialog is
loading when the key is pressed.
77552 Fixed the issue in which the Enterprise Manager GUI could hang due to a deadlock
in some multi-threaded code.
80284 Fixed the issue in which an unexpected error occurred in the DD System Manager
(formerly Enterprise Manager) after the user selected Status > Stats.
80464 Fixed the issue in which VTL could core-dump and restart when there is IO
contention on the first shelf of disk drives. This fix addresses an issue where
registry updates are not completing in time, resulting in a VTL restart. Specifically
the fix increases the priority of the IOs to the ext3 file system on the first shelf,
which includes the VTL registry operations.
82014 Fixed an issue where the Data Domain file system could panic due to memory leaks.
82950 Fixed the issue in which the Data Domain system could incorrectly generate an error
stating that the file system is disabled when the file system was actually only
momentarily unresponsive.
83228 Fixed the issue in which a user could set specific times for custom file system
reports but the reports would reflect the times and ranges the user set.
84800 Fixed the issue in which a Data Domain system experienced multiple panics due to
memory allocation issues.
87505 Fixed the issue in which adding a Data Domain system into Data Domain Enterprise
Manager caused the error ??systemInRecoveryMode??.
Bug # Description
47854 Fixed the issue that occurred after upgrading a Data Domain system to DD OS 5.0.
An NFS stream from the /ddvar/ ext3 file system could become unreadable
because its generation number could become updated, unbeknownst to the
function that looks up the stream.
74552 Fixed the issue that caused SNMP to stop and not to restart after creating and
destroying a VLAN and its IP alias.
76273 Fixed the issue in which a gateway could not be set on a VLAN interface. The route
set gateway or route reset gateway commands can now be used for this
RELEASE NOTES
Table 57 DD OS 5.4.0.1Networking Issues: Fixed (continued)
Bug # Description
purpose. See the EMC Data Domain Operating System Command Reference Guide for
details.
76348 Fixed the issue in which a false mismatach alert could be generated between actual
leading-zero and non-leading-zero IP addresses and netmask values set in the
registry.
77260 Fixed the issue that prevented platform services in DD OS from starting when the
onboard interfaces are configured into a virtual interface.
77321 Fixed the issue in which NFS or DD Boost stopped accepting incoming requests
after the Data Domain system reported repeated instances of connection attempts
being rejected.
77731 Fixed the issue in which powerSupplyDescription present within the
PowerSupplyWarning trap is NULL.
78034 Fixed the issue in which the Network Monitor could core-dump and restart if there
were no connections. Now the congestion checker reports to the log if there are no
connections, averting the Network Monitor issue.
78394 Fixed the issue in which a Data Domain system will dump core due to numerous
external connections, which created anomalies in the system congestion monitor
and failed to give the desired congestion statistics.
81914 Fixed the issue in which a system panic could occur if a user attempted to mount
Windows mount points via NFS or to mount Unix mount points via CIFS. Now,
instead of a system panic, the system returns an error message.
82425 Fixed the issue in which a file or directory from a Data Domain system-mounted file
system without READ access but with EXECUTE access was incorrectly given READ
access.
83260 Fixed the issue in which Data Domain system kernel could fail due to a watchdog
timeout.
83981 Fixed the issue in which the serial numbers of disks could appear differently in the
CLI and the System Manager GUI due to a mismatch.
84775 Fixed the issue in which remote procedure call requests could time out and cause
the DD OS file system to panic.
86993 Fixed the issue in which the DD OS file system could panic when a client attempted
to mount to a non-existent export path or when the client had no access
permission.
87295 Fixed the issue in which a large number of NFS exports on the Data Domain system
could overly tax the System Management Services (SMS) and cause the System
Manager (GUI) to hang.
89357 Fixed the issue in which the LUN (logical unit number) disappeared on a gateway
system.
Bug # Description
68658 Fixed the issue in which a fatal error code in certain PCI cards in DD640, DD670,
DD860, DD860g, or DD890 systems might go undetected. With this fix, any such
errors will cause a system to reboot and to issue an alert stating that the system
was rebooted in response to the PCI error.
73222 Fixed the following issue: Occasionally, following the replacement of a failed hard
disk drive on a Data Domain system with a SAS1 HBA, an alert would appear
indicating that the new drive is in a single path condition. Prior to this fix, the
workaround was to manually enable and disable the HBA port for that disk in order
to resolve the single path condition to resolve and to cancel the alert. Now this
resolution occurs automatically.
73771 Fixed the issue in which storage commands, such as storage add, storage
remove, or storage show could take an unexpectedly long time to complete on
Data Domain systems with a large number of shelves.
75153 Fixed the issue of a misleading alert that incorrectly warned of a connectivity issue
when in fact the alert actually reflected that an enclosure was low on spare drives.
75834 Fixed the issue in which performance of a Data Domain system with low stream
counts degraded due to a race condition that resulted in network request packets
being stalled.
76066 Fixed the issue in which the System Monitor could panic and core-dump due to
deallocating an already freed memory resource.
76834 Fixed the issue in which spurious error messages that occurred when reading disk
capacity affected the accuracy of the capacity assessment. This fix prevents alerts
from being generated from these spurious error messages and verifies whether
actual errors have occurred.
76923 Fixed the issue in which HBA ports on a Data Domain system became disabled after
a disk failure.
77087 Fixed the issue in which System Management Services (SMS) could dump core
when performing a disk unfail operation while generating a firmware upgrade
partition.
77211 Fixed the issue in which VTL returned exceptions when users accessed pages
related to system settings in the Data Domain System Manager (formerly
Enterprise Manager).
77320 Fixed a variety of issues affecting the behavior of system alerts related to fans, fan
speeds, and speed thresholds in DD640, DD670, DD860, DD860G, and DD890
appliances.
77377 Fixed the issue in buffer size calculation that caused the system monitor of a Data
Domain system to crash with memory errors.
77973 Fixed the issue in which an in-use disk showed the same serial number as another
disk in the enclosure, precipitating the failure of both disks.
78173 Fixed the issue in which a memory issue could create anomalous data and cause a
system failure.
78304 Fixed a variety of issues related to systemdID.
RELEASE NOTES
Bug # Description
78613 Fixed the issue in which the Data Domain file system could repeatedly experience
panics after upgrading from DD OS 5.2.1.x to DD OS 5.3.x.
78970 Fixed the issue in which a Data Domain system could experience a soft lock due to
abnormally high logging activity.
79015 Fixed the issue in which the Host Bus Adapter (HBA) driver could not schedule a
successful device rescan following the device discovery error and the hot plug of
the device, due to the incorrect use of expired system information.
79098 Fixed the issue in which the following sequence of events could occur: the vtl
tape copy operation failed after copying a portion of the tapes requested, which
subsequently caused a system crash, and after VTL restarted, the vtl tape
copy operation did not copy any tapes.l
79230 Fixed the issue in which the BMC module in the DD990 system controller could
become unresponsive.
79299 Fixed the issue in which an HBA error in a Data Domain system running DD OS
5.1.1.2 could experience a fault that disabled SAS 1 HBA's two ports, which further
removed the enclosures from both ports.
80952 Fixed the issue in which a faulty drive could cause a Data Domain system to shut
down while reporting impossible temperature readings.
80959 Fixed the issue in which a DD OS system upgrade could take much longer than
expected, and the file system could fail to be enabled.
81222 Fixed the issue in which a Data Domain system's system management services
(SMS) could core-dump due to a memory leak caused when a lower revision of SMS
allocates memory but fails to decode or free it for new string fields in the higher
revision of SMS.
81736 Fixed the issue in which initialization delays, particularly related to enclosure
scans, could persist long enough to encounter a timeout. This in turn could cause a
system panic, although the panic generally failed over to normal operation. This fix
revises the timeout to avoid the panic.
81847 Fixed the issue in which a user would receive no response from the Data Domain
system and could not collect a support bundle.
81864 Fixed the issue in which the system show stats vtl command could dump
core if it is executed while other VTL operations are running.
82094 Fixed the issue in which a Data Domain system could fail to upgrade to DD OS
version 5.2.0.6 from version 5.1.0.4.
82503 Fixed the issue in which a memory leak could cause System Management Services
(SMS) to crash.
82614 Fixed the issue in which a DD OS system upgrade for a DD120 or DD140 could stall
due to limited space available on the /ddvar volume.
82982 Fixed the issue in which the copy/reconstruction process did not initiate as
expected after an error was detected.
Bug # Description
83326 Fixed the issue in which daemons or scripts with calls to IPMI would hang because
the BMC (baseboard management controller) software had hung. Now an error is
returned after calls to IPMI hang indicating the BMC software issue.
85860 Fixed the issue in which the system upgrade precheck CLI operation could
unexpectedly perform an system upgrade of DD OS, not simply perform the pre-
checking.
86811 Fixed the issue in which a RAID could panic and reboot.
87829 Fixed the issue in which the Enterprise Manager summary screen on Data Domain
systems with the Extended Retention software option did not display both Active
tier and Retention tier space.
88417 Fixed the issue in which ONLINE disks became classified as UNKNOWN disks.
89696 Fixed the issue in which a user could not add multiple Data Domain Management
Center licenses with the same feature name (system count). A user could add the
licenses with the CLI, but only one license would be displayed in the GUI.
90243 Fixed the issue in which returning from an operation to delete a virtual synthetics
file took too much time.
Bug # Description
62297 Provided multi-streaming support for initializing replication contexts from
snapshots.
64656 Fixed the issue in which a replication context could become disconnected if the
user manages both the source and destination systems in the Enterprise Manager
and attempts to modify the replication contexts settings from the destination
system.
65477 Fixed the issue in which space statistics reported for MTree replication on a
destination Data Domain system were inaccurate.
73886 Fixed the issue in which a Data Domain system could panic in the following
situation. An MTree replication context on the source system points to a Data
Domain destination system with Extended Retention, and a file in the destination
Mtree has been migrated (data movement). When the source system detected the
apparently missing segments, the panic was triggered.
74441 Fixed the issue in which snapshot IDs in the registry left behind by MTree
replication could prevent expired MTree auto snapshots from being removed by the
garbage collection process.
74798 Fixed the issue in which a Data Domain system could panic because the replication
break timed out while the operations to shut down replication connections were
still in process.
76309 Fixed the issue with the MTree Replication break command, which required that the
Data Domain file system must restart in order to clear the snapshot protection
(instantiated as a soft lock) on the auto-snapshot created by MTree Replication,
RELEASE NOTES
Bug # Description
which further prevented the snapshot from being removed by the Garbage
Collection process.
77530 Fixed the issue in which all CLI commands return filesystem not
responding during initialization of a new MTree replication context.
77862 Fixed the issue of poor replication throughput performance from a large-capacity
Data Domain system to a lower-capacity Data Domain system. In particular, the
issue involved replication from a Data Domain system with a large stream count to
a system with a small stream count, in which the larger system could exceed the
smaller system's capacity.
78306 Fixed the issue in which network problems could affect checksums with encryption
over the wire. The fix strengthens the checksums to withstand network
transmission irregularities during replication.
78840 Fixed the issue in which MTree replication contexts were created with inconsistent
options. If they were created in the Data Domain System Manager (formerly
Enterprise Manager), they are created with the propagate retention lock
option disabled by default. But if they are created in the CLI, the propagate
retention lock option is enabled by default. This fix eliminates that
inconsistency by enabling the option by default in both settings.
79951 Fixed an issue resulting from the interaction between garbage collection and
replication contexts with low-bandwidth optimization enabled. Garbage collection
would refuse to run due to benign errors that look like missing segments.
80054 Fixed the issue in which data ingest rates could slow down because NFS threads
could become blocked if DNS lookups were delayed due to an unresponsive DNS
server.
80608 Fixed the issue in which the initialization of an MTree replication context could not
be started when an error interrupted the initialization.
80660 Fixed the issue in which two different threads become deadlocked caused a
timeout in the NFS3 Service thread, which in turn causes a system panic.
82618 Fixed the issue in which the Data Domain file system could panic because the base
snapshot identifier of a replication context on the source system became
unsynchronized with the base snapshot identifier of the replication context on the
destination system.
82724 Fixed the issue in which a quota limit was inappropriately applied to the
destination Data Domain system in an MTree replication set up. Enforcing the quota
limit on a destination system can cause a Data Domain file system panic when the
amount of data written to the destination system exceeds the quota limit. This fix
does not enforce the quota limit on the destination Data Domain system in the
MTree replication setup, and thus it resolves the Data Domain file system panic.
83438 Fixed the issue in which viewing real time charts over a long period of time could
cause result in an overflow exception.
84754 Fixed the issue in which shutting down MTree replication could cause memory
anomalies and an eventual file system panic.
Bug # Description
85297 Fixed the issue in which a user could not set up replication using the System
Manager GUI after upgrading to DD OS 5.2.1.0. Replication could still be set up with
out any issues using the command line.
Bug # Description
67273 Fixed the issue in which a Data Domain system could experience a kernel panic
because of un-synchronized access to a target device list in a race condition.
75327 Fixed the issue in which VTL exhibited degraded NDMP backup performance.
76559 Fixed the issue in which the DD System Manager (formerly Enterprise Manager)
reported inaccurate VTL compression statistics.
76574 Fixed the issue in which users received incorrect "Tape Alert" notices from their
backup system that used the IBM lin_tape driver.
76676 Fixed the issue in which a kernel panic could occur during memory allocations
associated with releasing space.
77020 Fixed the issue in which VTL could dump core during the vtl initiator show
operation while creating a support bundle when the associated links are offline.
77243 Fixed the issue in which VTL, which could stop due to a large, heavily loaded
configuration and to problematic file locality, could then fail to restart because the
time required to perform VTL recovery when restarting might actually exceed the
allowed startup time.
78571 Fixed the issue in which users could not add drives to a TS3500 library with the
I/OS license in the Enterprise Manager GUI and could only add drives using the DD
OS command line.
78603 Fixed the issue in which a direct connection between a Data Domain system and
EMC Celerra Storage via Fibre Channel did not function.
78824 Fixed the issue in which a Data Domain system re-booted and one or more disks
failed due to a race condition caused by multiple SSRs
78985 Fixed the issue in which the vtl tape move operation failed to move tapes
between drives in a TS3500 library.
79331 Addressed an issue that existed when using more than 5040 elements on IBMi
systems. This problem typically occurs when the VTL is configured with a large
number of slots and tapes, greater than ~5000.
79586 Fixed the issue in which a Data Domain system kernel could fail after a soft lockup
panic.
79983 Fixed the issue in which VTL and DFC devices could become invisible to any
initiators after issuing the scsitarget endpoint connection reset all
command.
80233 Fixed various issues in which VTL may restart during backups when the
administrator issues vtl show commands to the Data Domain system during periods
of heavy backup loads.
RELEASE NOTES
Table 60 DD OS 5.4.0.1VTL Issues: Fixed (continued)
Bug # Description
81676 Fixed the issue in which VTL users could not allocate tape drives after performing an
IPL (initial program load) to an input-output processor (IOP) or a logical partition
(LPAR) in an IBM i environment.
81722 Fixed the operation of the vtl tape show all or vtl tape show all
barcode barcode commands so that tapes smaller than 0.1GB are consistently
reported as 0.0GB.
82539 Implemented enhancements in several areas of VTL thread processing: individual
thread progress history, general thread progress history, time stamping, VTL
watchdog activity, and VTL server monitoring.
82994 Fixed the issue in which a Data Domain system could enter a race condition where a
command cannot be cleaned up after execution, because of incorrectly putting
back the command on deferred list.
83176 Fixed the issue in which the Tivoli Storage Manager application running on AIX
could generate a SCSI operation that would necessitate a Data Domain file system
operation on every tape in a tape library. In situations in which a Data Domain
system was heavily loaded or was performing garbage collection, the SCSI
operation could take longer than the time allotted for it, causing backup problems
and VTL restarts.
84170 Fixed the issue in which a user could not in a single step move tapes with
sequential barcodes that were placed in non-sequential slots.
84343 Fixed the issue that affected customers who use VTL with an IBM i license, who
upgraded to DD OS 5.3 from a previous release, and who also had an invalid or
unset SystemID. The WWNN for FibreChannel ports will no longer be changed post-
upgrade.
84899 Fixed the issue in which requesting a slot count during tape movement may cause
VTL to time out and restart. This could occur during a small timing window.
85193 Fixed the issue that caused the first reboot after an upgrade from DD OS 5.2 to 5.3
to fail because the system could not probe all the target ports, and as a result the
upgrade itself did not complete.
86644 Fixed the issue in which VTL registry transactions were not processed in sequential
order.
86696 Fixed the issue in which a tape could transition to a stuck condition from which it
could not be ejected if an error occurred, and no other IO to the tape was possible.
87457 Fixed the issue in which the VTL service could fail and restart three times in
succession and then be disabled if the user used the System Manager GUI instead
of the command line to create tape drives before opening the drive folder in the
GUI.
88440 Fixed the issue in which the auto option of the CLS command vtl tape move
did not work correctly.
Environment and System Requirements
So that you can use DD OS 5.4.3.0, make sure your Data Domain system and client
system tools conform to these requirements.
Supported Systems
DD OS 5.4.3.0 is supported on the following Data Domain systems:
u
Appliance Series: DD990, DD7200, DD890, DD880,DD4500, DD860, DD690,
DD4200, DD670, DD660, DD2500, DD640, DD630, DD620, DD610, DD580, DD565,
DD530, DD510, DD160, DD140, DD120
u
Appliance Series with Extended Retention software option: DD990, DD7200, DD4500,
DD860, DD4200
u
DDX Array Series: DD880, DD690, DD580
Supported Browsers
The following browsers are supported for use with the DD System Manager (formerly
Enterprise Manager):
u
On Windows XP Pro and Windows 7: Internet Explorer 7 , 8, and 9, Google Chrome,
and Firefox 16
u
On Mac OSX: Firefox 16, Google Chrome
File Downloads in Internet Explorer
In order to allow file downloads to show a prompt dialog in Internet Explorer, it is
recommended that the Security Zone in which the Data Domain system's hostname or IP
address belongs has the Automatic prompting for file downloads option set to 'Enabled'
for that Security Zone.
Procedure
1. To change this setting for a specific Security Zone, click on Tools > Internet Options to
see the Internet Options dialog.
2. Click on the Security tab, and then select the Security Zone which applies to the Data
Domain system.
3. Click on the Custom level... button to open the Security Settings dialog, then scroll
down to the Downloads section.
4. For the Automatic prompting for downloads option, select the Enabled radio button,
then click OK. If a prompt appears asking if you are sure you want to change the
settings for the Security Zone, click Yes.
5. Click OK again to exit the Internet Options dialog.
Supported Flash Versions
Flash version 11.5 has been tested for use with the DD System Manager (formerly
Enterprise Manager).
RELEASE NOTES
Known Issues and Limitations
This topic identifies known and open issues in Version 5.4.3.0 of DD OS.
DD Boost Known Issues
u
When running Backup Exec 2010 or 2012 with the DD Boost plugin version 2.5.0.3 or
earlier, duplication will fail reporting error 5009-nfs clone status failed or,
in ddfs.info log, ERROR: MSG-SFS-00004: **** fastcopy...error:
Internal error. This is due to an inadvertently introduced version
incompatibility. The workaround is to upgrade the DD Boost plugin to version 2.5.5.0
or later.
u
Due to a command line parsing limitation, DD Boost storage-units created with a
name of p, pa, pas, pass, passw, passwo, passwor or password cannot be deleted
via the ddboost storage-unit delete command or the Enterprise Manager.
The workaround is to not create storage-units with any of these names.
u
DD Boost should not be enabled on a Data Domain system that is a target for
collection replication.
u
As a result of how DD Boost streams are opened, DD Boost traffic can affect certain
statistics as though the Data Domain system were running replication. See KB article
94642 at the EMC Online Support site.
u
When you set the app-optimized-compression option on the filesystem
command to Oracle1 in order to backup Oracle data to the Data Domain system
using RMAN multiplexing, this can cause the Data Domain system to falsely detect
Oracle markers, even if you are not running Oracle data backup operations. However,
the app-optimized-compression option on the filesystem command is not
set by default, and even if you do set it, you can safely ignore the reports of falsely
detected Oracle markers.
u
When running NetBackup 7.0.1 and 7.1, opt-dupe jobs may fail with error code 84.
Examination of the bpdm log indicates 'copy_data_tir: Invalid image
copy: error 2060001' or at a high debug level a message of the form:
sanity_check_extent_copy_args STS_EINTERNAL mismatched offsets (0,
20709376) for stspi_copy_extent
This is a known NetBackup problem (ETrack 2270185). Contact Symantec for the
appropriate EEB.
u
With Distributed Segment Processing disabled, when a Backup Exec backup job runs
into a hard quota limit on a DD Boost storage unit, the backup job fails, and the
backup image is not deleted from the Data Domain system. In this situation, the
image cannot be erased from within the Backup Exec GUI. If you encounter this
situation, contact EMC Data Domain support for advice on how to proceed.
File System Known Issues
u
In order to ensure optimal performance of a Data Domain system with the Extended
Retention software option, you should not expand retention units in single shelf
increments. You should also not wait until the retention unit is nearly full before
expanding it.
u
When using the one-to-many topology for MTree replication contexts, two contexts
using the same source MTree cannot replicate in parallel. Once one context begins
replicating, the second context must wait until the first one finishes. Replication then
begins for the second context. This serial replication behavior is most noticeable
when simultaneously initializing large replication contexts.
Known Issues and Limitations 67
u
With certain vtl and scsitarget CLI commands, if a VTL, group, or initiator is
given a name that matches the starting letters of a command parameter, the
commands will fail with an inaccurate message.
u
On a Windows Vista or Windows 7 computer, you may see a File in use or
Filename is locked for editing by username message when
opening a Microsoft Office document (e.g., Excel or Word file) in a remote shared
folder in Windows Explorer that used the Details view and the Preview Pane layout.
This is caused by Windows holding a lock on the files for longer than normal, which is
behavior associated with the Details view and Preview Pane layout. The cause of this
issue is a sharing violation that happens between the operating system and the
Office application over a network resource.
This is a suggested workaround. On desktops accessing the files on a remote shared
folder, modify the following settings in Windows Explorer to disable the Windows
functions that cause this behavior:
1. Click Tools > Folder Options and select the View tab.
2. Uncheck Show pop-up description for folder and desktop items.
3. Uncheck Show preview handlers in preview pane.
4. Click Apply and then OK.
5. Click Organize > Layout and uncheck Details pane.
6. Click Organize > Layout and uncheck Preview pane.
u
Be aware that while you can add conditional auditing to a file in Windows 2012, the
option to add conditional auditing to a file is not available on a Data Domain CIFS
share volume.
u
Be aware that a user with the user or backup-operator role cannot overwrite a file with
the fastcopy operation.
u
MTree replication of the /backup MTree is not supported on systems with the DD
Extended Retention option. If Extended Retention is enabled, data to be replicated
needs to moved into other MTrees than /backup.
u
For replicated MTrees created before upgrading a Data Domain system to DD OS 5.3,
the age-threshold shows as Infinite, and the default policy configured by the user will
not be applied to such MTrees. The user must explicitly modify the age-threshold for
such MTrees in order to effect data migration to the retention tier.
u
Self-signed certificates can be used as imported host certificates for HTTPS. If you are
generating your own CA and signing the CSR, use organization unit and common
name fields values (RFC 5280) to distinguish between CA and host certificate. Refer
to RFC 5280 at http://tools.ietf.org/html/fc5280 for certificate attribute information.
u
If the space reported from the filesys expand CLI operation is incorrect following
the addition of an enclosure, disable and then re-enable the file system after the file
system is fully operational. After the file system restarts, the filesys expand
operation should report the correct space.
u
Migration of data and configuration information from one Data Domain system to
another can fail if the migrating source is configured for MTree replication. The
workaround for this failure is to break the MTree replication context, complete the
migration from the current Data Domain system to the new Data Domain system and
re-establish the context on the new Data Domain system.
u
Be aware that the operations in the DD System Manager for enabling and disabling
users are based on GMT and not on local times.
u
On systems with the DD Extended Retention software option, issuing a replication
resync may cause a file system panic. To prevent this from happening, you must
RELEASE NOTES
suspend space reclamation and stop data movement to the retention tier if the data
movement is running prior to issuing the replication resync. After the replication
resync completes, return space reclamation and data movement to their previous
states.
General Known Issues
u
If your DD OS 5.4.x or 5.5.0.x system is managing a Data Domain system that has IPv6
NIS servers, then you will not be able to add or remove NIS servers using the System
Manager GUI. The action to add or remove an NIS server will accidentally result in
removing the IPv6 server from the Data Domain system that supports IPv6.
u
Do not attempt to configure IPv6 interfaces with Enterprise Manager (EM). This
version of EM does not support IPv6. While some IPv6 addresses may display
properly, some locations may not. If you select a displayed IPv6 interface or attempt
to configure an IPv6 interface, you may see an error, or proper configuration may
otherwise not be possible.
u
The GUI auto-refresh feature, which refreshes the page every ten minutes, has the
effect of nullifying the GUI session timeout if that timeout is set to greater than ten
minutes.
Networking Known Issues
u
Be aware that the nfs reset clients command has the effect of deleting all the
NFS client and share configurations without prior warning. While this command's
behavior is correctly documented, users should note that it is not hardened with an
Are you sure you want to do this? warning.
u
Because DD OS does not support file locking (byte-range locks), the Network Lock
Manager (NLM) service has been disabled starting with DD OS 5.2. (This was done to
prevent upgrade issues when local clients or scripts are accessing the /data mount
point.) This can cause backup jobs to hang or fail unexpectedly when the backup
application or client relies on the NLM service on the Data Domain system. To resolve
this issue, mount the Data Domain file system with the appropriate option that
prevents sending of NLM requests to Data Domain system. That is, the client or
application should not rely on the NLM service on the Data Domain system. For Linux
clients, use the -nolock mount option. For Solaris clients, use the -llock option.
For other clients, refer to the manual entry for the NFS mount command.
u
Customers using Data Domain gateway appliances should not upgrade their systems
to DD OS 5.3.0.x. Upgrading gateway systems to DD OS 5.3.0.x could cause customer
data to become unavailable.
u
The Data Domain system supports router auto-generated IPv6 addresses that are
based on the MAC address. These addresses are added when the interface is brought
up, and they are removed when the interface is brought down. The user has no
control over these addresses from the Data Domain system, but these addresses can
be used to access the Data Domain system remotely. These addresses are not
currently visible with the net show settings CLI, but they can be viewed with the
net config CLI.
u
The first ro-community with access to localhost must be present in order for SNMP
traps to be sent out.
u
The mtree list operation for an MTree replica calculates an incorrect sum of files,
reflecting only the active files on the source system and not the active files on the
source plus the active files on the Extended Retention system.
u
While DD Boost IO jobs (backup or restore) are in progress, do not make configuration
changes with either the ddboost or nfs CLI commands. The only exceptions,
resulting in safe configuration changes, are for enabling or disabling distributed
segment processing and ifgroup changes.
u
Under some circumstances when the numbers of exported NFS ports is greater than
2, SNMP NFS can report an error, and not function correctly. This is expected, and
there is no workaround. This issue will be addressed in a future release.
u
When an alias interface has been defined for a virtual interface, either directly or for a
VLAN interface that is itself defined for the virtual interface, the alias interface cannot
be removed (destroyed) after the virtual interface is reset. In order to remove the alias
interface, you must first remove the interface for which the alias was defined. That is,
you must first remove either the virtual interface itself or the VLAN to which the alias
refers.
Platform Known Issues
u
Be aware that in order to upgrade a Data Domain system, you must disable NFS file
export if it is enabled on your current Data Domain system. Otherwise the upgrade
may fail.
u
Be aware that adding Fibre Channel IO Module(s) to an existing DD4200, DD4500 or
DD7200 controller will require moving one Ethernet IO Module to slot 5 if the
resulting IO Module quantity will be the maximum of six allowed in these models.
Consult either the EMC Data Domain DD4200, DD4500, and DD7200 Systems Hardware
Overview Guide or the EMC Data Domain DD4200, DD4500, and DD7200 Systems IO
Module and Management Module Replacement or Upgrade Field Replacement Guide for
specific slot addition rules. Moving an Ethernet IO module changes its port names,
which in turn requires reconfiguring all the prior network configurations (which are
present on the prior port names) to the new port names on new slot, that is, slot 5.
u
If you decide to perform a controller upgrade (headswap) on a legacy Data Domain
system to DD7200, DD4500, or DD4200 system, be aware of how certain decisions
affect the result. If you perform the controller upgrade without creating the DD OS file
system, then the file system core partition /ddr/var/ext is roughly 89GB. If you
create the new file system, then the file system core partition is about 170GB.
u
On some DD4200, DD4500, or DD7200 systems, there is only one on-board Ethernet
port, and the offline diagnostics suite requires ports to be paired to run the external
loopback test, because all ports on optional SLICs are dual or quad ports. Accordingly
no port can be used to pair with the only onboard port, and thus the onboard port
named as ethMa in DD OS is not tested during the offline diagnostics external
loopback tests.
u
If on a Data Domain system the spare SATA drive is replaced with a SAS drive in an
ES30 shelf, the new SAS drive is incorrectly allowed as the spare drive. The current
workaround is to rely on alerts about disk mismatches to signal the need for a
remedy. Checks to detect this situation more specifically will be added in a future DD
OS release.
u
If on a Data Domain system with ES 20 and ES-30 shelves a v (available) SAS drive
is replaced with a v SAS drive, DD OS incorrectly permits the replacement. The
current workaround is to rely on alerts about disk mismatches to signal the need for a
remedy. Logic to block this type of replacement will be added to a future DD OS
release.
u
When using the DD System Manager (formerly Enterprise Manager), in the table that
appears after selecting System Settings > Licenses, the check boxes by the license
keys display in some instances and not in others. In addition, when a check box is
selected, any license key and name in that row will disappear. This issue occurs only
with the Firefox 15 browser, and only on Macintosh OS/X and Linux systems. The
issue does not occur on Windows systems.
RELEASE NOTES
u
Port numbering in certain Data Domain legacy appliance models (for example,
DD660, DD690, DD680g, or DD880) is subject to some constraints. The interface
name may be dependent on the card type used in the slot. Chelsio 10 Gb cards
generally always have the highest numbers in the interface name. Consult the
hardware overview document for your particular Data Domain system at the EMC
Online Support site for more information.
u
Serial numbers for EEPROM units in most Data Domain systems cannot be re-
assigned with utilities in this release of DD OS. (Exceptions include the DD430,
DD460, DD460g, DD560, and DD560g models.)
u
When performing a controller upgrade (headswap) in which ports are going to
change, be sure to select all ports on the VTL access groups that will be affected by
the port change before (and not after) doing the head swap. Doing this will then allow
you to use any of the access group modifications that may need to be done after the
head swap.
u
Prior to swapping a system controller with a new one, clear all the alerts associated
with the controller being swapped out. Otherwise, these alerts will trigger false
alarms for the new controller. Use the alerts clear alert-id num CLI
operation to clear alerts before performing the controller swap (or after as the case
where a controller being swapped was not functioning before the swap).
Replication Known Issues
u
MTree replication between a source Data Domain system running DD OS 5.2.x source
and a destination Data Domain system running DD OS 5.4.x or DD OS 5.5.x
destination is not supported when Retention Lock governance is enabled on the
source MTree.
u
Be aware that low bandwidth optimization is not supported on Data Domain systems
with the Extended Retention software option enabled. For this reason you should not
use the utility in the System Manager GUI that enables low bandwidth optimization
on a system with Extended Retention. If you do enable low bandwidth optimization
on the system with Extended Retention, it can cause repeated file system panics.
Finally, if you enable low bandwidth optimization in this way, you can only disable it
from the System Manager GUI and not from the DD OS command line interface.
u
Using low bandwidth optimization on a Global Deduplication Array (GDA) is an
unsupported configuration that can cause a system panic.
u
When collection replication is performed, all users' information is copied over from
the source to the destination Data Domain system, but the users' home directories
will not be copied. For a user named so, this would result in this message:
Could not chdir to home directory /ddr/var/home/so:
No such file or directory when login to destination DDR as "so".
To avoid this message, create an identical set of users on both the source and
destination Data Domain systems prior to the initial collection replication operation.
u
If replication throttling is enabled with managed file replication, the throttling may
cause the job to fail. The workaround is to disable all replication throttles. If throttling
must be used, the short term workaround is to set the throttle manually with the
repl_throttle destination port rate command found in /ddr/bin/.
Contact EMC Data Domain Support if this is required.
u
During MTree replication initialization, the destination will report it has synchronized
when the first snapshot is replicated, but the source will report it is initializing until
the first MTree replication snapshot is replicated. This will only occur when there are
user-created snapshots on the source prior to replication initialization.
u
Using the DD System Manager to create MTree replication contexts where the source
system has the Data Domain Extended Retention License (previously called the Data
Domain Archiver) is not normally supported. Contact EMC Data Domain Support if you
require this support.
u
When you run operations that report the progress of replication jobs, reports include
the number of files replicated in directory replication, but those reports do not
include the number of files replicated in MTree replication.
u
The output of the replication watch CLI operation reports the number of files
replicated with directory replication but not the number files replicated with MTree or
other replication types.
u
Be aware that you cannot move tapes from a tape pool that is a directory replication
source. As a workaround, you can do one of the following; either copy the tape to a
new pool and then delete the old pool, or use an MTree pool, which allows you to
move tapes from a tape pool that is a directory replication source.
u
VTL normally prevents you from creating VTL pools with duplicate names. However,
when using replication it is possible to create this condition when two Data Domain
systems are running VTL in which one Data Domain system is creating an MTree Pool
with a name, for example, VTLPool and the other Data Domain system is creating a
BCM pool with the same name.
When replication is configured between these two Data Domain system and the VTL
pools are part of the replication context, then the pools will be created on the other
Data Domain system resulting in two VTL pools on the Data Domain system with the
same name.
The workaround is to break the replication context, delete the replicated pool, and
rename one of the pools.
u
When MTree replication contexts containing significantly large amounts of data are
configured and the contexts are being initialized on a Data Domain system, those
contexts may incorrectly show ERROR status in the DD System Manager. The error in
the DD System Manager is transient and goes away after the initialization process is
completed on the Data Domain system.
VTL Known Issues
u
Do not configure a Data Domain system with more than 255 tape devices in a single
access group.
u
Be aware that when persistent reservations are disabled or enabled, the process of
disabling interrupts the IO to all the VTL devices. That is, the process fundamentally
removes the VTL devices and then adds the devices back, irrespective of whether
they are using persistent reservations. Clients should be able to recover the IO after
the disabling or enabling process for persistent reservations.
u
Be aware that the DD OS SCSI Persistent Reservation Activate Persist Through Power
Loss (APTPL) implementation preserves persistent reservation information in most
situations even when APTPL is not enabled.
u
DD OS 5.4 supports SCSI-3 Persistent Reservation as defined in the SCSI
specifications, with the following limitations:
l
The PERSISTENT RESERVE OUT REPLACE LOST RESERVATION command is not
supported.
l
The PERSISTENT RESERVE OUT REGISTER AND MOVE command is not supported.
l
The PERSISTENT RESERVE IN READ FULL STATUS command is not supported.
l
When Persistent Reservations are disabled or enabled, the IO is not interrupted if
no device in the host machine is using Persistent Reservations. However if any
device in the host machine is using Persistent Reservations, the disable process
will interrupt the IO to all the VTL devices irrespective of whether they are using
RELEASE NOTES
Persistent Reservations. Host systems should be able to recover the IO after the
Persistent Reservations service is disabled or enabled.
u
If you plan to replicate tape data from a Data Domain system with a later version of
DD OS to another Data Domain system with an earlier version of DD OS, make sure
that the earlier version of DD OS supports the tape format that you are replicating. If
the earlier DD OS system does not support the tape format, you will be able to
replicate the tape data to the earlier DD OS system, but that earlier system will not
recognize or see, read, or manage it using VTL.
In the event this replicated data needs to be accessed by VTL, there are two options:
l
Upgrade the Data Domain system with the earlier DD OS version to a version of DD
OS that supports the tape format used on the Data Domain system with the later
DD OS version, or
l
Replicate the data back to the original Data Domain system (in case recovery is
required) and access the tape from the source (original/primary) system.
u
If your Data Domain VTL system is directly connected to a host device (e.g., a media
server) and a port goes offline and does not come back online, consult Knowledge
Base article 90104 at the EMC Online Support site for information on restoring the
port and re-establishing the link.
u
VTL in DD OS 5.1.1.0 or later releases is not interoperable with the EMC Disk Library
(EDL). As a result, the EDL does not accept the Data Domain VTL as a back-end
physical tape library, and the EDL cannot export tapes to a Data Domain system with
VTL.
u
If a SLIC or qLogic HBA is removed from a Data Domain system after it fails and is
never replaced, the VTL port alert is not cleared. The system administrator must
manually clear the VTL port alert.
u
Using the scsitarget persistent-reservation clear CLI operation can
cause a unit attention alert to be generated. However, if you execute the operation
a second time, it completes normally, without the alert.
u
If a Data Domain systems I/OS and VTL licenses are installed under DD OS 5.1.1.0 or
later, DD OS 5.2.0.6 or later, or DD OS 5.3.0.0 or later, the Fibre Channel World Wide
Node Name (WWNN) values will be unique. If a Data Domain system is upgraded to
one of these DD OS releases, the WWNN values will be changed. On a Data Domain
system running DD OS 5.3.0.0 or later, this name change can be managed by using
the scsitarget transport option set wwnn-scope CLI operation.
u
EMC has determined that customers may experience issues with this DD OS release
on systems that match the following criteria:
l
VTL license is applied.
l
I/OS license is applied, or will be applied in future.
l
DD-specific WWPNs on the VTL target ports. Look for target ports containing
WWPNs that have the 3-5th octets set to 00:21:88, which is the DD-specific OUI.
l
There are AIX initiators configured to access LUNs on a VTL existing prior to the
upgrade to the fixed release or the installation of the I/OS license, or both.
Upon upgrading to this release, or when applying the I/OS license to a system
running this release, the WWNNs will change on all target ports, making each of them
unique. This may affect the ability of some initiator systems (including backup
software media management or media access systems, and SAN-attached NDMP
backup systems) to regain access to pre-configured virtual tape drive and changer
LUNs. Initiators on AIX systems are known to be particularly sensitive to this change.
Some other initiator systems may need to be rebooted, or else they will need to
perform an online rescan of their Fibre Channel targets to regain access to the VTL
drive and changer LUNs following this change.
Customers who are considering an upgrade to this release should contact EMC Data
Domain Support for assistance prior to taking action if all of the following are true:
l
The VTL license is currently applied.
l
The I/OS license is currently applied, or will be applied in future for backups from
IBM iSeries systems.
l
There are AIX initiators accessing virtual libraries on the Data Domain system prior
to the upgrade and/or I/OS license installation.
l
The WWNNs of any two or more VTL target ports on the system are identical (as
noted in the vtl port show hardware CLI command output).
Customers who are not using VTL, who have not yet configured any virtual libraries for
use on their initiator systems or in their backup software, or who are using VTL but
not using or planning to use the I/OS license to allow backups from IBM iSeries
systems may safely ignore this warning.
u
The iSeries V5.4 and V61M0 systems generate a SCSI-level command to move a tape
from a tape drive to the same tape drive when the DSPTAPSTS command (Display
tape status) is executed. This command is not supported by the Data Domain VTL. As
a workaround, the command may succeed if you execute it a second time.
u
If the Data Domain system is very busy processing IO requests, the VTL commands
that process a large number of objects may time out and need to be reissued. This is
a temporary condition because the commands will run to completion once the IO load
on the Data Domain system has lessened.
Viewing Documents on the EMC Online Support Site
Follow these steps to view EMC Data Domain documents at the online portal.
To view documentation for EMC Data Domain products, go to the EMC Online Support site
and click Support by Product below the Search box. Type Data Domain in the Find a
Product box, wait for those words to appear in the list of matches below the box, and
click the words. Then click . In the list of categories under the Search box, click
Documentation.
u
The Product choices let you filter results by Data Domain system model number, such
as DD990, or by DD OS software release.
u
The Content Type choices let you filter results by category. Click More under Content
Type to see all of the categories. The categories that contain end-user and
compatibility documentation are these:
l
Manuals and Guides, for the software and hardware manuals for your system and
for integration guides that explain how to use EMC Data Domain systems with
backup software and other products.
l
Release Notes, for specific versions of the EMC Data Domain Operating System.
l
Compatibility Documents, for guides that show which EMC and third-party
components are compatible.
Open Source Software
This EMC 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, EMC will provide a copy of the source code that is required to be made
available in accordance with the applicable license. EMC may charge reasonable
RELEASE NOTES
shipping and handling charges for such distribution. Please direct requests for copies of
open source code in writing to this address:
EMC Legal
ATTN: Open Source Program Office
176 South St.
Hopkinton, MA 01748
DD OS Version 5.4.3.0 Upgrade Instructions
Upgrading to a new version of DD OS involves both planning for the upgrade and actually
performing it, as described in the following sections.
Preparing to Upgrade to DD OS 5.4
An upgrade to release 5.4 can be performed only from systems using release families 5.1,
5.2 or 5.3. Typically when upgrading DD OS, we only support the ability to upgrade two
release families at a time (4.7 to 4.9, or 4.8 to 5.0, etc.). However, in the case of DD OS
5.4, upgrading from three previous release families is supported. In order to upgrade to
release 5.4 from a release family earlier than 5.1, you will need to upgrade in steps. See
the latest 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, 5.0, 5.1, or 5.2 release notes for upgrade
instructions as appropriate for the version your system is currently running for exact
upgrade steps. The most current release notes for all versions of DD OS can be found
online at the EMC Online Support site.
If your upgrade plan calls for multiple successive upgrades (for example, from 5.1 to 5.3
and then to 5.4), 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.1 or later system, download the 5.4 image from the
appropriate EMC download site, and follow the upgrade instructions, as described in
Upgrading to DD OS Version 5.4.3.0 on page 77. The time for the upgrade process to
run depends on the amount of data on the Data Domain system. (If an upgrade fails,
contact your contracted support provider or visit us online at the EMC Online Support
site.)
Be aware of the following before you perform the upgrade to DD OS 5.4:
u
Data Domain systems with the Extended Retention software option enabled are
supported in fresh DD OS 5.5.0.x installations. However, Data Domain systems with
the Extended Retention software option enabled running earlier DD OS version such
as DD OS 5.4 cannot be upgraded to DD OS 5.5.0.x. Support for upgrading DD OS
versions with the Extended Retention software option enabled is planned for a later
DD OS 5.5.x version.
u
If at all possible, when upgrading from DD OS 5.1.x directly to DD OS 5.4, choose
version 5.4.0.4 or higher to avoid a lengthy upgrade process that can result from
numerous unverified containers. Upgrades to versions of DD OS 5.4 preceding
version 5.4.0.4 perform container verification prior to upgrading with some
DD OS Version 5.4.3.0 Upgrade Instructions 75
downtime, while upgrading to version 5.4.0.4 performs the container verification after
the upgrade without any downtime.
u
If you are using NetWorker with VTL, you should take the following steps to mitigate
any data compression loss:
l
Set the NetWorker tape block size on the Media Server to 256 KB. This value is
safe for all operating systems and drivers.
l
Make sure there is at least 10% free space available on the Data Domain system.
l
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.
u
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.
u
system headswap command: The system headswap command restores the
system configuration after a head unit replacement.
Note
The supported path for system controller upgrades to 5.4.x is to upgrade first to 5.1.x
or later and then perform the head swap. The system headswap command can be
used only from DD690, DD690g, DD880, and DD990g systems. Administrative users
only are permitted to invoke this command. For more information on system
headswap, see the documentation for your particular platform, including the
appropriate Field Replacement Unit documents, and sections of the Data Domain
Hardware Guide.
u
In a small number of customer systems, registry parameters may have been
overridden by the SE to tune them for your environment. If you know that your SE has
overridden registry parameters, contact your support provider or visit us online at the
EMC Online Support site before upgrading to 5.4.x, as those parameters may or may
not need to be reset before upgrading.
u
For systems that are already part of a collection replication pair, upgrade the
destination system first, and then upgrade the source system.
u
For a DD OS upgrade, it is not necessary to disable replication on either system in the
pair.
u
An upgrade of the destination Data Domain system from 5.2.x releases to 5.4.x in a
collection replication pair may take an hour or more. The slow upgrade results when
replication to the destination lags significantly or, in some cases, when doing an
upgrade just after a filesys clean operation. The best time to upgrade the
destination is when little data is waiting for replication and before (rather than just
after) a filesys clean operation.
Use the filesys show space command on the source and the destination. If the
value for the Data line in the Use% column is 2% or larger on the destination than on
the source, replication or processing of filesys clean results lags. Assume that
an upgrade on the destination will be slow.
The upgrade process generates a message every 30 seconds while the upgrade is
making progress. However, the messages are seen only from a serial console. Use a
serial console to verify that progress is continuous when doing an upgrade that you
suspect will be slow.
RELEASE NOTES
u
Do not attempt to power down the system while the upgrade process is running.
NOTICE
When upgrading to 5.4.x from a previous release, the CIFS registry keys under
config.cifs.global.raw.* are renamed to
config.windows.global.raw.*. If a key contains two or more consecutive spaces,
then the upgrade process fails to rename this key.
Do the following steps to rename the key manually after upgrading:
Procedure
1. Check if any old key still exists using the reg show config.cifs.global.raw
command.
For example:
# reg show config.cifs.global.raw
config.cifs.global.raw.dd user group1 = chaos\group2
2. Create new key with the same value of the old key using the reg set "newkey"
"value" command.
For example:
# reg set "config.windows.global.raw.dd user group1" "chaos\group2"
Note
If you plan to add a third SAS HBA (Host Bus Adapter) for the new DD880 expanded
capacity feature, upgrade to 5.4 before physically installing the SAS HBA. After the
software upgrade, install the SAS HBA. Be aware that the slot for the HBA is critical
and cannot simply be any open slot.
Upgrading to DD OS Version 5.4.3.0
Before you begin
Prior to upgrading your Data Domain system, be sure to review the upgrade preparations
and considerations described in Preparing to Upgrade to DD OS 5.4 on page 75.
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.
Procedure
1. Download the image for the DD OS 5.4.3.0-436446 from the appropriate EMC
download or support site.
2. Store the file, 5.4.3.0-436446.rpm, in the /ddvar/releases directory on the Data
Domain system.
Do not rename any software upgrade package that you received for your Data Domain
system and its licensed features. Upgrade processes and procedures rely on the
software package names being what they are. Renaming a software upgrade package
will cause the upgrade process to fail.
When downloading a Data Domain system software upgrade image using Internet
Explorer, the browser may add bracket and numeric characters to the upgrade image
name. Remove the added characters before performing the system upgrade.
3. Make sure that the Data Domain system is idle. All replication initialization and re-
synchronization should be complete, and no backups should be running. A useful
Upgrading to DD OS Version 5.4.3.0 77
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 DD System Manager (formerly Enterprise 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.
To upgrade a Data Domain system running release 5.1 or later,
a. Log in to the system where the upgrade is to be performed.
You can select any system from the DD Network device list, but you can upgrade
only the system where you are logged in.
b. Click the name of the host system you are upgrading in the Navigation pane.
c. Click Maintenance > System.
d. From the Upgrade Packages Available on this Data Domain System list, click in the
checkbox of the image to use for the upgrade.
e. Click Perform System Upgrade.
f. The Upgrade System dialog box appears.
g. Verify the version of the target image (the upgrade image) is 5.4.3.0-436446 and
click OK.
A progress dialog box appears and advises that the system will automatically reboot
to complete the upgrade.
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.
8. To upgrade a Data Domain system running release 5.1 or later using the CLI, issue the
command:
system upgrade 5.4.3.0-436446.rpm
Take note of the general effects of upgrading the Data Domain system to DD OS
5.4.3.0 that are described in the previous step.
Results
When upgrading, the following error may display:
[UPGRADE]: Find DDOS rpm at /ddr/var/releases/5.4.3.0-436446.rpm
[UPGRADE]: Check DDOS rpm .........[failed]
[UPGRADE}: DDOS upgrade failed with error!
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.
RELEASE NOTES
Note
With collection replication, no files are visible on the destination if replication was not
finished before starting the upgrade. After the upgrade, wait until replication completes
to see files on the destination.
Troubleshooting and Getting Help
EMC support, product, and licensing information is available for DD OS and other EMC
Data Protection and Availability Division (DPAD) products.
The information can be obtained as follows:
Product Information
For documentation, release notes, software updates, or information about EMC products,
licensing, and service, go to the EMC Online Support site (registration required) at:
https://support.emc.com/
Compatibility Guides
For specific backup software and hardware configurations supported by Data Domain,
visit the EMC Online Support site.
Technical Support
For technical support resources that may enable you to resolve a product issue before
contacting EMC Customer Service, go to:
u
The Avamar Support page at https://support.emc.com/products/759_Avamar-
Server/Documentation/
u
The NetWorker Support page at https://support.emc.com/products/
1095_NetWorker/Documentation/
u
The Data Domain Support page at https://support.emc.com/products/9012_Data-
Domain/Documentation/
The Avamar, NetWorker, and Data Domain Support pages provide access to:
u
Product documentation
u
How-to and troubleshooting information in the Support Topics section
u
Hardware and software compatibility information
u
Knowledge Base articles
If none of these resources resolves the issue, you can engage EMC Customer Service
using live interactive chat by selecting Additional Resources > Live Chat on the Support
pages.
If more in-depth help is required or you have an existing open Service Request (SR), you
can submit or review an SR through the EMC Online Support site at https://
support.emc.com/:
u
To open a new SR, select Support > Request Support > Create Service Request.
u
To open an SR, you must have a valid support agreement. Contact your EMC sales
representative for details about obtaining a valid support agreement or with
questions about your account.
u
To review an existing SR, select Support > Request Support > View Service Request.
Troubleshooting and Getting Help 79
Copyright
2013-2014 EMC Corporation. All rights reserved. Published in USA.

Published July, 2014
EMC 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. EMC Corporation 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 EMC software described in this publication requires an applicable software
license.
EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
RELEASE NOTES

Docu53897 Data Domain Operating System Version 5.4.3.0 Release Notes Directed Availability

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Docu53897 Data Domain Operating System Version 5.4.3.0 Release Notes Directed Availability

Uploaded by

Copyright:

Available Formats

RELEASE NOTES

2013-2014 EMC Corporation. All rights reserved. Published in USA.

You might also like