Over the past several years, I have utilized Virtual Server 2005 to run virtual machines for testing various Dynamics GP environments and development setups. Given that some clients use older software versions like SQL 2000 and GP 8, while others utilize the latest SQL 2008 and GP 10 service pack, maintaining these configurations on one physical machine proved challenging. Virtual Server offered an efficient way to manage and back up multiple server configurations. While Virtual Server and Virtual PC use the same VHD files, I found Virtual Server more user-friendly, easier for VM management, and faster.

I recently built a new Windows 2008 Server to transition my virtual machines to Hyper-V, which replaces Virtual Server 2005. To accommodate the memory requirements of virtual machines, I opted for the 64-bit version of Server 2008, bypassing the 3GB/4GB memory limitation of 32-bit Windows. My desktop machine, running Server 2008, supports up to 8GB of RAM, enabling me to comfortably host up to four virtual servers, each typically utilizing 1.5GB of memory, which exceeds my concurrent usage needs.

I am currently learning about Hyper-V, focusing on its differences and similarities to Virtual Server 2005. My goal is to understand how to perform comparable maintenance tasks and processes in Hyper-V, replacing my established Virtual Server 2005 methods. For example, I am exploring the optimal way to back up a Hyper-V image. Since Hyper-V creates slightly different files than VS 2005, I need to determine what to back up, when, and how. This includes investigating whether I can script a VM pause for backup execution, as I did with VS 2005. Additionally, I am looking into migrating an existing VS 2005 VHD file to Hyper-V (which is possible) and the necessary steps to ensure all server features function correctly within Hyper-V.

To begin, here are some helpful articles by Janique Carbone on VirtualizationAdmin.com that effectively explain Hyper-V basics and some new features.

Hyper-V Integration Services: These services seem to replace or upgrade the “Virtual Machine Additions” found in Virtual Server and Virtual PC. Installing them in your VMs is recommended for improved mouse usability, similar to VM Additions.

http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/general/windows-server-2008-hyper-v-integration-services.html

Understanding and Using Hyper-V Snapshots: While I still have questions about Hyper-V snapshots, they appear to be an impressive and highly functional feature.

http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/general/understanding-microsoft-windows-server-2008-hyper-v-snapshots.html

This video by Janique Carbone demonstrates the ease of creating and using snapshots:

http://www.virtualizationadmin.com/articles-tutorials/videos/microsoft-hyper-v-articles/general/using-hyper-v-snapshots.html

I find the way Hyper-V manages ‘branches’ of snapshots remarkable. It seems you can revert to previous snapshots and then create new snapshots, forming a new ‘branch.’ This feature is powerful, especially considering the speed of snapshot creation and application.

However, this capability can lead to many virtual server permutations. Learning to effectively manage these snapshots is crucial to prevent clutter and ensure meaningful use.

One initial recommendation for taking snapshots is to log out of all server sessions beforehand. Otherwise, your remote desktop connections will persist as disconnected sessions that you’ll have to clear if you revert to a snapshot.