Behind the Scenes: Episode 166 – SnapMirror Synchronous

Welcome to the Episode 166, part of the continuing series called “Behind the Scenes of the NetApp Tech ONTAP Podcast.”


This week on the podcast, we chat all about SnapMirror Synchronous, including technical details, what to expect for the initial use cases and where it fits into your business needs.


Join us as we welcome Data Protection VP Harish Arora (@IMHarishArora), Technical Director Balaji Ramani (, Principal Enginner Akhil Kaushik (akhil.kaushik@netapp.comand Product Manager Chris Winter ( to discuss! 

Finding the Podcast

You can find this week’s episode here:

Also, if you don’t like using iTunes or SoundCloud, we just added the podcast to Stitcher.

I also recently got asked how to leverage RSS for the podcast. You can do that here:

Our YouTube channel (episodes uploaded sporadically) is here:

5 thoughts on “Behind the Scenes: Episode 166 – SnapMirror Synchronous

  1. Pingback: ONTAP 9.6RC1 is available! | Why Is The Internet Broken?

  2. Around 31:45 Chris Winter says Snapmirror Sync shouldn’t be applied to the same problems as async Snapmirror, that it’s a totally different use case. Can you clarify? Both do basically the same job (replicating data to another site), but one updates periodically and one updates on each I/O. So how do they apply to totally different use cases? I mean obviously you apply SMSync to applications that require zero RPO, but other than that how is it used differently?


    • My understanding is that SMSync gives you an exact replica up to the second, which is useful for applications that need to consume data as soon as it is written in different sites, whereas async is more of a DR replication use case. And with future releases, we’ll see additional functionality added.

      Does that answer your question?


      • Hm. I hadn’t thought about the use case of an “active consumer” at the destination. I’m not really sure that’s applicable, but maybe that’s the kind of “totally different use case” Chris had in mind?

        I thought SMSync was just intended for the standard DR replication use case, but used for RPO=0 cases, when lost data (for changes between async updates) was unacceptable.

        Thanks, Justin! Love your blog, BTW. Lots of fantastic info.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s