I hear you. From an architecture perspective we aren't able to create the applicable test networks at the recovery site, and bubble networks will not provide us the accurate end-to-end application testing that is required. Believe me, I've been through all of those scenarios
. We're just not able (with this particular customer setup) able to do the type of robust application testing we require with a test failover. The business also wants to get the real feel for what an actual DR event will entail and look like. There are obviously a myriad of differences between a test and recovery, including shutting down production vm's, running certain scripts, the impact to replication being broken, ability for a successful mounting of the luns, etc. The test failover is handy, but not what is needed for what this customer is looking to achieve.