#SVM-DR adding a new volume - how will it behave

1 messages · Page 1 of 1 (latest)

waxen aurora
#

I have a question about SnapMirror. I have an SVM-DR with 10 volumes, and synchronization runs every hour. I’m adding a new 100TB volume and setting it as protected. The initialization will take 5 days.

Will the other volumes stop synchronizing until the new volume is fully initialized? As far as I remember, the scheduled update will fail, but will the error be caused by skipping one volume due to initialization or by all volumes?

In other words, will the RPO of existing volumes be affected if one volume is initializing for several days?

#

SVM-DR adding a new volume - how will it behave

raven yarrow
#

I have done this exact thing, and yes, the next snapmirror schedules will get delayed. You will be out of compliance until they finish. This was at least true with 9.12. I do not know if there is a way to get around this.

outer coral
#

yeah you should always try to add volumes to the SVM DR while they're new and mostly empty, and only fill them with data afterwards, to avoid that scenario

raven yarrow
#

^^^^^ This!

waxen aurora
#

@outer coral @raven yarrow thanks
Our issue is that the volume hit 100TB, forcing us to delete snapshots on the source, which corrupted the SVM-DR. Now we need to reinitialize the volume without affecting ~70 other volumes.

One idea is to use VSM fan-out to a new SVM on DR, rehost it to the DR SVM, and then convert VSM to SVM-DR.

balmy salmon
#

What version of ONTAP?
9.12.1P2 and higher supports 300T volumes

waxen aurora
#

@balmy salmon Unfortunately, 9.11.1.P16