Data Domain

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Data Center Infrastructure products. Dell carefully evaluates and monitors code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.

Network File System (NFS) allows a system to share directories and files with others over a network. This article is helpful in verifying whether an NFS export is configured correctly; NFS configuration, mount options, and client configuration. Mounting and Verifying Exports on the NFS Client.

HA pair with Retention Lock Compliance Enabled shows degraded status with SMS mirroring failing; logs contain iDRAC HTTP 500 “Failed to fetch iDRAC users, unable to update privilege”. The cause is an iDRAC stability issue that prevents user enumeration, leading HA to mark SMS as failed.

Both Data Domain (DD) (physical and virtual) and PowerProtect DD Management Center (DDMC) installs come with a REST service embedded. Customers may use it to build their own applications to interact with the DDs and DDMCs.

This article describes a condition where the Data Domain filesystem fails to start due to a potential Non-Volatile Random Access Memory (NVRAM) mismatch. It also provides a validated workaround to restore filesystem availability.

After upgrading to DDOS 8.5 or later, SupportAssist configuration may fail with the error "Unable to load JSON parser".

The primary focus for this article is to troubleshoot an interface down, multiple interfaces down, an intermittent interface, and a bad network card. Replacing parts should be the last step in resolving interface down issues. Troubleshooting these issues first such as reviewing the switch side, may lead to the quickest resolution.

Data Domain system gives a pre-check alert for licenses going deprecated.

The User's account is locked.

This article shows how to reset the DD3300 iDRAC password remotely with a bash command.

This article provides instructions on: Verifying Mode=Active Directory Joining a Data Domain system to a Windows Domain Verifying that DNS is configured properly.

STIG Compliance – STIG Requirement SV-279028r1138077: This requirement states that information transfer mechanisms must uniquely identify and authenticate source systems before permitting data access. To align with this requirement, DD Boost global-authentication-mode and global-encryption-strength should not be configured as none. Configure DD Boost to use two-way or two-way-password authentication and medium or high encryption strength, and verify that connected DD Boost clients such as PPDM support the selected settings.

Following a DD OS upgrade and reboot, certain network interfaces may not initialize successfully, resulting in missing routing rules and network connectivity issues. This behavior has been observed on systems using Intel E810 network adapters with Direct Attach (DA) cables and is resolved in DD OS 8.3.1.40 and later releases.

A BoostFS mount operation may create the /tmp/Boost_D4_Event.log file due to initialization of integrated DDBoost D4 libraries. On affected releases, the file may be created with world-writable permissions; this behavior has been corrected in later BoostFS releases that apply more restrictive permissions and automatically update existing files during installation or upgrade.

A Data Domain ASUP may report "ERROR: MSG-NFS-00005: Failed to do a filecopy, err = 2." This article explains what this error reports and how to address it.

This article provides estimates on scheduling lead time when booking Remote Proactive Services (RPS) upgrades.

This article expands on Active Directory integration for Dell Data Domain systems by providing commonly used CLI commands for domain joins, OU placement, authentication configuration, domain verification, access management, CIFS share considerations, and advanced troubleshooting. It serves as a command-reference companion to the primary Active Directory guide and includes examples and best practices for validating and maintaining Active Directory connectivity.

Network interfaces may go down, become intermittent, or fail to recover properly following events such as node reboots, HA failovers, link renegotiation, or other network transitions on systems equipped with Intel NICs. This issue can occur when the Intel workaround for M14MK dual-rate transceivers remains configured after the interfaces have been migrated to W4GPP 25Gb transceivers. The resulting speed mismatch can cause interface connectivity loss and intermittent network behavior.

This article describes the conditions that trigger the 'NVRAMHardwareFailure' alert on Data Domain systems and outlines the required resolution steps.

This article provides a structured troubleshooting workflow, event-specific remediation guidance, and the most likely resolution for SDPM (NVRAM) events.

This article describes how to sanitize and reconfigure Software Defined Persistent Memory (SDPM) settings in the BIOS and verify successful initialization after the system returns to DDOS.

If the license is in the old format when upgrading a Data Domain controller to a new model, it fails on newer DDOS codes.

MTree replication resync can fail with error "MREPL ASSOC failed: Dest MTree is WORM, source requests removal of WORM (5312)" when the source and destination MTrees have mismatched Retention Lock states. Resync operations are only supported when both MTrees have matching Data Domain Retention Lock Governance or Compliance settings.

This KB article outlines comprehensive guidelines for preparing a Data Domain High Availability (DDHA) system upgrade. Adhering to these instructions guarantees a successful upgrade experience.

Attempting to add a second disk pack to the active tier returns an error stating a partial shelf must be fully used first. The failure is caused by an insufficient capacity license that leaves the initial shelf only partially consumed.

A VLAN interface became inaccessible after a reboot because an invalid MTU configuration was rejected during initial configuration but still persisted in the registry, causing the interface to fail when the system later attempted to apply the invalid MTU during interface initialization.

Replacing, reimaging, or changing credentials on a Data Domain causes PowerProtect Data Manager agent backups to fail. Errors such as ABA0002, ABA0008, ABF0005, ABG0004, or PKIX (Public-Key Infrastructure (X.509)) path building failed due to stale credentials, mismatched storage units, and certificate validation issues.

KB explains a possible reason why an on-premise DDVE running off VMware may be seen to reboot every few minutes with leaving no traces or logs in the DDOS

This article provides detailed steps on how to install Data Domain Boost for NetBackup/BackupExec on a media server.

The "autosupport send" command fails with an error on Data Domain High Availability (DDHA) when ConnectEMC is not enabled or not running.