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; } } }

can snapshots on SVM-DR destination be used to restore data to the source volumes?

FelixZhou

We have SVM snapmirrors in place and do reserve same snapshot copies on destination for each volume. Can these snapshots on destination volumes be used for restoring data back to source volumes?

If not and we do need to keep volume snapvaults on destination, should we set up volume snapmirrors along with SVM snapmirors?

thanks.

Find more posts tagged with

Accepted answers

FelixZhou

good information.

if i understand right, the SVM will be only used for DR purpose. if we have to restore the data from snapshot of volumes from destination to the source, we have to snapmirror it back.

On source, we usually keep short term snapshots for instantly reocvery, and on destination we keep longer term snapshots. if SVM replications will be only used for DR purpose, should we also set up volume snapmirror to destination and keep snapvaults as longer term backup copies for in case any restores will be needed? Since the SVM replication already included the volume replications, will be volume replications duplicated?

thanks.

All comments

aladd

the SVM-DR is designed to continue serving data at the DR location should the source encounter a catastrophic failure sufficient enough to cause an outage.

If you require reverting back to a specific snapshot that exists on both SVMs, then simply restore from a local snapshot.

If you require to revert to a specific snapshot for restoration of the SVM from the destination, you can follow the below process to re-mirror the SVM to the origin (production) and restore from the snapshot locally.

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-dap%2FGUID-636DEBE4-31FB-49BA-931D-10911E6F70C5.html

Mirroring data volumes would be ideal, but that can depend on your need. It would be ideal to mirror data volumes in an SVM-DR configuration to enable the DR site to continue serving data in the above described catastrophic failure example.

FelixZhou

good information.

if i understand right, the SVM will be only used for DR purpose. if we have to restore the data from snapshot of volumes from destination to the source, we have to snapmirror it back.

thanks.

aladd

Hello @FelixZhou ,

I'm not entirely certain I understand the question.

SVM-DR includes the attached volumes to the destination site when created. no need to create the data volume relationships.

Ideally you would never encounter a DR scenario. But, in the event one is encountered, you would bring up the DR site SVM and it's volumes (assuming you have the preserve identity enabled, you would not need to change where clients are pointed).

You can reactivate the prod site through the following process. (reversing the mirror)

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-dap%2FGUID-EEB69177-FAFE-41C8-9FD9-5AB4665D3982.html&cp=8_3_3_6_2

FelixZhou

I mean without break or pause the SVM snapmirror relationship. can we perform any volume level restore from destination snapshot to source? thanks.