Just implemented in my environment a VPLEX METRO with XIO
When planning to move my SQL ha 2012 cluster i encountered some questions on how to do it properly.
When thinking of cluster under VPLEX with Vsphere 6 above it seems natural to drop the cluster issue and move to one server.
If i use cluster 2012 with sql 2012 "always one" with 2 nodes im gone "write/replicate" my self to death (;
The synchronous log shipping will replicate the db1 to db2 by log shipping "always on" and the VPLEX gone replicate them both to site B synchronously .
What is the best practice to this issue?
Is it wize to keep "always on" with metro cluster with vsphere 6?
ankur.patel
2 Intern
•
286 Posts
595
0
Posted January 13th, 2016 07:00
It depends
This is personal preference as your choice on technologies depends on what you are trying to achieve.
Just relying on VMware HA wont save you from a sql server issue. Always on will
VPLEX metro will allow for vmotion of the vm if you plan on doing mobility throughout the year. Always on will not
Another thought Ive seen customers bring up is using vplex metro for HA and use always on to a 3rd site to a further datacenter.