ONTAP Discussions

How to convert TDP to XDP SnapMirror?

adnovum
9,620 Views

Hi,

 

We have an old Netapp filer running 8.2.4P4 7-Mode which is the SnapMirror source to two remote locations running ONTAP 9.1 cluster as destination. We have a working SnapMirror type TDP setup running fine for months.

 

Now the source filer shall be migrated to a new cluster system using the 7-Mode transition tool. I've already done this with the two remote Netapp systems.

 

The question is: How do I have to change the SnapMirror relationships properly on the destination filers already running ONTAP 9.1?

- The source vserver and volume must be changed

- The type must be changed from TDP to XDP

- The volumes should have a common snapshot after migration is completed with the 7-Mode transition tool.

 

I have found a description how to change SnapMirror from DP to XDP. Is it the same procedure? 

https://kb.netapp.com/support/s/article/ka31A00000013gCQAQ

 

I assume that the transition SnapMirror is some kinde of special because it doesn't show up on the OnCommand protection config and the volumes can't be moved from one aggregate to another.

5 REPLIES 5

robinpeter
9,528 Views

There is only one type of snapmirror supported btween 7-Mode and Clustered Ontap, that is TDP.

Which is suppose to be used only for transition. if you are using TDP for data protection (DR). its not a "supported" solution by netapp.

Yes, it do work.. but again, it is not supported by NetApp.

 

There is no way to convert a TDP mirror relationship to XDP mirror (between 7 mode and Clustered Ontap)

 

-robin.

adnovum
9,431 Views

Thanks for your answer.

 

I didn't mean a XDP SnapMirror relationship between a 7-mode filer and a C-mode filer. I meant the required migration steps on the SnapMirror destination filers after the source volumes have been moved from an old 7-mode filer to a new C-mode filer using 7-mode transition tool.

 

Regards,

Bernd

adnovum
9,422 Views

This is what I'm trying to do.

 

  • "7filer" is old system running ONTAP 8.2 7-mode
  • "clustera" is new system running ONTAP 9.1. Volumes are being migrated from "7filer" to here with 7-mode transitioning tool.
  • "clusterb" is SnapMirror destionation running ONTAP 9.1 on a remote location 

SnapMirror relationship from old 7-mode system to remote cluster system with type TDP:

 

clusterb::> snapmirror show -destination-path clusterb-vs2:vs2vol

                            Source Path: 7filer:vol
                       Destination Path: clusterb-vs2:vs2vol
                      Relationship Type: TDP
                Relationship Group Type: none
                    SnapMirror Schedule: daily
                 SnapMirror Policy Type: async-mirror
                      SnapMirror Policy: WAN_Mirror
                            Tries Limit: -
                      Throttle (KB/sec): unlimited
                           Mirror State: Snapmirrored
                    Relationship Status: Idle
                File Restore File Count: -
                 File Restore File List: -
                      Transfer Snapshot: -
                      Snapshot Progress: -
                         Total Progress: -
              Network Compression Ratio: -
                    Snapshot Checkpoint: -
                        Newest Snapshot: clusterb-vs2(0537050135)_vs2vol.1507
              Newest Snapshot Timestamp: 05/11 13:45:10
                      Exported Snapshot: clusterb-vs2(0537050135)_vs2vol.1507
            Exported Snapshot Timestamp: 05/11 13:45:10
                                Healthy: true
                       Unhealthy Reason: -
               Constituent Relationship: false
                Destination Volume Node: clusterb-01
                        Relationship ID: 55487ddd-9432-11e6-afa7-00a09896ed75
                   Current Operation ID: -
                          Transfer Type: -
                         Transfer Error: -
                       Current Throttle: -
              Current Transfer Priority: -
                     Last Transfer Type: update
                    Last Transfer Error: -
                     Last Transfer Size: 252KB
Last Transfer Network Compression Ratio: 1:1
                 Last Transfer Duration: 0:0:17
                     Last Transfer From: 7filer:vol
            Last Transfer End Timestamp: 05/11 13:45:17
                  Progress Last Updated: -
                Relationship Capability: 8.2 and above
                               Lag Time: 0:10:31
           Identity Preserve Vserver DR: -
                 Volume MSIDs Preserved: -
           Number of Successful Updates: 1507
               Number of Failed Updates: 0
           Number of Successful Resyncs: 0
               Number of Failed Resyncs: 0
            Number of Successful Breaks: 0
                Number of Failed Breaks: 0
                   Total Transfer Bytes: 634429440
         Total Transfer Time in Seconds: 30344

Break SnapMirror relationship and resync volume from "clustera" after a volume as been copied with 7-mode transition tool.

 

