Symptoms

These steps apply to systems configured with basic one‑way replication (source → destination).However, environments may include more complex configurations such as: Bidirectional replicationChained replication across multiple systems When an MTree replication context is broken, the partner system must also have the matching context broken. ⚠️Warning: Before proceeding, understand the differences between replication Resync and Initialization.

Cause

An MTree resync may be required for several reasons, including: Cleaning not recovering disk space.MTree replication lag exceeding retention requirements.Replication panic associated with FastcopyAutoSupport alert: "Cannot recover from NVRAM: Recently written data may be lost."

Resolution

Important Notes ⚠️Note: Do not disable unrelated replication contexts. These recover automatically when the filesystem is re‑enabled. ⚠️Note: If the intention is to perform an initialization instead of a resync, delete the replicated MTree on the destination or rename the destination path after breaking the context. Option 1: Resync using System Manager (Web-UI) - *Recommended *Recommended, as it simplifies the procedure, is more efficient and avoids typos due to manual path entry. Break the existing replication context Open Enterprise Manager for the source system.Select Replication.Choose the replication context to break.Click Delete Pair.Confirm by clicking OK. This removes the replication context from both systems. Start the resync In the same Replication tab, click More → Start Resync.Select MTree Replication as the replication type.Select the source and destination systems.Specify the MTree path on both systems.Click OK to begin the resync. Resync duration varies from hours to days depending on system size and load. Option 2: Resync using Command-Line (SSH/DD-CLI) Save the current replication configuration Run on both source and destination: replication show config Copy the output into a text editor for reference when rebuilding contexts. Break replication on the source system Break a single context: replication break rctx://<context-number> Break all contexts (only when required): replication break context all Break related contexts on the destination system If the destination has only one partner, repeat the same steps as the source.If the destination has multiple replication partners, break only the shared contexts: replication break rctx://<context-number> Re-create the replication contexts Using the saved configuration, re-create the MTree contexts on both systems: replication add source mtree://<source-host>/<source-path> \ destination mtree://<dest-host>/<destination-path> Example: replication add source mtree://test.datadomain.com/data/col1/weekly \ destination mtree://test2.datadomain.com/data/col1/weeklytest Start the resync (source system only) replication resync rctx://<context-number> Note: The context number may differ from the original if lower numbers were available. Monitor resync progressreplication watch rctx://<context-number>

Support Cases