how are you doing?
there is a customer that he wants to use legacy time finder mirror commands instead of Snapvx?, does any one have any best practices or performance documentation in order to talk to the customer about snapvx vs time finder snapvx emulations??
Any idea, recomendation, etc?
For VMAX3, there is really only SNAPVX. CLONE and MIRROR command sets are provided for backwards compatibility. When CLONE / MIRROR is run, it's doing VX under the covers.
The thing about mirror is that it is COPY, so it cant exploit the NOCOPY feature of native SNAPVX. Also SNAPVX is the only command set that allows for targetless snaps.
In other words, while it might be convenient to keep using mirror, you are quite likely throwing capacity away (copy) by keeping with the old command set.
I'd like to add another point to the Mirror vs. SNAPVX discussion. Dynamic Volume Expansion (DVE) with local and remote replication has been recently been made available for All Flash arrays. This will work fine with native SNAPVX in that you can expand a source volume with SnapVX sessions and it will work just fine - no need to terminate the sessions first now. This functionality does not extend to the emulation modes of local replication though. so no DVE with active TF Mirror / Clone sessions.
There is development roadmap for SNAPVX and future enhancements to SNAPVX may not make it to the local replication emulation modes. More food for thought when considering a conversion from Clone / Mirror to SnapVX.