T"as pas à répeter l'opération sur Node B, faut juste joindre le Node B au cluster

lancer le gestionnaire du cluster, après clique droit, sur gestionaire cluster, gérer le cluster, parcourir, et sélectionne le cluster récemment crée (dans cet exemple : EXCH01 / PS : n'oublie pas d'allumer le Node1)

Ensuite, le cluster d'importe dans ton gestionnaire, après, tu faits clique droit sur Nodes (là ou ya déja Node1), ajouter un noeud, et tu sélectionne Node2, ensuite, suivant suivant … terminer) ton noeud va se rajouter automatiquement)

J'espère avoir répondu à ta quesiton

Hicham KADIRI
Network é Systems Administator

I have a problem in the step 3 :

- i create a cluster with de Node A, it's ok it works,
- but when i have to repeat operations for Node B, there is a problem (with COM component) : {E1568352-586D-43E4-933F-8E6DC4DE317A}. I try to resolve it with this (http://www.offsitenoc.com/blogs/creating-an-instance-of-the-com-component-with-clsid-e1568352-586d-43e4-933f-8e6dc4de317a/) but i can't add a 2nd node :s

Any idea ?

WE HAVE TO LOG ON THE BOTH NODES WITH THE ADMINISTRATOR ACCOUNT OF DC (server with exch hub+cas+starwind installed) to be able to install failover clustr and do all administrativ task's

NOTE : DISABLE A PARENTAL CONTROL FOR THE LOCAL ACCOUNT ADMINISTRATOR TOO

I dont understand the part where: Failover Cluster Installation (NodeB)

Should i do the same things as for NODA: Defining and IP and another Clust Name?

I hope someone can reply fast it's urgent.

Thank you very much

Well, MS allows you to do these things but they are very limiting. Many people want to use Hyper-V and ESX for Live Migration/Vmotion/Etc but MS will not support it. Microsoft may still support your entire solution, just not that specific aspect of it.

For example, check out this bullet (What is the support policy for additional functionality of virtualization products? ) from the following: http://www.windowsservercatalog.com/svvp.aspx?svvppage=svvpsupport.htm

In the same article :
“Microsoft does not support combining Exchange clustering solutions (namely, cluster continuous replication (CCR) and single copy clusters (SCC)) with hypervisor-based clustering, high availability or migration solutions (for example, Hyper-V’s quick migration). Both CCR and SCC are supported in hardware virtualization environments provided that the virtualization environment does not employ clustered root servers.”

AND

“Virtual disks that dynamically expand are not supported by Exchange.”

This is exactly what I have right now for my Exchange 2k7 SP1 deployment on ESX 3.5U4. Never any problem with it. I am running a SCC cluster, but wanted to move to CCR to avoid the iSCSI shared storage requisite. You need dymanically expanding disks, you need storage-on-demand. Alltogether it seems it has no positive effect on the MS support policy either.

Another point “… configured at the host level and dedicated to one guest machine.”

So block level devices cannot take advantage of Hyper-V Live Migration or HA features. Is that the correct conclusion ?

So avoid Exchange on Hyper-V is what MS is saying ? Same counts for SQL 2005/2008 I suppose ?

BR,

Ronald

The storage used by the Exchange Server guest machine can be virtual storage of a fixed size (for example, fixed virtual hard drives (VHDs) in a Hyper-V environment), SCSI pass-through storage, or Internet SCSI (iSCSI) storage. Pass-through storage is storage that is configured at the host level and dedicated to one guest machine. Pass-through volumes must be presented as block-level storage to the hardware virtualization software, because Exchange 2007 does not support using network attached storage (NAS) volumes.

Bit of topic, but I heard that for creating a VM based Windows 2008 cluster on Hyper-V you need iSCSI for the shared storage part and you cannot use directly Fibre Channel (as you can in VMWare). Any idea how to make this perform well ? Can you create Hyper-V VMs with a 10G NIC orso ? Or does Hyper-V R2 support direct storage access with fibre channel ?

Till now I see a 1Gbps connection for iSCSI to my mailstores no directly moving to production. Looking at the specs this seems to slow. Haven’t tried it though.

Hope you have an idea

BR,

Ronald Topp

Bit of topic, but I heard that for creating a VM based Windows 2008 cluster on Hyper-V you need iSCSI for the shared storage part and you cannot use directly Fibre Channel (as you can in VMWare). Any idea how to make this perform well ? Can you create Hyper-V VMs with a 10G NIC orso ? Or does Hyper-V R2 support direct storage access with fibre channel ?

Till now I see a 1Gbps connection for iSCSI to my mailstores no directly moving to production. Looking at the specs this seems to slow. Haven’t tried it though.

Hope you have an idea

BR,

Ronald Top