I am curious to hear from EMC why would you release TimeFinder/Clone functionality on VMAX3 when you know that is so broken ?  When you create TimeFinder/Clone recreate on VMAX3, it performs some kind of scan and that scan can take hours depending on how big your environment is.  For example i have a 30TB Oracle DB that consists of 86 x 500G volumes.  Every "symclone recreate" takes 1.5 hours to complete even if there is absolutely no changes on source or target devices.  My clone target is an R1 so until the clone becomes "Copied" i can't push it to my R2.   You  might say that i should be using TImeFinder/SnapVX,  well it's just as broken Reproduce TimeFinder/Clone functionality on VMAX3 .  Also the whole RDP issue with snapvx, unless you upgrade to a 3 weeks old Hudson,  you can't see RDP utilization.

Feedback that i am getting from my local EMC team is that there is no desire/direction of fixing this TimeFinder/Clone issue, basically we are screwed.  How can you let your decades long customers down like that ?