We fired up replication on a Hyper-V host that has never had any problems with disk space before. I use fixed disks for all of my VMs so the drive that stores my guests (G:) never was losing space. The G: drive has always had about 359GB free until I started
replicating 4 of my guests.
Here's some history of the G: drive gradually losing space over the span of almost a month now:
G: 359 GB free 6:11 AM 9/11/2014
G: 356 GB free 5:30 AM 9/12/2014
G: 352 GB free 9:10 AM 9/14/2014
G: 338 GB free 5:54 AM 9/18/2014
G: 328 GB free 6:46 AM 9/20/2014
G: 327 GB free 5:42 AM 9/21/2014
G: 326 GB free 6:45 AM 9/22/2014
G: 322 GB free 5:19 AM 9/23/2014
G: 325 GB free 5:21 AM 9/24/2014
G: 317 GB free 5:48 AM 9/25/2014
G: 299 GB free 5:11 AM 9/26/2014
G: 305 GB free 5:43 AM 9/29/2014
G: 298 GB free 5:51 AM 10/2/2014
G: 300 GB free 6:15 AM 10/3/2014
G: 296 GB free 5:45 AM 10/6/2014
Is there something I am missing to prevent this from using all of the available space on the drive? The health of the 4 replicated VMs is Normal so the replication is successful. I am only replicating 1 image, not several so I don't know why it keeps taking up more space every day.
I guess I just assumed that since the host drives are fixed then the drive should only decrease by what was changed on the server. Once the changes are replicated the associated .HRL files is zeroed out but the drive does not recover the space replicated
(assuming this is why the drive is losing space.)
Am I missing something?