• kurre
    0
    I have tried everything in thsi artlcle https://kb.msp360.com/standalone-backup/esxi-&-hyper-v/avhdx-files-not-merged-after-created-checkpoint

    I’m running Cloudberry Backup VM 7.4.2.2 on a Hyper‑V host (Windows Server 2019). Each night the job backs up a Windows Server 2019 VM .

    Over time the job has left behind hundreds of orphaned.avhdx differencing disks. I now have less than 6GB free on G:, and nightly backups fail when MSP360 attempts to create a checkpoint.

    Actions taken so far

    Disabled the backup schedule to stop further growth.

    Verified no checkpoints are listed in Hyper V Manager or via Get-VMSnapshot.

    Confirmed the orphaned.avhdx files are not referenced by the live VM (they date back to 2022).

    Planned workaround: Shut down the VM, move it to another host to collapse the chain, then delete the old files.

    Questions

    Is there an MSP360 setting that forces automatic merge/deletion of Hyper‑V checkpoints once a backup completes?

    If not, what is the recommended way to run image level backups without leaving residual.avhdx files (e.g., using crash consistent backups, different job type, or agent inside guest approach)?

    Are there cleanup utilities shipped with MSP360 that can detect and safely merge or delete orphaned snapshots?

    Any best practice documentation for Hyper V backup retention and disk space guidelines would be appreciated.

    Current environment

    Cbloudberry Backup VM 7.4.2.2

    Hyper V hosts: Windows Server 2019

    VM OS: Windows Server 2019 Standard

    Backup target: SMB share on NAS (incremental forever, compression enabled)
  • Steve Putnam
    36
    We use a power shell script in our RMM to identify any snapshots older than three days so that they can be remediated, usually merged or deleted.
bold
italic
underline
strike
code
quote
ulist
image
url
mention
reveal
youtube
tweet
Add a Comment