Hi ,
Regarding CCR solution, I read on Windows Server Catalog (SVVP) that for example this configuration is Supported with :
- Exchange Server 2007 Service Pack 1 on Hyper-V with Windows Server 2008 (x64) Guest OS
- Supported Exchange 2007 SP1 and later must be deployed on the Windows Server 2008 operating system
- supported features: Anti-Virus, Back-up Software, Virtual Machine Management Software, Cluster Continuous Replication (CCR), Virtual Processors.
Unsupported features: Unified Messaging, Dynamically Expanding Virtual Disks, Virtual disks that use differencing or delta mechanisms, Hyper-V Quick Migration combined with Exchange Clustering,
-----------------
Do you know what means Hyper-V Quick migration combined with Exchange on unsupported feature, I dont understand cos I have the same status on unsupported features with VMware.
does it mean windows 2008 clustering not supported?
with this configuration can we deploy 2008 clustering on Hyper-V as CCR ? DO you recommend to virtualize Exchange 2007 as I supposed you already experienced it ...
basically you cannot combine the HA features of Hyper-V/Vmware with the Exchange HA. Either go for Quick Migration but use standalone versions of Exchange or use CCR but use a hyper-v guest that is not highly available.
Yes you can run Exchange 2007 CCR virtualized on Hyper-V using Windows 2008 clustering but you cannot make the Hyper-V/VMWare guests highly available.
Virtualizing or not depends highly on your requirements, it's doable for sure..
Should You Virtualize Your Exchange 2007 SP1 Environment?http://msexchangeteam.com/archive/2009/01/22/450463.aspx
Sincerely,
Tonino BrunoTonino@btconsulting.be | ICT Consultant | B.T. Consulting bvba
Hi Tonino,
To clarify once again the architecture, as they provide me some corrections.
- 2 Exchange clusters MSCS EXchange 2003 under Windows 2003 in the same administrative group (for email )
- >> each cluster on different location with each node of each cluster on different location.
->> the 4 servers are on physical machin
- Another Exchange Exchange 2003 in stand alone in another administrativ group (for voice message storage )
->> virtual machin
Question : Can we migrate the 2 clusters MSCS Exchange from Exchange 2003 to 2 new Clusters CCR in Windows 2008 and let the Exchange 2003 on stand alone in this transition for a while
Sure... have a look at my collegue his blog posting on the transitioning to Exchange 2007
http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part1.htmlhttp://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part2.htmlhttp://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part3.htmlAnd for Exchange 2010 the Deployment Assistanthttp://technet.microsoft.com/en-us/library/ee681665.aspx
Running ExBPA on MS Exchange 2003 give us some errors, I dont know if all make a sense for Exchange migration from EXCH2003 to EXCH 2007:
-Organization : ............
'Global incoming message size '
'Global Outgoing message size not set'
'Recipient Update appears to be stalled'
-Admin Group:
>Srv EXCH1:
'Open relay test failed'
'Microsoft Exchange System Attendant resource dependency '
'DSAccess configuration is hard-coded
'Journaling recipient resides on the locql server'
'Journaling recipient should be hidden'
'Message transfer agent (MTA) outages will affect CLuster'
'MSDTC outages will affect cluster group' > as a best practice , use the Clusterter administrator program to disable the 'affect this group' option for this resource
'single global catalog in topology '> there is only one global catalog server in the Directory Services Access topology on server. this configuration should be avoided for fault tolerance reasons
(.....)
They all should be reviewed and resolved before moving to Exchange 2007/2010. Some of them are deliberate choices that have been made in the past I suppose and are not considered to be best practice such as fixing the DSACCESS configuration.
Thanks.
- Where can we have more explanations or help about errors provide from EXBPA.
- Regarding the server said in a previous note , EXCH5 , which is A Exchange Server 2003 too but will migrate after a while but not in their first target . This Exchange Server provide some errors too ,
' VMware detected. Exchange server apppears to be running as a virtual machin.Please review the support policy... '
I know that according to the MS policy Exchange 2007 is supported only on Windows 2008 on Virtual Machin
You say that we have to resolved the errors before moving to Exchange 2007. So Can this Exchange 2003 running on Windows 2003 in Virtual environment can affect the migration of the other Exchange 2003 running in a Cluster to Exchange 2007. I believe that it will be in transitioning Exchange 2003/2007
Exchan