Veeam B&R: v9.5 U1
Exagrid: EX13000E v220.127.116.11
The case was opened because backups for a Backup Job randomly went missing under Disks -> Backups.
Opening up the status for the job the following warning showed.
The Veeam support person soon realized that our Backup Copy jobs were going to the exact same location (Exagrid share) to their relevant Backup Jobs and was concerned. I said it was configured this way because deduplication on a Exagrid is done by share and because KB2056
Our repository configuration
The Veeam support person did some research and found there was a known major bug between Veeam and Exagrids where backup files would lose their association with a backup job. We then looked at Backup -> Backup (imported) and found it completely flooded with backup jobs (even ones that had run the night before).
He then installed a Veeam patch (file replacement), Veeam.Backup.Core.dll (MD5 1C0BD7AD1153151B1386F8C7C6F2E976).
The backup jobs that ran last night have gone directly to Disk (imported) (as they were doing before), however, this time the backup is also showing in the normal backup area? So I guess the patch made some sort of difference.
The Veeam support person said they think we haven't lost any data however we could not restore the data in the normal way, we have to manually copy the backup files out of the Exagrid repository which is not a great situation if you were planning to use Instant VM Recovery. The boss isn't happy as we have $100,000 in Veeam licensing / support.
I believe the Veeam support person is doing everything possible to help and I have no complaints, I just thought I'd post it here to get some feedback from engineers (any ideas as to what the issue may be?) as I'm stressing about the accessibility of our backup data. Very worried.