Hi all, I apologies for the lengthy post, and any irrelevant information. I'm trying to provide as much information as I can.
I have been asked to log this ticket by Veeam, as they determine it is a Microsoft issue.
We use Veeam Backup and Replication to backup all of our Hyper-V guests.
We also use VeeamONE to report on issues.
Our environment is:
- a standalone physical server running our Veeam software
- two clustered servers with Fibre Channel storage (Cluster Shared Volumes) hosting our VMs (approx. 20 guests VMs)
For the most part, this all runs fine. Occasionally, however, VeeamONE reports the following error:
Description
Fired by event: 12240 Microsoft-Windows-Hyper-V-VMMS
Event description: '': Attachment 'C:\ClusterStorage\ServerName\Virtual Hard Disks\diskname_E40FF910-B414-4DFA-BDC3-BE02ACDCF27A.avhdx' not found. Error: 'The system cannot find the file specified.' (0x80070002). (Virtual machine ID )
Initiated by: DOMAIN\BackupAdmin
Knowledge
Cannot open VM attachment
It happens to random servers, on random dates, so no pattern to the issue.
The AVHDX files that is "not found" is the snapshot file created by Veeam during the Backup process.
Veeam uses an API to take the snapshot, then another one to remove it when the backup is complete.
So, in effect, the error is correct, as the file no longer exists, but why is it being logged, if the API is removing the snapshot correctly, should Windows be able to detect this and not log the error?
My main concern is that this then logs an error with VeeamONE, and makes our reports and KPIs look bad, with all these false reports.
I know that the easy solution is to turn off that Alert, but I would like to catch legitimate issues, not the false positives.
If relevant:
- All servers fully patched and restarted
- Integration services are up to date on most servers (issue happens regardless of version)
Again, I apologies for lengthy post. In summary, my question is: Why does Windows/Hyper-V log that error for a temporary Snapshot disk? Is it a bug in the API call? Is Veeam initiating the API call incorrectly?