Subscribe

Does dp volume type need re-sizing based on source ?

Scenario:

A snapmirror relationship is establised between a cDOT 8.2 source and destination volume across cluster1:SVM1:vol1 and cluster2:SVM2:vol1_mirror respectively.

 

Question:

When vol1 is resized, say grown up or down, does user need to take care of destination volume vol1_mirror size appropriately ?

Or Data ontap takes care of it vol1_mirror dp volume ?

 

Premise:

In the 7Mode world, when primary volume is grown, snapmirror destination volume needs to be manually resized, equal to or greater than source.

Other wise, the next update would fail with error, destination volume size smaller than source.

 

Regards

adai

Re: Does dp volume type need re-sizing based on source ?

I believe in 8.2 , automatic volume resizing on the DR side was implemented,

Re: Does dp volume type need re-sizing based on source ?

I vaugely remembered so, but couldnt find any documentation on the same.

 

Regards

adai

Re: Does dp volume type need re-sizing based on source ?

If you still need a answer and link to the guide:

 

When a destination volume grows automatically 

During a data protection mirror transfer, the destination volume grows to ensure the success of the transfer. At the start of a data protection mirror transfer, the destination volume grows in size if the source volume has grown. This occurs irrespective of any automatic growth setting on the destination volume. The automatic growth of the destination volume occurs as long as there is available space in the aggregate that contains the destination volume. You cannot prevent Data ONTAP from growing or limiting it growth.

 

It is written in the Data Protection Guide of cDOT 8.2:

https://library.netapp.com/ecm/ecm_download_file/ECMP1196819