I'm re-running the test that took 35 hours to reproduce the bug(Commit da1674843 as tip of tree). I hope it causes the bug to trigger much faster. If it does, I'll use this method for testing.
If it still takes a considerable amount of time to reproduce, I'll investigate the snapeshot only method as suggested by @Emsi.
Thanks for the suggestions @faulpeltz and @Emsi. I was using the Windows Server Backup GUI, which allowed me a maximum of 30 minutes backup intervals.
I now have a Powershell script to kick of one backup after another:
$i=1 ####### ######" ####### ######" "\\?\Volume{ VOLUME_ INFO}" -hyperv:"VM_NAME" ####### ######" ####### ######"
while($true)
{
"######
"Starting backup $i"
"######
wbadmin start backup -quiet -backupTarget:
"######
"Finished backup $i"
"######
$i++
}
I'm re-running the test that took 35 hours to reproduce the bug(Commit da1674843 as tip of tree). I hope it causes the bug to trigger much faster. If it does, I'll use this method for testing.
If it still takes a considerable amount of time to reproduce, I'll investigate the snapeshot only method as suggested by @Emsi.