Hyper-V Cluster Question


i working on setting hyper-v cluster 2 nodes failover/high availability. think have pretty basic understanding of needed set far, had question. let's have 2 nodes setup, dual switches multipath , iscsi san storage of vms. understanding both nodes use vms on san (not simultaneously, 1 node take on should other node go down). let's 1 of vms running windows server 2008 , while doing security patches, etc. there corruption/issue os. obviously, effect either node since using same file. suppose 1 have resort restoring backup @ point, doesn't make failover/high availabilty pointless extent? perhaps there missing , appreciate insight on how should handled properly. thanks!

since have high availability solution available in hyper-v failover clustering, why should consider guest clusters ?

reasons considering guest cluster, when need high available solution sql servers.

example: when sql server installed in two-node failover cluster, sql server service installed on both nodes of cluster. when 1 of nodes fails, remaining node take on processing being done on dead node. 
if had single sql server vm in hyper-v failover cluster, sql server restart on remaining node in cluster, having time consuming tasks completed before beeing able client requests.

requirements guest cluster:
can use iscsi guest clusters. 
build guest cluster, should follow same steps 'normal' cluster, using iscsi.

kristian (virtualization , coffee: http://kristiannese.blogspot.com )


Windows Server  >  Hyper-V



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607