@Julien_Mos
SM-S is designed, like all "synchronous" replication solutions, to ensure that data written to the primary site is replicated on the secondary site before acknowledging the IO back to the application, SM-S can operate in a less strict mode of operation. SM-S can use a policy type of either "Sync" or "Strict-sync". The former will not block application IO for short-term periods of "out-of-sync" conditions; while the latter will return an IO failure if the secondary site ack is not received in the designed timeframe.
Regardless of operational mode, the expectation is that both sites will acknowledge the IO..."sync" mode simply provides some leeway in the secondary site ack.
For details, please review the online documentation
Thanks
Tony Ansley
I am a NetApp employee.