Resuming a SnapVault relationship with clustered Data ONTAP
Suggest changes
If you restore using a Snapshot backup other than the latest one, you need to resume the SnapVault relationship so that Snap Creator can continue to run backups.
-
Re-create and resynchronize the SnapVault relationship.
hana::> snapmirror create -source-path hana1a:hana_data -destination-path hana2b:backup_hana_data -type XDP Operation succeeded: snapmirror create the relationship with destination hana2b:backup_hana_data. hana::> snapmirror resync -destination-path hana2b:backup_hana_data -type XDP Warning: All data newer than Snapshot copy sc-backup-daily_20140430121000 on volume hana2b:backup_hana_data will be deleted. Do you want to continue? {y|n}: y [Job 6554] Job is queued: initiate snapmirror resync to destination "hana2b:backup_hana_data". [Job 6554] Job succeeded: SnapMirror Resync Transfer Queued
-
To actually restart the SnapVault transfer, a manual Snapshot copy is required.
hana::> snapshot create -vserver hana1a -volume hana_data -snapshot sv_resync hana::> snapshot modify -vserver hana1a -volume hana_data -snapshot sv_resync -snapmirror-label daily hana::> snapmirror update -destination-path hana2b:backup_hana_data Operation is queued: snapmirror update of destination hana2b:backup_hana_data.
-
Verify that the SnapVault relationship appears in the destination list.
hana::> snapmirror list-destinations -source-path hana1a:hana_data Progress Source Destination Transfer Last Relationship Path Type Path Status Progress Updated Id ----------- ----- ------------ ------- --------- ------------ --------------- hana1a:hana_data XDP hana2b:backup_hana_data Transferring 38.46KB 04/30 18:15:54 9137fb83-cba9-11e3-85d7-123478563412