There are several scenarios where Exporting a Guest Partition is appropriate. The most common scenario is when a new Hyper-V Host Server is brought online to offer additional capacity, or a newly configured 'High Availability' configuration of Hyper-V is made available. There are some caveats for using the 'Export' function. Taylor B from the Microsoft Hyper-V Test Team offers an excellent WMI-Based 'Guest Partition Export' in his Blog entry. In this scenario I will use the Hyper-V Management Console to Export a Guest Partition. If you have ever wondered how to export a Guest Partition in Hyper-V, here is your entry!
The general steps to follow are:
- If this is a 'Guest Partition Template' use the Sysprep process to 'seal' the Template prior to beginning.
- If this is a Domain Member (Domain Joined Member Server, for example) - take note of the Network Interface Settings of both the Hyper-V Host (the Host where the Export occurs) and the Hyper-V Target (the Host where the Import will occur). The changes in how Network Interface Cards and Virtual Switches in Hyper-V (in a good way) make these two configuration settings the most likely to cause additional configuration steps.
- Create an 'Export Folder' on the NTFS Partition (or LUN) where the 'Export' will generate files.
- 'Shut Down' the Guest Partition prior to Export.
- Export the Guest Partition into the Export Folder.
- Import the 'Export Folder' on the new Hyper-V Target Host.
- Validate the 'Settings' for the Guest Partition (remember the NIC Settings above) and correct as required.
- Launch the Guest Partition on the new Hyper-V Target Host.
1. In the Hyper-V Management Console I select a specific 'Guest Partition (the cool new name for Guest Server)' to be Exported. The idea here is to allow 'exporting' from one Hyper-V Host (in the Maintenance Window, for example) to another Hyper-V Host. It happens this particular Guest Partition is a Vista Enterprise Template (Translation: Vista Enterprise sealed using Sysprep).
2. I prefer to review all the Guest Partition settings in advance of making changes. A quick review of all the settings follows. When in a Production Environment, pay particular attention to the Network Interfaces and Virtual Switch settings in Hyper-V. The architectural differences made to Hyper-V in this regard (compared to Virtual Server 2005 R2) require minor configuration changes in some instances.
3. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Add Hardware' Tree Node.
4. Guest Partition 'Settings' reviewed in advance of 'Export'. 'BIOS' Tree Node.
5. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Memory' Tree Node.
6. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Processor' Tree Node.
7. Guest Partition 'Settings' reviewed in advance of 'Export'. 'IDE Controller 0' Tree Node.
8. Guest Partition 'Settings' reviewed in advance of 'Export'. 'IDE Controller 1' Tree Node.
9. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Network Adapter' Tree Node.
10. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Name' Tree Node.
11. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Integration Services' Tree Node.
12. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Snapshot File Location' Tree Node.
13. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Automatic Start Action' Tree Node.
14. Guest Partition 'Settings' reviewed in advance of 'Export'. 'Automatic Stop Action' Tree Node.
15. Upon review of the Guest Partition 'Settings' we can begin the 'Export'. Again, our objective is to Export the Guest Partition to allow an 'Import' of the Guest Partition on another Hyper-V Server. One more item before we begin, I always examine the File and Folder structute of the Guest Partition. In this instance, note the File Extension of the Configuration File (I note it below). It begins as an .XML File, then changes (during the Export process) into .EXP (Export File) extension.
16. Here is the File and Folder structure for the Guest Partition due to be 'Exported'.
17. Note the Snapshot File Folder.
18. A matching GUID-based Folder in the Snapshots Folder.
19. Here is the heart of a Hyper-V Guest Partition - the .VHD or Virtual Hard Disk. Note the size of 8.6GB.
20. Here is the Virtual Machine Configuration File (used to have a .VMC File Extension I believe). This File Extension will change from .XML to .EXP during the Guest Partition Export process.
21. A matching GUID-based Folder structure to the 'Snapshot Folder' above.
22. Here is the 'Target Folder' the Guest Partition Files and Folders will be exported into.
23. Okay, no more threats...the Export is about to begin. (-:
24. Target Folder selected and next hit the 'Export' button.
25. Export underway. We will visit the Target Export Folder next.
26. Export of the Guest Partition complete. Let's move to the Folder structure to see what we have.
27. The Folders (and Files for that matter) look very similar to the original Source Folder Structure.
28. Good, we have our Virtual Hard Disk (.VHD) File (with matching 'Size' and 'Date Modified' values).
29. Excellent! We now have a 'Fully Exported' Guest Partition. This can be 'Imported' using a similar process on the Target Hyper-V Host Server. Keep in mind my prior comments about watching the Network Interface Cards ans Virtual Switches closely.
As you advance in working with Hyper-V, I hope understanding how to 'Export' a Guest Partition is well used in your System Engineer Toolkit!
If you'd like to 'Learn Advanced IT' - Check out the Free Video Lessons on Windows 2008 SP2 Failover Cluster Nodes for Highly Available File Services and other Microsoft topics as well - http://www.exchangesummit.net.
Posted
Jan 19 2009, 04:20 AM
by
lynn lunik