Hyper V Live Migration Scenario


just wish make sure thinking/planning practically achievable. please advice/recommend/correct me. following wish do/achieve.

1. using win2008 r2, install/setup 3 hyper v host on similar server h/w. enough shared storage.

2. create hyper v /windows cluster using 3 server nodes.

3. have requirement run 8 application servers, configure/create 4 vm's each on of first , second hyper v host respectively or else configure/create 3+3+2 vm's spread across 3 hyper v host

4. using live migration hyper v feature of r2 should able achive following

a. move manually of vm's 1 hyper v host without service disruption. or there momentarily service disruption?

b. in case 1 hyper v host goes down vm's hosting should activate automatically on other available hyper v host. happen or without service disruption?

c. suppose if out of 3 hyper v host, 1 hyper v host hosting 2 vm's & hyper v host goes down.  can/will 2 vm's staring running on hyper v host or is possible have such configuration 1 of vm's failed hyper v host start running on hyper v host 2 & starts running on hyper v host 3 automatically.



hello,

i`ve written posts hyper-v failover cluster. might find relevant

failover cluster use hyper-v >> http://kristiannese.blogspot.com/2011/01/failover-cluster-for-use-with-hyper-v.html

preparing iscsi disk >> http://kristiannese.blogspot.com/2010/12/prepare-your-iscsi-disk-for-use.html

 

some information csv feature:

r2 introduced significant change in way storage volumes can accessed vms, , feature (csv) is available hyper-v 2008 r2 vms. csv functions distributed-access file system access vhds. other cluster technologies other vendors have accomplished similar function creating proprietary cluster file systems. these cluster file systems provide locking mechanism shared among hosts in cluster limits access disk single node @ time, nodes have read/writes access. csv not use proprietary volume format, uses standard ntfs windows has used years :-). also: csv enables hyper-v hosts have full read/write access vhds of vms hosting. 
csv option turn on in failover cluster built hyper-v r2 hosts. 
it`s implemented creating directory on c: volume of each node in cluster.
example:
c:\clusterstorage\volume1
c:\clusterstorage\volume2
in case, 2 shared disks in cluster assigned csv. first volume has 4 vms stored on it, , second volume has 5 vms stored on it. 1 node of cluster own physical lun of shared volume, each volume can owned different nodes of cluster. csv provides ability each node have full read/write access individual vhds used different vms.
-does csv performance? 
the impact disk type of vhds. fixed vhds provides same performance pass-through disk, again: gives flexibility. recommend not use dynamic vhds. especially in production environment. 
another thing group csv volumes similar disk types (group sas disk 1 csv, , sata etc.)
-where can more detailed info on csv? 
also: not hesitate post things around @ forums. many people has lot of experience hyper-v, csv etc.
active directory requirements failover cluster scenario >> http://kristiannese.blogspot.com/2010/11/failover-clustering-and-domain.html
and last: it`s possible configure preferred nodes vms, , define policy on should located after service interruption on host etc. 
good luck!


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


Windows Server  >  Hyper-V



Comments

Popular posts from this blog

for loop and start-job from cmd.exe

Edit Group Policy

File Share Witness is not a valid File share path