The behavior that you are seeing is expected.
For snapmirror replication, the entire transfer needs to complete before the data can be seen on the destination filer.
The high level steps for a SnapMirror transfer are:
1. The source storage system creates a Snapshot copy.
2. The new copy is compared to the baseline copy to determine which blocks have changed.
3. The changed blocks are sent to the destination and written to the file system.
4. After the update is complete, both file systems have the new Snapshot copy, which becomes the baseline copy for the next update.
In your case, step 3 was unable to complete due to the link break. In most cases, we would generate a restart checkpoint. Once the network link is re-established, the snapmirror transfer would start back from the restart checkpoint.