When to export and import Hyperv virtual machines to keep business running.
Last Review: June 28, 2019
Product(s): Office 365, Azure
Author(s): John Whinery
A cyberist created this article using the patented Delta Method by modernizing a typical approach.
Hyperv virtual machines (VM) should be exported and imported for migration to new equipment or as failsafe for recovery from updates/upgrades beyond incremental checkpoints. Unlike a checkpoint, exporting a copy of the VM is a full backup in case anything goes wrong. Best practice is having identically configured Hpyerv hosts with the same operating system, drive and memory configuration, network cards, and virtual switch naming conventions.
All requirements should be verified before proceeding to implementation steps:
Check for any Event Viewer errors and test functions with user verification. Processor or RAM may need to be increased for better performance depending upon Hyperv workload. Be sure to remove the VM from previous Hyperv host and delete exported VM copies after testing and next VM backup is complete.