Hi Joel,
Thank you for the detailed description of the issue. May I ask you to share the Veeam Support case number? It sounds like you and Support are approaching the same conclusion, but would be helpful just to track the issue.
Your solution in step 9 likely will be required regrettably unless Microsoft Support is able to assist; I would advise simply show the stacked up avhdx files to the Microsoft representative on your Support Case and then the checkpoint list in the Hyper-V manager (and the Powershell output) and ask them to explain the discrepancy.
"The process cannot access the file because it is being used by another process"
This + the permissions event error starts me thinking about anti-virus interference, but that's mostly a guess; the above error is an OS error that Veeam Backup and Replication returns when it cannot access something due to lock conflicts; VBR tracks the resources it locks during any operation and will give a more informative message if there is another Veeam operation locking the same resource, and usually AV is the culprit.
However, as noted please post the case number and show your Microsoft case representative the same issues with the avhdx files existing on disk but not shown in Powershell/Hyper-V manager.
Thank you for the detailed description of the issue. May I ask you to share the Veeam Support case number? It sounds like you and Support are approaching the same conclusion, but would be helpful just to track the issue.
Your solution in step 9 likely will be required regrettably unless Microsoft Support is able to assist; I would advise simply show the stacked up avhdx files to the Microsoft representative on your Support Case and then the checkpoint list in the Hyper-V manager (and the Powershell output) and ask them to explain the discrepancy.
"The process cannot access the file because it is being used by another process"
This + the permissions event error starts me thinking about anti-virus interference, but that's mostly a guess; the above error is an OS error that Veeam Backup and Replication returns when it cannot access something due to lock conflicts; VBR tracks the resources it locks during any operation and will give a more informative message if there is another Veeam operation locking the same resource, and usually AV is the culprit.
However, as noted please post the case number and show your Microsoft case representative the same issues with the avhdx files existing on disk but not shown in Powershell/Hyper-V manager.
Statistics: Posted by david.domask — Apr 17, 2024 2:29 pm
