January 15, 2013 at 6:34 am
All -
What are your thoughts about:
- SQL cluster (2005 or greater) built on two Hyper-V nodes, Win 2008R2
- The nodes are on separate Hyper-V hosts
- Each host is itself running on a hardware-based Win 2008R2 cluster
We have several of these in SQL 2008R2 and a couple in SQL 2005.
Is there any real advantage to this belts-and-suspenders approach?
Is there any specific danger or vulnerability (i.e., might a failure at the hardware level cause simultaneous failovers, and what might be the implications there?
I'd appreciate your insights.
Mike Hinds
DBA, 1st Source Bank
Mike Hinds Lead Database Administrator1st Source BankMCP, MCTS
January 17, 2013 at 2:06 am
Most envrionments have DR solution coupled with HA solution in place for BCP events... GOD forbidding never occurs!
In your configuration if it is not GEO cluster then would suggest SQL mirroring to remote site in SYNCHRONOUS MODE with Manual Failover if possible.
The above option though good would need to supported by windows team for DNS update pointing to secondary server.
Not great fan of Hyper V rely more on VM solutions from VM ware, stating this would leave rest to experts on Hyper V to comment.
Some interesting read though below..
http://www.windowsitpro.com/article/virtualization2/Make-SQL-Server-Sing-on-Hyper-V-103658
Cheer Satish 🙂
January 18, 2013 at 11:00 am
This is a good article from David Klee that might be useful to your questions http://www.houseofbrick.com/blog/virtualizing-business-critical-sql-servers-a-part-5-high-availability-and-comparing-the-performance.html?blogger=solutionsarchitects. Hope this help.
Regards,
BP
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply