Published: September 9, 2010
This article contains preliminary guidance for using Microsoft Project Server 2010 with the Windows Server 2008 Hyper-V virtualization technology. The scope of this guidance covers Microsoft Project Server 2010 and Microsoft SharePoint Server 2010.
Support statement
Hardware and software requirements
In order to run Project Server 2010 in a Hyper-V environment, you must meet the Hyper-V prerequisites and follow the recommendations documented here and in Other resources later in this article.
Project Server 2010 recommendations for Hyper-V
The following are recommendations for setting up Project Server 2010 in a Hyper-V environment.
-
Review the documents described in Other resources, later in this article, as a prerequisite to deploying Project Server 2010 and SharePoint Server 2010 in a virtual environment.
-
Any Hyper-V virtual server must meet the requirements of the physical server (for example, CPUs, memory, and disk I/O) that you will run as a Hyper-V guest. As with all virtual technologies, there is an overhead cost on the host computer for each virtual machine.
-
Do not use the Hyper-V snapshot feature on virtual servers that are connected to Project Server 2010. This is because the timer services and the search applications might become unsynchronized during the snapshot process, and after the snapshot is finished, errors or inconsistencies can occur.
-
Do not use more virtual CPUs than there are physical CPUs on the Hyper-V host computer. Although Hyper-V lets you allocate more virtual CPUs than the number of physical CPUs, this causes performance issues because the hypervisor software has to swap out CPU contexts.
-
Leverage virtual networks. Hyper-V enables you to configure the following kinds of virtual networks:
- Private: The virtual machines on the private network can communicate with one another.
- Internal: The virtual machines can communicate with one another and with the host computer.
- External: The virtual machines can communicate with one another, the host computer, and computers on the physical network.
Private networks and internal networks do not use the physical network adapter or cable. Therefore, communications are faster and network congestion is minimized. You can take advantage of this network performance gain by creating an external network for the front-end Web servers and by creating a private or internal network for the application and SQL Server database servers.
Other resources
The following table provides important information about resources for Hyper-V, Project Server 2010, SharePoint Server 2010, and SQL Server 2008.
Conclusion
In any scenario, a virtual server that is running Project Server 2010 has the same minimum, and fundamental, requirements as a physical server that is running Project Server 2010. Virtualization provides many benefits. However, it does not eliminate or circumvent the existing requirements and best practices that relate to deploying, configuring, and maintaining a Project Server 2010 environment.
Change History
|
Date
|
Description
|
Reason
|
|
September 9, 2010
|
Initial publication
|
|