Vmware tabanlı sanallaştırmada Exchange 2010 DAG desteği

 

Aşağıda Technet sayfasında Exchange 2010 implementasyonu sırasında sanallaştırma altyapısı kullanılacak ise dikkat edilmesi gereken noktalar belirtilmiş.

    Only management software (for example, antivirus software, backup software, or virtual machine management software) can be deployed on the physical root machine. No other server-based applications (for example, Exchange, SQL Server, Active Directory, or SAP) should be installed on the root machine. The root machine should be dedicated to running guest virtual machines.
    Microsoft doesn’t support combining Exchange high availability solutions (database availability groups (DAGs)) with hypervisor-based clustering, high availability, or migration solutions that will move or automatically failover mailbox servers that are members of a DAG between clustered root servers. DAGs are supported in hardware virtualization environments provided that the virtualization environment doesn’t employ clustered root servers, or the clustered root servers have been configured to never failover or automatically move mailbox servers that are members of a DAG to another root server.
    Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it’s running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots aren’t application aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange. As a result, making virtual machine snapshots of an Exchange guest virtual machine isn’t supported.
    Many hardware virtualization products allow you to specify the number of virtual processors that should be allocated to each guest virtual machine. The virtual processors located in the guest virtual machine share a fixed number of logical processors in the physical system. Exchange supports a virtual processor-to-logical processor ratio no greater than 2:1. For example, a dual processor system using quad core processors contains a total of 8 logical processors in the host system. On a system with this configuration, don’t allocate more than a total of 16 virtual processors to all guest virtual machines combined.
    When calculating the total number of virtual processors required by the root machine, you must also account for both I/O and operating system requirements. In most cases, the equivalent number of virtual processors required in the root operating system for a system hosting Exchange virtual machines is 2. This value should be used as a baseline for the root operating system virtual processor when calculating the overall ratio of physical cores to virtual processors. If performance monitoring of the root operating system indicates you’re consuming more processor utilization than the equivalent of 2 processors, you should reduce the count of virtual processors assigned to guest virtual machines accordingly and verify that the overall virtual processor-to-physical core ratio is no greater than 2:1.
    The operating system for an Exchange guest machine must use a disk that has a size equal to at least 15 GB plus the size of the virtual memory that’s allocated to the guest machine. This requirement is necessary to account for the operating system and paging file disk requirements. For example, if the guest machine is allocated 16 GB of memory, the minimum disk space needed for the guest operating system disk is 31 GB.
    In addition, it’s possible that guest virtual machines may be prevented from directly communicating with fibre channel or SCSI host bus adapters (HBAs) installed in the root machine. In this event, you must configure the adapters in the root machine’s operating system and present the LUNs to guest virtual machines as either a virtual disk or a pass-through disk. 

Özellikle işaretlediğim kısımlar birçok proje planlamasında atlanan nokta olabiliyor.Nedir bunlar?

Microsoft, Exchange yüksek erişebilirlik çözümleri kullanılacak ise bunun hyper visor tabanlı cluster çözümleri, migration seçenekleri ile kullanımını desteklememektedir.DAG yapısını ancak root cluster çözümünün kullanılmadığı durumlarda aktif edebiliyorsunuz.

Vmware bu konuda ne diyor?

Enhanced Clustering Support for Microsoft Windows – Microsoft Cluster Server (MSCS) for Windows 2000 and 2003 and Windows Server 2008 Failover Clustering is now supported on an VMware High Availability (HA) and Dynamic Resource Scheduler (DRS) cluster in a limited configuration. HA and DRS functionality can be effectively disabled for individual MSCS virtual machines as opposed to disabling HA and DRS on the entire ESX/ESXi host

Eğer Vsphere update 1 geçerseniz, içerideki sanal makineyi HA disable duruma getirdiğiniz takdirde çözümünüz vmware tarafında supported hale geliyor.

Bir diğer önemli kısım ise processor ratio değerleri.

Exchange server, üzerinde çalıştığı sanal makine konfigurasyonunda virtual processor-to-logical processor oranının 2:1’den büyük olmaması istiyor.Bunun dışında kalan konfigurasyon aynı şekilde unsupported olarak görülmektedir.

Leave a Reply

Your email address will not be published. Required fields are marked *

91 − 83 =