VMware ESXi and vSphere Cluster Management

How to Restore a Snapshot in Oracle VirtualBox

Learn how to restore an Oracle VirtualBox snapshot, protect current VM work, use VBoxManage, understand snapshot trees, and verify the restored guest state.

Restoring a snapshot in Oracle VirtualBox rolls a virtual machine (VM) back to a saved checkpoint. This is useful for undoing a failed update, returning to a clean lab environment, or repeating a test from a known state.

A virtual machine is a software-defined computer running a guest operating system on a host computer. A snapshot is a saved checkpoint representing the VM's virtual disk and configuration state at a particular time.

What Restoring a Snapshot Does

When you restore a snapshot, VirtualBox makes the selected snapshot's captured state active again. The guest returns to the disk contents and VM configuration represented by that checkpoint.

You can restore an earlier snapshot or, when several checkpoints exist, a later snapshot. The key decision is the node selected in the snapshot tree—not simply the newest or oldest entry.

What changes during a restore

VM component	Expected result after restore	Risk or note
Guest files on affected virtual disks	Reverted to the disk state represented by the snapshot	Files created or changed afterward can be lost
Installed applications and updates	Returned to the versions present at the checkpoint	Later installations, patches, and configuration changes are removed from the restored state
VM configuration and virtual hardware settings	Snapshot-associated settings are reinstated	Memory, device, attachment, and other settings may differ from the current configuration
Data created after the snapshot	Usually absent from affected virtual disks after rollback	Preserve important work before restoring
Host-side files outside the virtual disk	Normally unchanged	Host folders, network locations, and separately managed external storage are not automatically rolled back

The affected storage is the VM's virtual hard disk, which is a disk image file or virtual storage device used by the guest. Data stored in a shared host folder or on an external storage system may not be governed by the snapshot.

Prepare Before Restoring

Use this checklist before starting the rollback:

Check	Why it matters	Recommended action
Correct snapshot selected	A snapshot tree can contain several similar checkpoints	Review the name, timestamp, description, and parent-child position
Current work preserved	Rollback can remove later guest changes	Create a snapshot of the current state, or copy essential files to independent storage
Guest activity stopped	Active writes can produce inconsistent or incomplete results	Shut down the guest cleanly when practical and close applications
Disk space and host stability checked	Snapshot operations can require storage and time	Check available host capacity and avoid the operation if host storage is unstable
Post-restore verification planned	The restored configuration may differ from the current one	Prepare to test startup, files, applications, networking, and relevant devices

Also verify that no other user, process, backup job, synchronization tool, or integration is actively writing important data to the VM. Snapshots are not a substitute for independent backups.

Restore a Snapshot in VirtualBox Manager

Open Oracle VirtualBox Manager.
Select the target VM in the machine list.
Open the VM's snapshot or history view.
Inspect the snapshot tree or list. Select the exact checkpoint you want to activate.
Open the selected snapshot's context menu or use the restore action.
When prompted, choose whether to preserve the VM's current state by creating a new snapshot before the rollback. Select this option when current work might be needed later.
Confirm the operation. Wait for VirtualBox to finish changing the disk and configuration state; do not interrupt the process.
Start the VM after the restore completes.
Verify that the guest matches the intended checkpoint.

The wording and placement of controls can vary between VirtualBox versions, but the workflow remains: select the VM, open its snapshot history, select a node, choose restore, decide whether to preserve the current state, and confirm.

Restore a Snapshot with VBoxManage

VBoxManage is VirtualBox's command-line administration utility. It is useful for repeatable lab work, scripted testing, and remote administration. A VM can be identified by its registered name or by its UUID, a unique identifier. Snapshots can likewise be identified by name or UUID.

First list the snapshots so you can confirm the available checkpoint names and identifiers:

VBoxManage snapshot "VM name" list

Replace VM name with the registered VM name. Use the listing to confirm the intended snapshot before restoring it.

To restore a snapshot by name:

VBoxManage snapshot "VM name" restore "Snapshot name"

Replace both quoted values with the exact VM and snapshot names. If names are ambiguous, restore by snapshot UUID:

