topic Re: SnapMirror Resync Scenario in General Discussion

SnapMirror Resync Scenario

nicholsongc — Wed, 04 Jun 2025 11:01:34 GMT

Follow along...

I break a SnapMirror relationship (involving a FlexGroup volume) between SITE "A" (PROD) and SITE "B" (DR) and release the mirror. Note: I do not delete any snapshots from either side

I then create a new relationship between SITE "A" (PROD) and SITE "C" (pre-PROD) and complete the initialization.

The data is then cut-over and SITE "C" is now PROD.

Should I be able to then create a new relationship and RESYNC between SITE "C" (PROD) and SITE "B" (DR)?

Or will I need to re-initialize?

Re: SnapMirror Resync Scenario

Ontapforrum — Sun, 12 Jul 2020 23:20:09 GMT

Hi,

Re-sync will not work. You will need to re-initialize from C to B.

As I understand your plan:
1st : A(PROD) ---------> B (DR) [Both A & B will have common-snapshot for their respective relationship, hence sync & re-sync is possible]

2nd : A(PROD) --------> C (pre-PROD) [Both A & C will have common-snapshot for their respective relationship, hence sync & re-sync is possible]

3rd : C(PROD) --------> B (DR) [No, There is no-common-snapshot between C & B to perform resync/sync] = re-initialize will be needed.

Thanks!

Re: SnapMirror Resync Scenario

nicholsongc — Mon, 13 Jul 2020 11:44:45 GMT

Thank you. And just to expand this for my edification... had the destination at "C" been a cascade from "B" (and not a FlexGroup volume), there-synch would be possible?