Opened a case on this, 02090539, but wanted to post here to see if anyone else has seen this.
We utilize the Nimble snapshot integration for some of our backups. Basically just point Veeam Backup server at our SAN and then use it to crack open Snaps and do FLRs, etc.
Works well for the most part, however today we've run across a situation where Veeam has incorrectly identified the location of the snapshot data. The VM resides on 'volume 12' in vCenter. Veeam, after indexing the snaps, thinks the VM is on 'volume 02'. If you do a restore, it fails, because the data isn't on that volume.
This is happening to a number of VMs where Veeam has incorrectly identified their snap volume location on the Nimble array. The more we dig and cross-reference, the more we find in Veeam with incorrect volume locations.
Has anyone run into this? We've done full rescans of the Nimble and its volumes from inside Veeam and it never seems to sort itself out.