There is no inherent synchronization between the two schedules. I think, if two snapshots are attempted at exactly the same second, one of them may fail. T is always better to schedule so that they do not overlap.
So snapmirror snapshots are generated 'on request', since it's pull based. The destination asks for an update from the source. I'm not sure if you're talking about snapshots on the destination (only with qtree snapmirror) or on the source. I would guess that the 'local' snapshot will occur first given that the destiantion has to ask for a snapmirror update and that would add a little latency to the operation. Now would I guarantee it'll always happen that way? Nope 😉
Thanks for your reply.. just would like to clear the concept. since the snapmirror snapshots are created on request and if the on the same time the normal snapshots are scheduled to create. does it mean the normal snapshot will be created first and the same will be replicated using snapmirror. its a bit confusing for me but if you can elaborate it would be helpful.
"does it mean the normal snapshot will be created first and the same will be replicated using snapmirror."
No, snapmirror will create it's own snapshot. As other have said as well, you're trying something which really doesn't have a defined behavior. You are much better off staggering the schedules so there's no chance of them conflicting.