Mike Resseler wrote:Robin,
The reason of that free space is because we need to take a snapshot of the Hyper-V VM. At that moment, what happens is that the original VHD(X) gets "frozen" (read-only) and all writes are going to a differential file (AVHD(X)). This is the way the backup of VM's work in Hyper-V (and for that matter, more or less the same in VMware). If the datastore is low on space that file can't be placed there and also the merge (after the backup) won't be possible as it needs additional space also (working space, it gets free again after that)
You say 5%, but how much is that in GB? And what is your host OS? And lastly, what is the size off the VM in total?
Mike Resseler wrote:Hmm. I would rather say you have space enough for those sizes. But, I might be wrong here but your VMs OS disk is only 2.72 GB? that seems low if it is a windows VM?
The disk free space I cannot calculate because it depends on how much churn there is (and the growth of the AVHDX because of that). If it is a very busy VM during the backup, it will be a big AVHDX file (could even be bigger than the original one if many changes occur).
How much is the total size of those datastores?
Mike Resseler wrote:That means you are already running on snapshots for some time I think. Can you check on Hyper-V manager to see if there are open snapshots? Potentially multiple?
Users browsing this forum: jay.cheon and 18 guests