Skip to main content
NetApp Knowledge Base

Is it possible to convert an XDP relationship to a DP relationship in ONTAP?

Views:
1,946
Visibility:
Public
Votes:
2
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror

Answer

No, converting an XDP relationship to a DP relationship is not a supported process

Additional Information

Why can't I convert it?
  • Type DP uses BRE (Block Replication Engine) which tracks each block and is unaware of the file system structure
    • BRE reads blocks from the source aggregate.
    • It then sends the data over the network to the destination aggregate.
    • Lastly, it writes the to the destination aggregate.
  • Type XDP uses is LRE/LRSE (Logical Replication Engine / Logical Replication engine with Storage Efficiency). 
    • LRSE tracks the data logically based on the file system structure.
    • XDP transfers do logical writes which are within the flexvol.
  • The engine that -type XDP mirrors, SnapVault, and version-independent SnapMirror, use is LRE/LRSE (Logical Replication Engine / Logical Replication engine with Storage Efficiency). 
    • LRSE tracks the data logically based on the file system structure.
    • XDP transfers do logical writes which are within the flexvol.
  • So when the resync is attempted, BRE cannot find any snapshots that hold block-based references to the data so it reports that there are no common snapshots since the block-based engine cannot understand the logical tracking.
Common issues after attempting to convert
  • Resync back to the source (after converting from XDP to DP) will fail with the following error message

No common Snapshot copy found between <source> <destination>

  • Running snapmirror show command (after converting from XDP to DP) will fail with the following error message

cluster_82b::> snapmirror update -destination-path vs2:vs2_sv_dest Operation is queued: snapmirror update of destination vs2:vs2_sv_dest
cluster_82b::> snapmirror show -destination-path vs2:vs2_sv_dest

Source Path: vs1_test:compress_test
Destination Path: vs2:vs2_sv_dest
Relationship Type: DP
SnapMirror Schedule: -
Tries Limit: -
Throttle (KB/sec): unlimited
Mirror State: Snapmirrored
Relationship Status: Idle
Transfer Snapshot: -
Snapshot Progress: -
Total Progress: -
Snapshot Checkpoint: -
Newest Snapshot: 5min.2015-05-04_0830
Newest Snapshot Timestamp: 05/04 08:32:57
Exported Snapshot: 5min.2015-05-04_0830 Exported Snapshot Timestamp: 05/04 08:32:57
Healthy: false
Unhealthy Reason: Transfer failed.
Constituent Relationship: false
Destination Volume Node: cluster-01
Relationship ID: 003d8e96-f25a-11e4-bbdf-123478563412
Transfer Type: -
Transfer Error: -
Current Throttle: -
Current Transfer Priority: -
Last Transfer Type: update
Last Transfer Error: Destination was previously used as the destination of an XDP relationship. Using an XDP destination volume as the destination volume for a DP relationship is not supported.
Last Transfer Size: -
Last Transfer Duration: -
Last Transfer From: vs1_test:compress_test Last Transfer End Timestamp: 05/04 08:41:14
Progress Last Updated: -
Relationship Capability: 8.2 and above
Lag Time: 0:8:20
SnapMirror Policy: DPDefault

  • A DP relationship that is converted to an XDP relationship can be converted back to a DP relationship, IF the source and destination volumes still have Snapshots with the same instance and version UUIDs.
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.