ONTAP Discussions

Moving primary volume while DR/Secondary stayed on same array

CAPATEL_NET1984
1,576 Views

we are moving our primary volume from one site to another site but our secondary/DR site is staying same and DR volumes will be stayed same as well.

when we move to our newer site can we setup snapmirror from our new site so same DR site and to same volumes? will that be a full sync/new sync or it will be just delta copies? 

 

1 ACCEPTED SOLUTION

hmoubara
1,496 Views

Hello 

 

Thanks for the clarification. With snapmirror you should be able to perform a snapmirror resync to be able to resync from B to a common snapshot on A1. This should be your steps:

 

Update A -> B relationship (from B)
Break A -> B relationship (from B)
Release with relationship info only true on A so the snapshots stay for the resync later.
Create new snapmirror A -> A1 and initialize.
After transfer is done and it is idle you can break it and release with only relationship info again.
At this point you should have a matching snapshot you can use on A1 to do a resync from B.
 

Below is some documentation about snapmirror resync:

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-cmpr-940%2Fsnapmirror__resync.html

 

 

Thanks

View solution in original post

4 REPLIES 4

hmoubara
1,538 Views

Hello,

 

Are you moving the source volume within the same cluster or to a different cluster?

How are you planning to move the volume?

 

Here is a documentation about moving a source snapmirror volume:

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.exp-vol-move%2FGUID-10F57AAF-77B4-43BF-B8D3-B35AC36315AF.html

CAPATEL_NET1984
1,514 Views

Hi, we are not using "Volume move" technology

current setup site A--> site B via snapmirror

new setup is site A is going away

site A--> site A1 we will do snapmirror

final setup will be site A1--> site B

 

in this case , can we use the same DR target volumes at site B?

if we use same volumes, will it be incremental or a full copy?

hmoubara
1,497 Views

Hello 

 

Thanks for the clarification. With snapmirror you should be able to perform a snapmirror resync to be able to resync from B to a common snapshot on A1. This should be your steps:

 

Update A -> B relationship (from B)
Break A -> B relationship (from B)
Release with relationship info only true on A so the snapshots stay for the resync later.
Create new snapmirror A -> A1 and initialize.
After transfer is done and it is idle you can break it and release with only relationship info again.
At this point you should have a matching snapshot you can use on A1 to do a resync from B.
 

Below is some documentation about snapmirror resync:

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-cmpr-940%2Fsnapmirror__resync.html

 

 

Thanks

Alireza_D
343 Views

I have the same question but in our case we also trying to move the DR (site B) volumes into a new cluster too so :

 

Site A (Primary) should move to new cluster

Site B (DR) should also move to new cluster 

 

What's the best way to resync the volumes after the move so we can just update the Delta instead of new snapmirror relationship since we talk about a lot of data , and off course with min downtime. 

Public