> Hello,
>
> SBS Premium, MS scenario hyper-v setup (w2008-64bit as host, 2 vms: SBS
> 64-bit and W2008 32-bit).
> Host with 5 volumes (C - host system, D - sbs vhdfixed, E - W2008 32-bit
> vhdfixed, F - W2008 data vhdfixed, S - host swap).
> SBS machine is being paused with 16060 error - vol D runs out of disk
> space.
> Volume D contains only sbs vhd file and empty trash (actually switched off
> for this vol). Oryginally there is 1,08 GB free space on it. But when the
> machine is paused the free space is 199MB or even 99MB (but no additional
> files on it).
> It's hard to recover from the issue - restarts are not helpful (is this
> still Microsoft?? ;) )
> I suspect vss here. Full system backups (C, D, E, F) are scheduled to run
> every day at 9 p.m. (to a host external hard drive). Registers on the host
> are patched to do such backups properly. For a few days everything was
> fine
> but then a backup failed and I saw a weird issue in logs. Physical server
> restarted at the end of the bachup. The first message after that was:
> 1101 - "Inspection events were dropped during transport. The realtime
> backup
> file is corrupt by incorrect closing" [translated from polish - sorry for
> mistakes].
> and 6008 - unexpected restart
> Then come warnings:
> 16050 (hyperv) - volume D almost out of space
> 2013 (srv) - D runs out of space
> and then error
> 16060 (hyperv) - 'sbs' has been paused because it has run out of disk
> space
> on 'D:\'. (Virtual machine ID 53EC00D5-1A97-47E1-8E09-C9C733FA30DE)
>
> Questions:
> 1. How to quickly recover from such issue?
> 2. What is the best way here to prevent such issues?
> 3. What are best practices for organising hyper-v volumes?
>
> Best regards,
> --
> Krzysztof Wozniak, solidea.pl