Data Domain: Retention Lock Compliance Configuration Issue on HA Standby Node

Summary: When Retention Lock Compliance (RLC) is configured on a Data Domain system, the active node reboots while the standby node remains unchanged, causing a High Availability (HA) error on the standby node. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Setting up Retention Lock requires the Data Domain system to be restarted to take full effect.

When Retention Lock is configured on a Data Domain HA cluster, the active node is restarted, but not the standby node. The result is that the HA system is half-configured for Retention Lock.

Cause

Setting up retention lock compliance requires a reboot, but in HA systems this does not occur by default on both nodes.

Resolution

The solution is to reboot the Data Domain HA node that was not rebooted during the initial configuration of Data Domain Retention Lock.
 
To avoid this issue, use the steps below when configuring Retention Lock on a Data Domain HA system:
  1. Run the following command from the active node to configure Retention Lock Compliance (RLC). This causes the active node to reboot: 
    # system retention-lock compliance configure
  2. Wait for the HA configuration to come online after the reboot. Run the following command on either node to check the HA state: 
    # ha status

    For example: 
    sysadmin@dd-ha-p1(active:1)# ha status
HA System name:       dd-ha.example.com
HA System status:     highly available
Node Name                       Node id   Role      HA State
-----------------------------   -------   -------   --------
dd-ha-p1.example.com            1         active    online
dd-ha-p0.example.com            0         standby   online
-----------------------------   -------   -------   --------
  3. Issue the failover command on the newly active node. The failover triggers a reboot, which is required to complete the RLC configuration on both nodes. 
    # ha failover
  4. Wait for the HA configuration to come online after the reboot. Run the following command on either node to check the HA status: 
    # ha status
  5. Issue the following command from the newly active node to finalize enabling RLC: 
    # system retention-lock compliance enable
  6. The RLC status should now report as enabled from both nodes: 
    # system retention-lock compliance status
 
This process may incur downtime for ongoing backups, so customers enabling RLC on a Data Domain HA system must plan for this in advance.

Affected Products

Data Domain

Products

Data Domain
Article Properties
Article Number: 000052574
Article Type: Solution
Last Modified: 23 نيسان 2026
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.