Symptoms

Observed Symptoms Vault Data Domain reaches full condition (capacity utilization >90 %).Poor deduplication or compression performance.Networker expiration jobs do not run, causing saveset buildup.Avamar checkpoints or old recovery points remain, consuming space.Data mismatch between primary and disaster‑recovery environments.DDFS panic or other DD functionality failures.Replication between source DD and CR vault DD is out of sync. Caution: High utilization can lead to backup failures and service disruption.

Cause

Primary Causes Vault Data Domain reaches full condition because the data‑protect environment is not kept stable and capacity is not properly managed. Capacity Planning and Growth Monitoring Gaps Customers allow DD utilization to exceed 90 % or reach 100 % before taking action, resulting in rapid fill‑up. Insufficient health‑check on capacity utilization and growth trends.Failure to identify abnormal growth patterns early. Configuration and Operational Issues Improper configuration of Networker, Avamar, and Cyber Recovery components leads to unnecessary data accumulation. Networker volumes not set to appendable and “scan not needed” state.Recyclable savesets are not processed promptly.Backup strategies do not segregate types into separate storage‑units with clear retention.Pre‑encryption or pre‑compression is enabled, increasing data size on DD.Oracle mtrees are not configured with app‑optimized‑compression (oracle1), reducing deduplication efficiency.Avamar expiration/retention settings are not aligned with customer requirements, causing stale checkpoints.Old snapshots and stale data are retained on DD beyond retention policies.Excessive number of Cyber Recovery copies are kept in the vault DD. Maintenance and Housekeeping Deficiencies Lack of regular cleaning and verification activities allows data locality to degrade and capacity to fill unnoticed. Weekly cleaning of DD is not performed.Health‑checks on DD capacity and growth are not executed by the customer.Replication health for Cyber Recovery is not regularly verified.

Resolution

Resolution Steps 1: Verify overall environment stability before performing any backup or replication activity. 2: Networker Check connectivity with Data Domain after each activity.Confirm Networker devices are in a mounted state.Ensure volumes are in appendable and “scan not needed” state.Validate that Networker expiration jobs are functioning.Check for recyclable savesets; if they accumulate, take action immediately.Run the command to process recyclable savesets. nsrim -X Configure backup strategy so that each backup type uses a different storage unit with a clear retention period.Ensure no backups are sent with pre‑encryption or pre‑compression.Ask Data Domain team to set oracle1 as app‑optimized‑compression for Oracle mtrees/STU only. 3: Avamar Verify Avamar expiration/retention matches customer requirements.Verify Avamar maintenance jobs are running successfully.Verify old checkpoints expire according to the Avamar maintenance cycle.Check for older Avamar recovery checkpoints on Data Domain mtree and expire them manually if present. 4: Data Domain (DD) Perform health check on capacity utilization and growth.Highlight abnormal growth immediately.Do not wait for utilization to exceed 90 % or reach 100 %.Check for old or stale snapshots on any mtree.Verify Oracle mtree has app‑optimized‑compression set to oracle1.Confirm older data on Data Domain is within backup retention (review daily AutoSupport emails).Keep a limited number of Cyber Recovery copies in the vault to control utilization.Run cleaning once a week to maintain good data locality. 5: Cyber Recovery (CR) If the CR vault reaches full, reduce the number of CR copies and remove old copies.Ensure replication is in sync and CR functions correctly.Verify sync time and mtree pre‑compression size between source and vault.Focus on source Data Domain capacity; the vault will reflect changes automatically.Consider upgrading Data Domain capacity only after all other measures are applied. Implementation Recommendations Deploy: Size storage based on environment and retention; consider backup types and cloning requirements. Install: Install DPD components with redundancyDisable encryption and compression before sending data to Data Domain.Place different backup types on separate mtreesEnable oracle1 parameters for Oracle data; maintain proper file‑directory ratio. Production: Keep environment stable.Segregate backup types and windows.Run cleaning on Data Domain once or twice a week.Monitor backup progress and capacity utilization regularly. When to engage support: Poor deduplication/compression – contact DD and Networker support. Networker expiration not occurring – contact Networker support.Data mismatch between production and DR – contact Cyber Recovery support.DDFS panic or any functionality loss – contact DD support.Capacity utilization over 90 % – contact DD, Networker, and Cyber Recovery support.Replication issues – contact Cyber Recovery or DD support.

Support Cases