#VDMX FILES HYPER V FULL#
#VDMX FILES HYPER V WINDOWS#

Most likely, that snapshot isn't Veeam's, but comes from someone taking a checkpoint (that is how it is called in Hyper-V) with the Hyper-V UI. If you can't get it merged, then you would loose a LOT of data. From the timestamps, I can see you are running on a snapshot disk for 1 month, 1 day and about 12 hours which is:Д«) Not good for the performance of your Exchange server It means that the VM is running on those snapshots already for quite some time. What seems to be not normal is the size of those snapshots. They also have a MRT and RCT file, which is again normal, and size of those files is also normal. Then I see again two disks (Exchange_XXXX.AVHDX and ExchangeBackEnd_XXXX.AVHDX). As I said, those files are the mechanism to understand what blocks are changed in between backups. Both those drives have a MRT and RCT file and the sizes are normal sizes, nothing wrong with that. (Exchange.VHDX and ExchangeBackEnd.VHDX). What I can see is that you two disks in that directory. The picture makes it a bit more clear (a picture says more than a 1000 words ). Pretty much Work, but by the Way, Veeam B&R is awesome in Home Lab especially for Testing etc pp. I will Check today if the Problem is surely Fixed with migrating the Storage one time, and if it is, i will buy a external Drive to migrate the Storage. I would now sayed i just move that Storage one time too, as Workaround for that problem, but i have no Storage at home where i could migrate it, and the Filer is always Busy too and has to be High Avaible. At that Point, everything was in a normal state again.Д«ut when Veeam takes new backups, it creates new Files again, as it is normal, and it deletes now old Files in the SystemVHDx, but still not on the great Drive, with 2 TB. It took about 12 Hours to Merge all the SystemVHDx Files and the Files of the 2 TB VHDx.

#VDMX FILES HYPER V FULL#

Then i had to move (Just the one) the System VHDx File to another Storage because the Flash Storage was almost full and then all the VMs and the Host would crash.ДЄfter Hyper V completet the move Action of the System VHDx successfully, it autmatically shows me that it began Merging.

#VDMX FILES HYPER V WINDOWS#

i Tried to merge with Powershell, but there was not even an Output, i think because Windows has no Checkpoints registered and so the Action was successfull quitted. In Hyper V were no Checkpoints as i could see. I had the Problem VM-Wide, with the System VHDx (about 30 GB) and with the Storage VHDx (About 2 TB yet).

Vdmx files hyper v