Exchange 2010 DAG configured on Microsoft Server 2008 HyperV
I have two Virtual Servers configured using HyperV. These servers have the Mailbox role installed on them, with a DAG configured for HighAvailability. The DAG seems to be working fine, but when I run the Exchange Best Practice Analyzer for exchange 2010 on get an error on my 2nd mail Server, that says the following:
-Unsupported Virtual Machine Configuration - Clustering
When I click the link that says "tell me more about this issue and how to resolve it", it says the following:
The Microsoft® Exchange Server Analyzer Tool queries the Win32_ComputerSystem Microsoft Windows® Management Instrumentation (WMI) class to determine whether the value for the Model key is set to "Virtual Machine".
The Exchange Server Analyzer also queries the Win32_Service WMI class to determine the value of the Started key for ClusSvc, the Windows Cluster service. A value of True for the Started key indicates the Cluster service is started, and a value of False indicates the Cluster service is not started.
The Exchange Server Analyzer displays an error if the following conditions are true:
• The value for the Model key is set to "Virtual Machine".
• The value of the Started key for the Cluster service is set to True.
This error indicates that the Exchange server is a clustered Exchange server that is running in a virtual machine environment. This configuration is not supported.
To correct this error
1. Build a physical cluster and move the mailboxes to the physical cluster from the clustered Exchange server that is running in the virtual environment.
2. If you cannot build a physical cluster, you can correct this error as follows:
1. Move the mailboxes from the Exchange Server that is running in the virtual environment to a non-virtual, stand-alone Exchange Server computer.
2. Re-home any public folders and transfer any roles performed by the clustered Exchange server as required.
3. Uninstall Exchange Server from the virtual machine to decommission and remove it from the Exchange Server infrastructure and from Active Directory.
For more information about Microsoft support policy for running Exchange Server 2003 in virtual environments, see Microsoft Knowledge Base article 320220, "Support policy for Exchange Server 2003 running on hardware virtualization software" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=320220).
Before I installed exchange 2010 High Availability (DAG). I was reading articles that said there was no problem with doing this on HyperV virtual servers. Does Microsoft really not support High Availability on Virtuals? Thanks.
-Unsupported Virtual Machine Configuration - Clustering
When I click the link that says "tell me more about this issue and how to resolve it", it says the following:
The Microsoft® Exchange Server Analyzer Tool queries the Win32_ComputerSystem Microsoft Windows® Management Instrumentation (WMI) class to determine whether the value for the Model key is set to "Virtual Machine".
The Exchange Server Analyzer also queries the Win32_Service WMI class to determine the value of the Started key for ClusSvc, the Windows Cluster service. A value of True for the Started key indicates the Cluster service is started, and a value of False indicates the Cluster service is not started.
The Exchange Server Analyzer displays an error if the following conditions are true:
• The value for the Model key is set to "Virtual Machine".
• The value of the Started key for the Cluster service is set to True.
This error indicates that the Exchange server is a clustered Exchange server that is running in a virtual machine environment. This configuration is not supported.
To correct this error
1. Build a physical cluster and move the mailboxes to the physical cluster from the clustered Exchange server that is running in the virtual environment.
2. If you cannot build a physical cluster, you can correct this error as follows:
1. Move the mailboxes from the Exchange Server that is running in the virtual environment to a non-virtual, stand-alone Exchange Server computer.
2. Re-home any public folders and transfer any roles performed by the clustered Exchange server as required.
3. Uninstall Exchange Server from the virtual machine to decommission and remove it from the Exchange Server infrastructure and from Active Directory.
For more information about Microsoft support policy for running Exchange Server 2003 in virtual environments, see Microsoft Knowledge Base article 320220, "Support policy for Exchange Server 2003 running on hardware virtualization software" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=320220).
Before I installed exchange 2010 High Availability (DAG). I was reading articles that said there was no problem with doing this on HyperV virtual servers. Does Microsoft really not support High Availability on Virtuals? Thanks.
ASKER
I used the below article to configure the DAG. This installs windows 2008 failover clustering. So the two HyperV hosts are clusterd.
http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part3.html
http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part3.html
OH wait you have exchange installed ON the hyperV servers ? or as images inside the hyperv servers ?
the article you pointed to is a standard procedure to install Exchange 2010 DAGs it doesn't have anything to do with hyper V
check the hardware virtulization section in this one
http://technet.microsoft.com/en-us/library/aa996719.aspx
http://technet.microsoft.com/en-us/library/aa996719.aspx
ASKER
I have a windows 2008 R2 physical server with Hyper-V installed. One this server I have two Virtual Hosts, Mail 1 and Mail2. I have a DAG configured for High Availability for Mail1 and Mail2.
OK so Mail 1 and Mail2 are NOT on the physical server but images.
Do you clustering enabled on the HyperV servers (NOT on the exchange images ?)
Do you clustering enabled on the HyperV servers (NOT on the exchange images ?)
ASKER
This is my setup:
I have two Physical Servers that have Hyper-V installed on them. The physical servers are not clustered. On physical Server1, I have a virtual Machine "Mail1". One Physical Server2, I have virtual Machine "Mail". The DAG and failover clustering is configuring between the two virtuals. The Physical servers are not clustered. Does this make sense? Is this a wrong setup?
I have two Physical Servers that have Hyper-V installed on them. The physical servers are not clustered. On physical Server1, I have a virtual Machine "Mail1". One Physical Server2, I have virtual Machine "Mail". The DAG and failover clustering is configuring between the two virtuals. The Physical servers are not clustered. Does this make sense? Is this a wrong setup?
As far as I know your configuration is supported and the below taken from http://technet.microsoft.com/en-us/library/aa996719.aspx seems to confirm my saying
" Microsoft doesn't support combining Exchange high availability solutions (database availability groups (DAGs)) with hypervisor-based clustering, high availability, or migration solutions. DAGs are supported in hardware virtualization environments provided that the virtualization environment doesn't employ clustered root servers."
so unless you have clustered your hosts there is nothing wrong with your config
" Microsoft doesn't support combining Exchange high availability solutions (database availability groups (DAGs)) with hypervisor-based clustering, high availability, or migration solutions. DAGs are supported in hardware virtualization environments provided that the virtualization environment doesn't employ clustered root servers."
so unless you have clustered your hosts there is nothing wrong with your config
ASKER
In portion of the article you referenced above it says Microsoft does not support hypervisor-based clustering. Isn't that whay I did?
The Mail1 and Mail2 VM's are clustered, the phyical servers are not. When I run the exchange best practice Analyzer it says that clustering on Virtuals is not supported. Sorry if I sound confused, I am just looking for a high availability solution that microsoft supports and am hoping to do it with virtual servers. Thanks
The Mail1 and Mail2 VM's are clustered, the phyical servers are not. When I run the exchange best practice Analyzer it says that clustering on Virtuals is not supported. Sorry if I sound confused, I am just looking for a high availability solution that microsoft supports and am hoping to do it with virtual servers. Thanks
Again as far as I know the above means that if the hosts are not clustered then it is supported
ASKER
Thanks for your input Akhater. I will see if I can call Microsoft and see what they have to say. I have to know for sure if this is supported. The reason I am having my doubts is because the exchange best practice analyzer says "-Unsupported Virtual Machine Configuration - Clustering" I will add a comment after I find out. Thanks.
I would love to hear MS opinion on this however again you are sure you don't have clustering or NLB running on the hosts?
ASKER
By hosts, you are referring to the physical Server's correct? If so then yes, I am sure that Clustering / NLB is NOT running on the physical servers. I have VMs that reside on the physical servers that do have clustering configured. For example, Mail1 VM is on Physical Server 1 and Mail2 VM is on Physical Server 2. The VMs have clustering configured.
OK then I will be waiting for your answer then ! I have never seen anything referring to this as unsupported configuration. I might be mistaken though
This is a bug from the ExBPA, it is not updated with this info. This was confirmed by Henrik Walther http://www.msexchange.org/Henrik_Walther/
ASKER
Thanks Akhater, can you poing out in the above link where you read that. I couldn't find it.
ASKER
If you don't mind, can you point out the part of the article that says its an ExBPA bug I would very greatly appreciate it. I couldn't find it. Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
ASKER
I just got off the phone with microsoft this seems to be a bug in the ExBPA. Thanks for all your help Akhater.
You are welcome, thank you for the updates
DAG are supported on HyperV just not when the HyperV server themselves are clustered