This value should be used as a baseline for the host operating system virtual processor when calculating the overall ratio of physical cores to virtual processors. If performance monitoring of the host 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 In this event, you must configure the adapters in the host machine's operating system and present the logical unit numbers LUNs to guest virtual machines as either a virtual disk or a pass-through disk.
Host machines in some hardware virtualization applications may require storage space for an operating system and its components. Additional storage space is also required to support the operating system's paging file, management software, and crash recovery dump files.
Some hypervisors maintain files on the host machine that are unique to each guest virtual machine. For example, in a Hyper-V environment, a temporary memory storage file BIN file is created and maintained for each guest machine. The size of each BIN file is equal to the amount of memory allocated to the guest machine. In addition, other files may also be created and maintained on the host machine for each guest machine.
Each Exchange guest machine must be allocated sufficient storage space on the host machine for the fixed disk that contains the guest's operating system, any temporary memory storage files in use, and related virtual machine files that are hosted on the host machine. In addition, for each Exchange guest machine, you must also allocate sufficient storage for the message queues and sufficient storage for the databases and log files on Mailbox servers. Pass-through storage is storage that's configured at the host level and dedicated to one guest machine.
All storage used by an Exchange guest machine for storage of Exchange data must be block-level storage because Exchange doesn't support the use of network attached storage NAS volumes, other than in the SMB 3. Also, NAS storage that's presented to the guest as block-level storage via the hypervisor isn't supported.
The only supported usage of SMB 3. Such file shares can't be used for direct storage of Exchange data. When using SMB 3. Storage used by Exchange should be hosted in disk spindles that are separate from the storage that's hosting the guest virtual machine's operating system.
However, there is reduced performance in this configuration if the network stack inside a virtual machine isn't full-featured for example, not all virtual network stacks support jumbo frames.
This technology makes sense for workloads in which memory is needed for brief periods of time and then can be surrendered for other uses. However, it doesn't make sense for workloads that are designed to use memory on an ongoing basis. Exchange like many server applications with optimizations for performance that involve caching of data in memory is susceptible to poor system performance and an unacceptable client experience if it doesn't have full control over the memory allocated to the physical or virtual machine on which it's running.
As a result, using dynamic memory or memory overcommit features for Exchange isn't supported. The following are answers to some frequently asked questions about host-based failover clustering and migration technology with Exchange DAGs:. Microsoft can't make support statements for the integration of third-party hypervisor products using these technologies with Exchange, because these technologies aren't part of the Server Virtualization Validation Program SVVP.
You need to ensure that your hypervisor vendor supports the combination of their migration and clustering technology with Exchange. If your hypervisor vendor supports their migration technology with Exchange, Microsoft supports Exchange with their migration technology. Host-based failover clustering refers to any technology that provides the automatic ability to react to host-level failures and start affected virtual machines on alternate servers.
Use of this technology is supported given that, in a failure scenario, the virtual machine is coming up from a cold boot on the alternate host. This technology helps to make sure that the virtual machine never comes up from a saved state that's persisted on disk because it will be stale relative to the rest of the DAG members. Migration technology refers to any technology that allows a planned move of a virtual machine from one host machine to another host machine.
This move could also be an automated move that occurs as part of resource load balancing, but it isn't related to a failure in the system. Migrations are supported as long as the virtual machines never come up from a saved state that's persisted on disk.
This means that technology that moves a virtual machine by transporting the state and virtual machine memory over the network with no perceived downtime is supported for use with Exchange.
A third-party hypervisor vendor must provide support for the migration technology, while Microsoft provides support for Exchange when used in this configuration. Skip to main content. This browser is no longer supported.
Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No.
Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Exchange Server This forum provides a place for you to discuss the Exchange You are welcome to come and post questions and comments about your experience with this software.
Sign in to vote. Is there any performance factors when Virtualizing Exchange server?
0コメント