Best Practices for Using BizTalk Server on Hyper-V
The list below represents a summary of the installation and configuration requirements described in the Deploying BizTalk Server on Hyper-V section of this guide. These should be used as a quick reference list when installing, configuring and deploying BizTalk in a Hyper-V environment. Links to the relevant sections are provided for further information.
- Ensure you are using an x64-based version of Windows Server 2008. Hyper-V is available only for 64-bit, x64 editions of Windows Server 2008.
- Ensure your processor supports hardware-assisted virtualization. This requires a processor that is compatible with Intel VT or AMD Virtualization (AMD-V).
- Use Windows Server 2008 Core Edition for the root partition. This will minimize server overhead and improve Hyper-V performance.
- Run only the Hyper-V server role on the root partition.
- Ensure hardware-assisted virtualization and Data Execution Prevention (DEP) is present and enabled.
- Using a fixed size virtual hard disk (VHD) provides improved performance compared to dynamically-resized VHDs for operating system drives.
- Use pass-through disks for high disk I/O activities.
- Pass-through disks must be set as offline in the Hyper-V root partition.
- Use the SCSI controller to attach pass-through disks. The SCSI controller can only be installed if Hyper-V integration services are installed. Therefore, use of the SCSI controller to attach pass-through disks will ensure that Hyper-V integration services are installed which in turn will ensure optimal disk I/O performance.
Note Do not attach a system disk to a SCSI controller. A virtual hard disk that contains an operating system must be attached to an IDE controller.
- Use the Network Adapter instead of the Legacy Network Adapter when configuring networking for a virtual machine. The legacy network adapter is designed for operating systems that do not support integration components.
- Ensure that integration components (“enlightenments”) are installed on the virtual machine.
- Whenever possible, configure a 1-1 mapping between virtual and logical processors. For more information about configuring a 1-to-1 mapping between virtual and logical processors see the “Optimize Processor Performance” section in Optimizing Performance on Hyper-V.
- To minimize the time required to install virtual machines, create a base image consisting only of the guest operating system and software prerequisites. Use SysPrep to prepare the VHD image for reuse, and then base all your virtual machines (VMs) on this VHD.
Note Use SysPrep before installing BizTalk Server. After BizTalk Server is installed, SysPrep is no longer supported because BizTalk Server stores configuration information that SysPrep does not know about and therefore does not reset. For more information about SysPrep, see http://support.microsoft.com/?kbid=926028.
- For instructions on how to install BizTalk Server on the guest operating system, see the BizTalk Server 2006 R2 Installation Guides at http://go.microsoft.com/fwlink/?LinkId=81041.
- Run the BizTalk Server 2006 Best Practices Analyzer (BPA) tool on your completed BizTalk Server installation. The BPA tool is available at http://go.microsoft.com/fwlink/?LinkId=122578.
- For guidance on configuring, maintaining, and monitoring your solution, see the BizTalk Server Operations Guide at http://go.microsoft.com/fwlink/?LinkId=110533.
- To tune your BizTalk Server installation, follow the guidance in the “Optimizing Performance” section of the BizTalk Server Performance Optimizations guide at http://go.microsoft.com/fwlink/?LinkId=122579.
- When troubleshooting CPU-related issues in Hyper-V virtual machines, see the “Measuring Processor Performance” section in Measuring Performance on Hyper-V.