# VM Snapshot Recovery After VME Manager Restore

This topic explains why VME Manager may not display VM snapshots after a VME Manager restore. It also describes how to identify and recover or clean up snapshots that still exist outside VME Manager.

## Problem Summary

After a VME Manager restore, snapshots may no longer appear in the VME Manager UI. The affected VM may also appear as a discovered instance instead of a managed instance. Testing confirmed that VME Manager can lose snapshot visibility after restore, while the snapshot file can still remain on the filesystem.

This condition creates an orphaned snapshot.

An orphaned snapshot exists at the storage or hypervisor level, but VME Manager no longer tracks or displays it.

## Reason for Undisplayed Snapshots

VME Manager stores snapshot information in its database. When an administrator restores VME Manager from an older backup, VME Manager restores the database to the state captured at the backup time.

If a snapshot was created after that backup, the restored database does not contain that snapshot record. As a result, VME Manager does not display the snapshot after restore.

The restore does not necessarily delete the underlying snapshot data. Testing confirmed that the snapshot file can still remain on the filesystem after the restore.

Table 1. Behavior

    | Area | Result |
| --- | --- |
| VME Manager UI | VME Manager does not display the snapshot. |
| VM state | The VM can appear under discovered instances. |
| Snapshot metadata | VME Manager loses snapshot details such as description and creation date. |
| Filesystem | The snapshot file can remain on the filesystem. |
| VM data | Files created inside the VM remain after restore. VME Manager does not revert the VM. |
| Managed conversion | Converting the VM back to managed state does not restore the missing snapshot entry. |

Undisplayed snapshots can create the following risks:

- Administrators cannot manage the snapshot from VME Manager.
- Snapshot files may continue to consume storage.
- VME Manager may not show the actual snapshot state of the VM.
- Administrators may need hypervisor-level or filesystem-level validation before cleanup.
- VMs created after the VME Manager backup may lose labels, tags, and metadata after restore.

## Recovery Process

Use the following process to identify and recover or clean up undisplayed snapshots.

1. Check Snapshot Visibility in VME Manager

   1. Log in to VME Manager.
   2. Open the affected VM.
   3. Go to the snapshot view.
   4. Confirm whether VME Manager displays the expected snapshot.If VME Manager does not display the snapshot, continue with CLI and filesystem validation.
2. Check Snapshot Metadata from the Hypervisor

   Run the following command on the VME or hypervisor host:

   ```
   ```
   Shell  
   virsh snapshot-list <vm-name>  
   Show more lines  
   Example:  
   Shell  
   virsh snapshot-list ubuntu-test
   ```
   ```

   If the command returns no snapshot entry, VME Manager and the hypervisor snapshot metadata may no longer show the snapshot. Testing showed this behavior after restore.
3. Check Snapshot Files on the Filesystem

   Check the VM disk directory for snapshot files. Search for files with the naming pattern `<diskname>-snap-<id>`

   If the file exists, the snapshot data still exists at the filesystem level even though VME Manager does not display it. Testing confirmed this condition after VME Manager restore.
4. Validate the VM Data

   Log in to the VM and check the expected files, application data, and service state.

   If the files created inside the VM remained after VME Manager restore. This means the restore did not revert the VM to the snapshot state.

## Recovery Options

Choose one of the following options based on the VM state and business requirement.

**Option 1: Keep the Current VM State and Clean Up the Orphaned Snapshot**

Use this option when the VM runs correctly and you do not need to recover data from the snapshot.

1. Back up the VM or affected virtual disks.
2. Confirm that the VM and applications work as expected.
3. Identify the snapshot chain at the hypervisor or filesystem level.
4. Commit or merge the snapshot chain using approved hypervisor tools.
5. Remove orphaned snapshot files only after you confirm that the VM no longer depends on them.
6. Convert or import the VM into VME Manager if it appears as discovered.
7. Create a new snapshot from VME Manager if required.

**Option 2: Recover Data from the Snapshot**

Use this option when you need data from the orphaned snapshot.

1. Stop or reduce write activity on the VM.
2. Back up the VM disk and snapshot files.
3. Identify the base disk and related snapshot files.
4. Inspect the snapshot chain using approved hypervisor or storage tools.
5. Recover the required data.
6. Commit the required disk state.
7. Start the VM and validate the data.
8. Import or convert the VM into VME Manager.
9. Create a new VME-managed snapshot.

**Option 3: Recreate Snapshot Management in VME Manager**

Use this option after you clean up or merge orphaned snapshots.

1. Convert or import the VM into VME Manager.
2. Confirm that VME Manager shows the VM as managed.
3. Confirm that no unwanted orphaned snapshot file remains on the filesystem.
4. Create a new snapshot from VME Manager.
5. Record the new snapshot name, creation date, and purpose.

Converting the VM back to managed state does not restore the old missing snapshot entry. Create a new snapshot after you validate and stabilize the VM.

## Important Guidance

- Do not delete snapshot files directly unless you confirm that the VM does not depend on them.
- Always back up VM disk files before you modify, merge, or remove snapshot files.
- Do not rely only on the VME Manager UI after a restore. Validate the VM at the hypervisor and filesystem levels.
- Use approved hypervisor tools to commit, merge, or recover snapshot data.
- Recreate snapshots in VME Manager after cleanup if you need VME-managed snapshot operations.
