All pages
Powered by GitBook
1 of 9

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Residual Hyper-V checkpoints remaining after differential disk merge

Residual virtual machine checkpoints remain visible in Hyper-V Manager after differential disk files (.avhdx) have been merged, and they cannot be removed using standard tools such as Hyper-V Manager or PowerShell.


Residual checkpoints after .avhdx consolidation are typically caused by metadata desynchronization between the disk files and Hyper-V configuration. This can happen, for example, when differential disks are manually merged using PowerShell while Hyper-V Manager is still open — in this case, the .avhdx files are correctly merged into the base .vhdx file, but the checkpoint metadata is not removed. Other scenarios can also lead to the same issue, but this is one of the most common.


First, for the integrity of the operation, power off the virtual machine (before making any changes).

  • Open PowerShell as administrator and use the following command (replace [VirtualMachineName] with the actual name of the virtual machine as displayed in Hyper-V Manager):

    1. The command will return the names and IDs of all snapshots associated with the VM.

    1. For more detailed information, you can execute the following command:

    1. In the VM settings (Hyper-V Manager > Settings > Checkpoints > Checkpoint file location), identify the path where snapshots are stored and navigate to this directory in File Explorer. You will find folders and files named according to the snapshot identifiers returned earlier. Do not delete them yet, as they are still locked by the Hyper-V service.

    2. Open the services console (services.msc) and stop the service named Hyper-V Virtual Machine Management Service (VMMS). Alternatively, you can use a PowerShell command:

    1. Once the service is stopped, delete all folders and files corresponding to the problematic snapshot identifiers.

    2. Restart the previously stopped service using the following command:

    1. Reopen Hyper-V Manager and confirm that the previously persistent checkpoints no longer appear in the list of snapshots.

    Issue

    Cause

    Resolution

    Before attempting manual checkpoint removal, ensure that incremental (.avhdx) disks have been successfully merged into the main virtual disk. In the VM’s settings, confirm that the virtual hard disk path points to a .vhdx file, not an .avhdx.

    Get-VMSnapshot -VMName [VirtualMachineName] | Select-Object Name, Id
    Get-VMSnapshot -VMName [VirtualMachineName] | Format-List
    Stop-Service vmms
    Start-Service vmms

    Hyper-V

    Hyper-V related issues.

    Backup ends with "DW9700 - Creation of Application consistent snapshot failed" error
    Hyper-V environment is not visible in XMS despite installing the agent on the host
    Residual Hyper-V checkpoints remaining after differential disk merge
    Unable to assign a license to a Hyper-V host
    Unable to backup a Hyper-V cluster
    Cover
    Cover
    Cover
    Cover
    Cover

    VMware

    VMware backup is missing some files
    Cover

    Unable to backup a Hyper-V cluster

    Issue

    You are unable to backup your Hyper-V cluster.


    Resolution

    To secure a Hyper-V cluster, install a dedicated backup agent on each Hyper-V host. After installation, open XMS, go to Virtual Machines > Hyper-V to add the entire cluster to your backup plan using the dedicated checkboxes.

    Backup ends with "DW9700 - Creation of Application consistent snapshot failed" error

    Issue

    Backup (or replication) process finishes with "DW9700 - Creation of Application consistent snapshot failed" error message.


    Cause

    The error “DW9700 - Creation of Application consistent snapshot failed” usually means that during backup (or replication) process the Xopero system tried to create a VSS snapshot with application consistency, but the process didn’t complete successfully.


    Resolution

    1. Check whether integration services are enabled in your virtual machine settings (Services > Backup (volume shadow copy) must be checked).

    1. Check whether the operating system is supported by Hyper-V:

    Check if integration services are running on the guest system:
    Supported Windows guest operating systems for Hyper-V on Windows Server and Azure Stack HCI
    Supported Linux and FreeBSD virtual machines for Hyper-V on Windows Server and Windows
    Manage Hyper-V Integration Services

    VMware backup is missing some files

    Issue

    VMware backup is missing files and/or folders.


    Cause

    If your VMware backup ends with warnings, the task details may indicate that one or more files failed to back up. Permissions for the Datastore Browser are managed by the vCenter server — in some cases, access to the Datastore Browser may be disabled for security reasons or to prevent users from accessing core virtual machine files and folders stored on the datastores.


    Resolution

    Enable the Datastore Browser feature:

    1. Stop the VirtualCenter Server service.

    2. Back up the configuration file:

      1. For Windows vCenter Server: C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg

      2. For vCenter Server Appliance: /etc/vmware-vpx/vpxd.cfg

    1. Open the vpxd.cfg file in a text editor.

    2. Locate the <vpxd> tags and add the following entry within them:

    3. Save the changes.

    Unable to assign a license to a Hyper-V host

    Issue

    You have the license but cannot assign it to your Hyper-V host.


    Resolution

    To assign the correct installer license for Hyper-V hosts, you must use a dedicated Hyper-V per socket license. This license type is based on the number of processor sockets in the physical machine.

    Learn more about licenses in .

    this article
    Start the VirtualCenter Server service.
  • You should now be able to back up the previously problematic files.

  • Optionally, create a snapshot of the vSphere server VM to enable restoration in case of a failure.

    <enableHttpDatastoreAccess>true</enableHttpDatastoreAccess>

    Virtual machines

    VMware
    Hyper-V
    Cover
    Cover

    Hyper-V environment is not visible in XMS despite installing the agent on the host

    Issue

    You cannot see your Hyper-V environment in Xopero ONE Management Service (XMS) even after installing the agent on the host.


    Resolution

    Remember to use the appropriate installer to natively secure the Hyper-V host for external backup. This dedicated installer can be downloaded from the XMS in Virtual Machines > Hyper-V tab using the (+) Add new button.

    If the Hyper-V host was added as a regular agent (with endpoint or server license), go to the Devices tab, select the device, and choose Delete from the top menu (without deleting data). With the correct installer and a Hyper-V per socket license, the license will be assigned automatically.