VBoxManage snapshot "VM name" restore <snapshot-uuid>

Use the UUID shown by the snapshot listing. The VM should not be actively running during an operation that requires it to be powered off. Shut it down cleanly before retrying if necessary. If the shell cannot find VBoxManage, run it from a terminal where the VirtualBox installation is available in the system path.

Understand the Snapshot Tree

Snapshots can form a snapshot tree, which is a parent-child history of saved VM states. A later snapshot may be based on an earlier one, while separate branches can represent different experiments or lab paths.

Select the intended node rather than assuming that the newest checkpoint is correct. Restoring a node changes which saved virtual disk state and VM configuration become active. For easier selection, use descriptive labels such as clean-install, pre-update, or before-network-test, and add descriptions that record the purpose and important software state.

Validate the VM After Restoration

Start the VM and confirm that the guest operating system boots normally.
Check the expected operating-system version, installed applications, updates, and important files.
Review virtual hardware and VM settings that may have changed after the snapshot was created.
Test the network connection if the VM is used for networking or administration work.
Check shared folders, clipboard integration, USB or other device access when they matter to the workflow.
Confirm that virtual disk attachments and boot order are appropriate.
For a testing or training environment, document which checkpoint was restored and record any validation results.

Practical Examples

Undo a failed operating-system update

Take a snapshot before applying the update and label it pre-update.
Apply the update. If the guest becomes unstable, shut it down cleanly when possible.
Restore the pre-update snapshot.
Start the guest and verify that it returns to the known working operating-system and application state.

The update and related disk changes made after the snapshot are removed from the restored VM state.

Preserve current lab work before returning to a baseline

Create a snapshot of the current experiment state and label it clearly.
Restore the clean baseline snapshot.
Run the lab again from the baseline.
Restore the newly created experiment snapshot later if you need to resume the earlier work.

Creating the current-state snapshot before the rollback protects work that may be useful later, although important files should also be copied to independent storage.

Restore a named checkpoint from the command line

List snapshots for the VM with VBoxManage snapshot "VM name" list.
Identify the desired name or UUID.
Power off the VM and run the appropriate restore command.
Start the VM and validate the operating system, files, applications, and required integrations.

Limitations and Safety Considerations

Restoring can be destructive for changes made after the selected snapshot.
A snapshot is part of VM storage management, not an independent backup. Keep separate backups of important guest data and VM files.
Snapshot operations can require additional disk capacity and may take longer for large or complex VMs.
Avoid creating, deleting, or restoring snapshots while the VM is in active use or while host storage is unstable.
Manage snapshots deliberately on long-lived VMs with large virtual disks. An extensive snapshot history can complicate storage management and maintenance.
Data in host folders, network locations, or separately managed external storage may remain unchanged even when the guest disk is rolled back.

Troubleshooting

The desired snapshot is not visible

Confirm that the correct VM is selected and that its snapshot or history panel is open. Inspect the complete tree. The snapshot may have been deleted or may belong to another registered copy of the VM. You can also run VBoxManage snapshot "VM name" list to inspect snapshots for the selected VM.

You are afraid of losing current changes

Create a snapshot of the current state before restoring. Copy essential guest data to an independent location when it must survive outside snapshot history, and confirm the rollback target before accepting the restore prompt.

The VM does not look as expected after restoration

Review the snapshot tree and check whether the wrong node was selected. Determine whether the unexpected data is in a shared folder, network location, or other storage not governed by the VM snapshot. Then validate VM settings and virtual disk attachments.

The command-line restore fails or targets the wrong object

Check the exact VM name, snapshot name, and UUID by listing registered objects and snapshots. Power off the VM cleanly before retrying, and run VBoxManage from a terminal where the VirtualBox installation is available.

Summary

To restore a VirtualBox snapshot, identify the correct checkpoint, preserve current work if necessary, stop guest activity, restore the snapshot through VirtualBox Manager or VBoxManage, and validate the resulting VM. The operation returns affected virtual disks and VM configuration to the selected point in history; it does not merge later changes into that state. For related workflow guidance, see restore a VirtualBox snapshot.