nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

snapmiror auto resize

nadavassa

Hello,

We have volumes with XDP snapmiror relationship. (ontap 9.3)

when we resize the source volume we should resize also the destination volume?

also, what is the differences between XDP to DP?

Thank you for your help

Find more posts tagged with

Accepted answers

christsai

Hi @nadavassa

I think your snapmirror type is XDP.

1.If the SnapMirror relationship is a "type-DP":
Modify the desired value (size, max inodes, etc.) on the source volume. After a SnapMirror Update\Resync operation from the destination, the value will be reflected on the destination volume as well.

2.If the SnapMirror relationship is a "type-XDP":

By default, a type-XDP destination volume may not match the source volume total size, but will auto-grow and auto-shrink as-needed based on total used space. This is controlled via the autosize-mode of the destination volume which is set to grow_shrink by default. For more information see volume autosize command in the manual pages. You can still increase the destination volume manually through the vol size command, if desired.

https://kb.netapp.com/app/answers/answer_view/a_id/1073852/loc/en_US

All comments

christsai

Hi @nadavassa

when we resize the source volume we should resize also the destination volume?

During a data protection mirror transfer, the destination volume grows automatically in size if the
source volume has grown, provided there is available space in the aggregate that contains the volume.

also, what is the differences between XDP to DP?

Starting with ONTAP 9.3, SnapMirror extended data protection (XDP) mode replaces SnapMirror
data protection (DP) mode as the SnapMirror default.

Until ONTAP 9.3, SnapMirror invoked in DP mode and SnapMirror invoked in XDP mode used
different replication engines, with different approaches to version-dependence.

• SnapMirror invoked in DP mode used a version-dependent replication engine in which the
ONTAP version was required to be the same on primary and secondary storage.

• SnapMirror invoked in XDP mode used a version-flexible replication engine that supported
different ONTAP versions on primary and secondary storage.

https://library.netapp.com/ecm/ecm_get_file/ECMLP2811525

nadavassa

Hello,

Thank you for your reply, but I didn't properly understand the auto grow concept.

We have XDP snapmiror relationship between 2 volumes. after resizing the source vol (manually) the des vol didn't grow automatically (many snapmiror reps/updates occur).

we have enough space in the aggr.

so what is the reason for this situation?

Thanks

christsai

Hi @nadavassa

I think your snapmirror type is XDP.

2.If the SnapMirror relationship is a "type-XDP":

https://kb.netapp.com/app/answers/answer_view/a_id/1073852/loc/en_US

nadavassa

Thank you for your help!