Currently EQL does not do synchronous replication.  Smallest interval is 5 minutes.  A hybrid approach would likely be the best.   ESX has SRM, Site Recovery Manger.  Using EQL replication all the VMFS volumes and non-SQL volumes would use standard replication.  If you had to enable the remote DR site,  SRM would allow you to get that up and running quickly.     SRM knows how to promote the replicas, scan in the VMFS volumes, re-register the VMs and start things back up.  For the volumes that are most time sensitive using a host based sync rep program would be better.   This would save you a lot of time and money to implement.  It's what many of our customers do.   Regards,   -don 
Hi  I have taken over the management of the VMWare ESX 4.5i cluster the boss would like to make the cluster available if one of the data centres becomes unavailable.  So I have set up something similar but on evas with CA.  So i am looking for HA not disaster recovery features. What I would like to have is   3 node + PS at DC1 and 1 (or 2 nodes) + PS at DC2.  No the systems that are running on this are 3 tier web / app / DB.  basically J2EE stuff.  What I would like :) active / active replication between the 2 PS devices, active/active being that I can write to a lun that is being replicated on both devices at the same time.  This would make life easy - make sure I have enough bandwidth to handle replication, latency isn't going to be too bad, as the DC's are within 30km of each other.  This way I can put all the nodes in 1 esx cluster and use VMware's drs/ha features to restart machine etc etc...   For the web doesn't really matter ... just reverse proxy's mainly. Apps - websphere clusters (2 nodes in dc1 and 1 node in dc2). The DB is going to be interesting (MS SQL), have to investigate MS cluster or VMWares drs...  networking BGP already in place.  Next best is the same as above, but with out active/active lun replication .... If the 2 PS can be active/passive - so in sync, but only 1 master, such that node 1 at dc2 talks to the lun via the WAN link thats sort of okay.  But the system must be able to handle fail over, ie the PS on DC1 fails, the PS at DC2 must take over the role and provide all the LUNs This is also workable.  But from my reading of the PS docu, it has replication, but it snaps and then replicates the snap - this doesn't work for me, I could loose committed transactions - THATS A NO NO.    I could use MS SQL replication, but ........  So forums guru's can I do what i want with the PS range or do I have to move up to emc/eva/IMB/hitachi ....  Alex  
Metro (Stretch) Cluster with PS6010