Archive for the ‘Hyper-V’ Category

Problem:

Type: Consistency check Status: Failed Description: DPM cannot continue protection for VMware <vm_name> on <vCenter_server/ESX host IP>  (ID 30184) More information End time: 2018-03-12 23:48:37 Start time: 2018-03-12 23:48:37 Time elapsed: 00:00:00 Data transferred: 0 MB Cluster node – Source details: <vm_name> Protection group: Protection Group 1 Items scanned: 0 Items fixed: 0

 

Resolution 1:

Problem with VM *.vmx file.

  • Delete vmx and recreate VM
    or
  • create new VM and bind hdd from old VM.

 

Resolution 2:

  • check if there is not snapshot on VM! :)

Problem:

Recently I noticed running out of space on one of Hyper-V host. There was only ~10% free space. Couple of VM was placed out of clustered storage, on local RAID.

But what was strange, this VM has ~100 AVHDX files and 1 main VHDX file, but there was no checkpoints!

Automerge should start automatically, but it doesn’t. So let’s try on my own.

 there are about 100 AVHDX files!

 

but there is no any checkpoint in Hyper-V MMC

 

Resolution:

  1. Automerge : should start automatically. Delete checkpoints, then poweroff VM.
    In my situation, there was not any checkpoint, so automerge didn’t start.
  2. Merge files manually through Hyper-V : Hyper-V MMC -> edit disk -> locate latest AVHDX file (by date modification). Repeat procedure until you achieve one VHDX file.
    In my situation (~100 AVHDX files) it would take too long :) 
  3. Merge files manually – without Hyper-V :
    a) download VHDUtils from here
    b) extract makevhd.exe file to VM AVHDX files localization
    c) on cmd or PS run command:
    makevhd -d   merged-disk.vhd   0   latest-modified-avhdx-file.avhd
    d) wait, there will be no progress bar
    e) when merging has completed – attach VHDX to VM.
    You may have “Cannot change disk since a disk merging is pending” warning – just remove HDD from VM, apply VM settings, and then re-add newly merged VDHX file to VM.

That’s it.