clusterb::> snapmirror break -destination-path clusterb-vs2:vs2vol 
clusterb::> snapmirror delete -destination-path clusterb-vs2:vs2vol

clusterb::> snapmirror resync -destination-path clusterb-vs2:vs2vol -source-cluster clustera -source-vserver clustera-vs7 -source-volume vs7vol -type XDP -policy WAN_Mirror 

This fails with the following error:

 

clusterb::> snapmirror show -destination-path clusterb-vs2:vs2vol 

                            Source Path: clustera-vs7:vs7vol
                       Destination Path: clusterb-vs2:vs2vol
                      Relationship Type: XDP
                Relationship Group Type: none
                    SnapMirror Schedule: -
                 SnapMirror Policy Type: async-mirror
                      SnapMirror Policy: WAN_Mirror
                            Tries Limit: -
                      Throttle (KB/sec): unlimited
                           Mirror State: Broken-off
                    Relationship Status: Idle
                File Restore File Count: -
                 File Restore File List: -
                      Transfer Snapshot: -
                      Snapshot Progress: -
                         Total Progress: -
              Network Compression Ratio: -
                    Snapshot Checkpoint: -
                        Newest Snapshot: clusterb-vs2(0537050135)_vs2vol.1507
              Newest Snapshot Timestamp: 05/11 13:45:10
                      Exported Snapshot: -
            Exported Snapshot Timestamp: -
                                Healthy: false
                       Unhealthy Reason: Transfer failed.
               Constituent Relationship: false
                Destination Volume Node: clusterb-01
                        Relationship ID: f2cbf424-3610-11e7-8ea5-00a09896edcf
                   Current Operation ID: -
                          Transfer Type: -
                         Transfer Error: -
                       Current Throttle: -
              Current Transfer Priority: -
                     Last Transfer Type: resync
                    Last Transfer Error: Cannot restore volume "clusterb-vs2:vs2vol" to Snapshot copy "clusterb-vs2(0537050135)_vs2vol.1507" because it is either 7-Mode, pre-8.2 or has a legacy-style inofile. Such a Snapshot copy is not supported for this operation.
                     Last Transfer Size: -
Last Transfer Network Compression Ratio: -
                 Last Transfer Duration: -
                     Last Transfer From: clustera-vs7:vs7vol
            Last Transfer End Timestamp: -
                  Progress Last Updated: -
                Relationship Capability: 8.2 and above
                               Lag Time: -
           Identity Preserve Vserver DR: -
                 Volume MSIDs Preserved: -
           Number of Successful Updates: 0
               Number of Failed Updates: 0
           Number of Successful Resyncs: 0
               Number of Failed Resyncs: 1
            Number of Successful Breaks: 0
                Number of Failed Breaks: 0
                   Total Transfer Bytes: 0
         Total Transfer Time in Seconds: 0

So how am I going to re-establish SnapMirror from the migrated filer without re-transmitting several terabytes of data over a slow WAN connection around the world that is going to take months? Just because of a legacy style iofile?

 

This is the 7-mode snapshot. Can it be converted to a C-mode snashot somehow?

 

clustera::> volume snapshot show -vserver clustera-vs7 -volume vs7vol -snapshot clusterb-vs2(0537050135)_vs2vol.1507 

                              Vserver: clustera-vs7
                               Volume: vs7vol
                             Snapshot: clusterb-vs2(0537050135)_vs2vol.1507
                        Creation Time: Thu May 11 07:45:10 2017
                        Snapshot Busy: false
                       List of Owners: -
                        Snapshot Size: 156KB
           Percentage of Total Blocks: 0%
            Percentage of Used Blocks: 0%
                              Comment: -
                      7-Mode Snapshot: true
      Label for SnapMirror Operations: -
                       Snapshot State: -
                 Constituent Snapshot: false
                          Expiry Time: -
                 SnapLock Expiry Time: -

Or other ideas?

 

EBIsysadmin
7,910 Views

Sorry to resurrect this but had the same problem, got some help from our partner support.

 

Issue seemed to be for me (ONTAP 9.3GA) that the snapmirror relationship defaulted to XDP even when trying to set DP explicitly, see:

 

https://kb.netapp.com/app/answers/answer_view/a_id/1071159

 

The command mentioned in the KB didn't work but this did:

 

options -vserver <cluster mgt SVM> -option-name replication.create_data_protection_rels.enable -option-value on

 

Once I'd set that on just the target C-mode cluster it all worked and the SM relationship was set to DP rather than XDP so could carry on with the block based snapmirror. Once you've got enough C-mode snapshots and removed the old 7-mode ones you could convert to XDP

 

cheers

 

Z

Aravind
5,993 Views

The command mentioned is of 7 mode . you can run from node shell

Public