Restoration Hyper-V Virtual Machines in Saved/Paused States

Protecting Hyper-V Virtual Machines in Saved/Paused States with XoperoONE

Understanding the Hyper-V VM Saved and Paused States

Hyper-V virtual machines (VMs) can be placed in various states depending on the operational needs. Two specific states include Saved and Paused:

Saved state

  • When a VM enters the Saved state, its current state is preserved to disk, effectively freezing its operation.

  • All memory content and device states are saved, and the VM's execution is paused until it's resumed.

  • This state is commonly used for freeing up host resources temporarily or safely shutting down the host without losing the VM's running state.

Paused state

  • A VM in the Paused state is temporarily suspended, halting its execution while maintaining its current memory state.

  • This state allows administrators to perform immediate maintenance without closing the VM or disrupting active sessions.

  • Unlike the Saved state, the Paused state keeps the VM's memory in RAM, requiring sufficient host resources.

Protecting Hyper-V Virtual Machines in Saved/Paused States with XoperoONE

XoperoONE is designed to effectively protect Hyper-V virtual machines (VMs), including those in the Saved or Paused state. This article explains how our solution handles VMs in these states, providing clarity on the use case and restoring capabilities.

Protection of Hyper-V VMs in Saved/Paused State

  • XoperoONE can secure virtual machines in both the Saved and Paused states.

  • However, direct restoration of VMs back into the Saved/Paused state is not possible.

Restoration Process:

  • VMs are restored along with all their data to the backup state, but they cannot be directly restored into the Saved/Paused state.

  • The machine is restored in a powered-off state, requiring manual intervention to switch it back to the desired state.

Last updated