how to access snapvault snapshot on SVM-DR destination

[FelixZhou]

we have configured SVM snapmirror and will have a need to restore data from snapvault snapshots. Since we used SVM snapmirror, the destination SVM is offline. when we need to access snapvault snapshot, currently we will create a flexclone to a test SVM to access the snapshot. We have many snapshots and not sure where is the data located. is there any way we can access to all snapshots on destination at same time for data browser and search?

thanks in advance

[hmoubara]

Hello @FelixZhou 

Check the below kb:

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_control_access_to_a_Snapshot_directory_in_ONTAP_9

Thanks 

[FelixZhou]

thanks for reply. Actually we are looking for a way to access all snapshots together on the SVM-DR destination when SVM is offline. let us say we have 60 snapshot on SVM snapmirror destination, we don't where is the data located, we know we can Flexclone snapshot by snapshot to search the data. But is there any way to access all snapshots at one shot?

thanks,

[aladd · Accepted solution]

With SVM-DR setup, this won't be feasible because the destination vserver has to be in an offline RO state for the configuration.

in a traditional XDP relationship, you would be able to create a share or mount point on the destination vserver to access the volumes attached to that vserver, in order to access the RO destination volumes.

[FelixZhou]

great idea. this is what i am looking for. i will test it out.

thanks for your sharing.

[ansley_tj]

@FelixZhou, To be able to access the Snapshot copies within the destination SVM of an active SVM-DR relationship you can use -identity-preserve false parameter when you setup your SVM-DR relationship. With this parameter you can start the destination SVM using vserver start <svm-name> command and you should be able to access the R/O DP volumes and their snapshots.

If you want self-service for your users, you will have to do the above and then create a new NAS identity for your users to mount.

Note: this will mean that the source SVM's NAS(NFS/CIFS export policies/shares, etc) and network (IP addresses, etc) configuration information will not be transferred and in the event of a needed failover to the destination, you will have to reconfigure the network settings of the destination SVM to those that were used by the source SVM (or reconfigure your clients...though reconfiguring the destination SVM will probably be simpler and faster 😀)