Re: Hyper-V cluster
- From: "Ryan Sokolowski [MVP]" <ryan@xxxxxxxxxxxxxxxxx>
- Date: Tue, 6 Jan 2009 10:36:38 -0800
I'm not sure what you mean by "groups." Failover Clustering configures each service or application separately, including Virtual Machines. Each VM should contain a Virtual Machine resource, a Virtual Machine Configuration resource and one (or more) disk(s). This will also affect your proposed migration plan using groups. I'd recommend reading more about 2008 Failover Clustering to develop a better understanding and also working with the technologies in your test environment prior to undertaking a full-scale production migration.
Hope this helps,
--Ryan
--
Ryan Sokolowski
MVP - Clustering
MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP
"Steve Drake" <steve@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:0E3044EA-61F6-4DF7-A6B0-12B9F66B49BA@xxxxxxxxxxxxxxxx
Hello,
I am new to hyper-v and windows 2008 clustering, but I do have experience with windows 2003 clustering and virtual server.
What I need to achieve is a 3 node hyper-v cluster. This will be running many VMs and they will be grouped and SAN attached.
So we may have 8 cluster groups each with its own area on the SAN for the VMs and it will contain its own set of high availability virtual machines.
We could have all 8 groups running on Server A or we could have 2 on A 2 on B and 4 on C.
We need to be able to move groups from server to server.
First of all, can we do this?
My second question is about migrating a 3 standalone Virtual server servers to a Hyper-V cluster with 3 server. Note our existing platform is not SAN attached, all the VMS are on local disks.
We already have the 3 servers running virtual server, we can only take one down at a time. To keep this simple I will assume we only have 3 groups.
Our 3 servers are (Virtual Server A,B and C)
VSA,VSB,VSC
They will become
HVA,HVB,HVC (Hyper-V A,B and C)
We intend to do the following :
1. Backup the VHDs on VSA and rebuild VSA as HVA with Windows 2008.
2. Install clustering on HVA, Install Hyper-V on HVA.
3. Create a cluster group (GROUP A)
4. Add a DISK to GROUP A , DISKA (This is on our SAN)
5. Restore the VHDs to the shared disk
6. Add the VHDs to Hyper-V and make them highly available in Cluster Manager.
7. This gets us running with Hyper-V (a few weeks will pass)
8. Backup the VHDs on VSB and rebuild VSB as HVB with Windows 2008.
9. Install clustering on HVB, Install Hyper-V on HVB.
10. Add this server to the cluster
11. Add this server as a fail over node to group A
12. Test fail over of GROUP A
13. Create cluster group (GROUP B)
14. Add a disk to GROUP B, DISK B (Again from the SAN)
15. Restore the VHDs to the shared disk (DISK B)
16. Add the VHDs to Hyper-V and make them highly available in Cluster Manager.
17. We now have 2 cluster groups and 2 servers.
18. Follow same theme for adding 3rd server, do we need to do anything special to make the 3rd server easy to add?
Thanks
Steve
.
- Follow-Ups:
- Re: Hyper-V cluster
- From: Steve Drake
- Re: Hyper-V cluster
- References:
- Hyper-V cluster
- From: Steve Drake
- Hyper-V cluster
- Prev by Date: Cluster not supported in SCVMM?
- Next by Date: Re: How to migrate 32 bit to 64 bit cluster?
- Previous by thread: Hyper-V cluster
- Next by thread: Re: Hyper-V cluster
- Index(es):
Relevant Pages
|
