NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform.
You will still be able to view content, but posting and replying will be temporarily disabled.
To learn more, please review the information in this blog post.

Data Protection

ONTAP 9 Modifying SnapVault Source Volume without baseline transfer

tyrone_owen_1
4,917 Views

Hi,

 

In 7-mode you could modify the SV source volume without incurring a full baseline transfer: https://kb.netapp.com/app/answers/answer_view/a_id/1034855/~/how-to-move-a-snapvault-or-snapmirror-primary-from-one-volume-to-another

 

Has anyone completed this activity in ONTAP 9.3+?

 

Cheers

1 ACCEPTED SOLUTION

tyrone_owen_1
4,685 Views

Thanks for the reply.

 

The process for SnapVault is slightly different to the one in the article:

 

  • Update SnapVault between A -> C
  • Break SnapVault between A -> C (stop further updates)
  • Update the SnapMirror relationships A -> B (transferring the SV baseline snap)
  • Break the snapmirror relationship between A -> B
  • Delete the SV relationship between A -> C (you don't seem to be able to set up a second SV relationship on the destination vol)
  • Create the SV relationship between B -> C 
  • Resync the SV relationship between B -> C 

Cheers

View solution in original post

2 REPLIES 2

GidonMarcus
4,871 Views

Hi

 

the correct article for Cdot is in:

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

 

 

 

Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK

tyrone_owen_1
4,686 Views

Thanks for the reply.

 

The process for SnapVault is slightly different to the one in the article:

 

  • Update SnapVault between A -> C
  • Break SnapVault between A -> C (stop further updates)
  • Update the SnapMirror relationships A -> B (transferring the SV baseline snap)
  • Break the snapmirror relationship between A -> B
  • Delete the SV relationship between A -> C (you don't seem to be able to set up a second SV relationship on the destination vol)
  • Create the SV relationship between B -> C 
  • Resync the SV relationship between B -> C 

Cheers

Public