topic cDOT snapmirror resync and sc issue in Data Protection https://community.netapp.com/t5/Data-Protection/cDOT-snapmirror-resync-and-sc-issue/m-p/23997#M984 <HTML><HEAD></HEAD><BODY><P>[Submitting on behalf of Tobias.]</P><P>Hi SC experts!</P><P></P><P>I have an issue with my SC (4.1P1) setup. I’m using the SAP HANA plugin, but that’s not relevant for the problem, I think. Here’s where I’m facing problems:</P><UL style="list-style-type: disc;"><LI>- My setup is based on cDOT (8.2 P6) / Linux / NFS</LI><LI>- I have a config where I take backups of primary volumes (wdflabvs07_fp_infra:/schana_data). </LI><LI>- The volumes are protected using snapmirror type XDP (snapvault) – the SC plugin triggers the update during a backup run (wdflabvs07_fp_infra:/schana_data -&gt; wdflabvs10_fp_backup_t002:/sv_infr_schana_data)</LI><LI>- Everything is running fine up to here</LI><LI>- Then I would like to restore a primary snapshot which is older than the base snapshot for the snapmirror relationship</LI><LI>- In order to do that, I’m quiescing and deleting the snapmirror relationship to release the base snapshot</LI><LI>- Then I restore the (older) primary snapshot</LI><LI>- Now I would like to recreate the snapmirror relationship again (to continue protection of backups) – without a complete baseline transfer.</LI><LI>- I’m creating the snapmirror relationship again with type XDP, then I resync the destination.</LI><LI>- In system manager and on the cluster console, everything looks fine: the most recent common snapshot on primary is tagged “snapmirror” and the connection shows up.</LI><LI>- Now in SC, when I run the next backup, it fails, stating that the SnapVault relationship is missing:</LI><LI></LI><LI><IMG src="http://community.netapp.com/legacyfs/online/25595_logs.png" width="1013" /></LI></UL><P></P><P></P><P>I already had a look into that and we could verify that SC is not able to find the relationship anymore. Nevertheless, </P><UL style="list-style-type: disc;"><LI>- I don’t understand why this is happening and</LI><LI>- How should the correct procedure look like resync the relationship in such a scenario?</LI></UL><P></P><P>Any help would be highly appreciated.</P><P></P><P>Kapil</P></BODY></HTML> Thu, 05 Jun 2025 05:37:08 GMT Arora_Kapil 2025-06-05T05:37:08Z cDOT snapmirror resync and sc issue https://community.netapp.com/t5/Data-Protection/cDOT-snapmirror-resync-and-sc-issue/m-p/23997#M984 <HTML><HEAD></HEAD><BODY><P>[Submitting on behalf of Tobias.]</P><P>Hi SC experts!</P><P></P><P>I have an issue with my SC (4.1P1) setup. I’m using the SAP HANA plugin, but that’s not relevant for the problem, I think. Here’s where I’m facing problems:</P><UL style="list-style-type: disc;"><LI>- My setup is based on cDOT (8.2 P6) / Linux / NFS</LI><LI>- I have a config where I take backups of primary volumes (wdflabvs07_fp_infra:/schana_data). </LI><LI>- The volumes are protected using snapmirror type XDP (snapvault) – the SC plugin triggers the update during a backup run (wdflabvs07_fp_infra:/schana_data -&gt; wdflabvs10_fp_backup_t002:/sv_infr_schana_data)</LI><LI>- Everything is running fine up to here</LI><LI>- Then I would like to restore a primary snapshot which is older than the base snapshot for the snapmirror relationship</LI><LI>- In order to do that, I’m quiescing and deleting the snapmirror relationship to release the base snapshot</LI><LI>- Then I restore the (older) primary snapshot</LI><LI>- Now I would like to recreate the snapmirror relationship again (to continue protection of backups) – without a complete baseline transfer.</LI><LI>- I’m creating the snapmirror relationship again with type XDP, then I resync the destination.</LI><LI>- In system manager and on the cluster console, everything looks fine: the most recent common snapshot on primary is tagged “snapmirror” and the connection shows up.</LI><LI>- Now in SC, when I run the next backup, it fails, stating that the SnapVault relationship is missing:</LI><LI></LI><LI><IMG src="http://community.netapp.com/legacyfs/online/25595_logs.png" width="1013" /></LI></UL><P></P><P></P><P>I already had a look into that and we could verify that SC is not able to find the relationship anymore. Nevertheless, </P><UL style="list-style-type: disc;"><LI>- I don’t understand why this is happening and</LI><LI>- How should the correct procedure look like resync the relationship in such a scenario?</LI></UL><P></P><P>Any help would be highly appreciated.</P><P></P><P>Kapil</P></BODY></HTML> Thu, 05 Jun 2025 05:37:08 GMT https://community.netapp.com/t5/Data-Protection/cDOT-snapmirror-resync-and-sc-issue/m-p/23997#M984 Arora_Kapil 2025-06-05T05:37:08Z Re: cDOT snapmirror resync and sc issue https://community.netapp.com/t5/Data-Protection/cDOT-snapmirror-resync-and-sc-issue/m-p/24004#M985 <HTML><HEAD></HEAD><BODY><P>We figured out a workaround/solution to this problem.</P><P>Resync is not enough, we must create a new snapshot on primayry and do a SnapMirror update using the appropriate SnapMirror lable before we start regular backups through Snap Creator.</P><P>Thanks,</P><P>kapil</P></BODY></HTML> Tue, 29 Apr 2014 07:39:13 GMT https://community.netapp.com/t5/Data-Protection/cDOT-snapmirror-resync-and-sc-issue/m-p/24004#M985 Arora_Kapil 2014-04-29T07:39:13Z