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

Snapmirror fail

Julien_Mos

Hello,

I need help with a snapmirror that no longer works.
See the status of the command in the attached file.

Apparently the last synchro took place on 24.10.2023 and since then I see that there has been a lot of failed updates. I guess it's related?

I have the impression that it can no longer sync, but I can't work out why.

Last question, is there any way of monitoring these synchronizations?

Let me know if you need more information.

Best

TeamViewer_KbJi5hO0Xh.png

TeamViewer_znlMRCtHGS.png

Find more posts tagged with

Accepted answers

dbenadib

On the screenshots I can see that we are talking about synchronous replication wich is currently healthy.

Would you mind to provide the output of :

cluster peer show

snapmirror show -state unhealthy -fields unhealthy-reason

All comments

Sergey_Osipov

please take a look here

might be applicable

https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/1584155

TzwaynY

Hi,

could you go onto the original Cluster via CLI and execute this command:

snapmirror list-destinations -source-volume SSD1

Would be intereseting to see, how many destinations are listed. Im asking because there is a limit on how many destinations you can fan out from a single volume.

It depends on the Hardware you have and the Ontap you are running aswell.

And you can see there is the relation exists on the source-volume. If not, that could also explain your problem.

And if someone added more destinations then the maximum possible snapmirror relations from the single volume on the 24.10 last year, that could maybe explain that issue you are facing right now.

Best regards

Kai

dbenadib

On the screenshots I can see that we are talking about synchronous replication wich is currently healthy.

Would you mind to provide the output of :

cluster peer show

snapmirror show -state unhealthy -fields unhealthy-reason

dbenadib

Note also that SM Sync is limited in terms of RTT latency .

Can you also share the output of :

network test-path -source-node STOCH6CLU001H1 -destination-cluster STOCH6CLU001 -destination-node STOCH6CLU001H2 -session-type SyncMirrorRemote

Limits for SM Sync are documented here : https://docs.netapp.com/us-en/ontap/data-protection/snapmirror-synchronous-disaster-recovery-basics-concept.html#snapmirror-synchronous-operations-allowed