Jobs failing after moving/replacing CSVs

[joserizal]

Hello all,

We yesterday replaced the CSVs in 2 of our SANs, copying over all the data to the new volumes and ensuring volumes had nothing on them before removing. Veeam seems to have picked this up automatically as going into Manage Volumes on the clusters in Backup Infrastructure shows the new volumes, however just about every VM running on those clusters has failed in their backup job, with error "System cannot find the path specified. Failed to open file [FILEPATH POINTING TO OLD VOLUME GUID] in readonly mode. Failed to open file [FILEPATH POINTING TO OLD VOLUME GUID] for reading." It looks to be trying to find the old volume still based on the GUID it is displaying. However the logs seem to find the object in the correct location.

[22.12.2016 10:03:37] <24> Error Failed to add backup object. Path: [FILEPATH POINTING TO NEW VOLUME] (Veeam.Backup.Common.CRegeneratedTraceException)

[22.12.2016 10:03:37] <24> Error File2Text failed (Veeam.Backup.Common.CAgentException)

[22.12.2016 10:03:37] <24> Error Failed to open file [FILEPATH POINTING TO OLD VOLUME GUID] in readonly mode. (Veeam.Backup.Common.CCppComponentException)

I have tried rescanning each of the hosts on the cluster and going into Manage Volumes > Rescan in Veeam Backup Infrastructure as well as refreshing the hosts and VMs in SCVMM. Does anyone have any ideas?

Case # 02017355

[foggy]

How have you swapped the volumes and copied VMs to the new volumes? Looks like links to the old volumes still exist somewhere in VM configuration, which wouldn't be the case if you used native export/import or migration.

[joserizal]

Potentially may have been resolved with a restart of the virtual hosts (tested restarting one and migrating a VM to it which has worked).. scheduling to have them all restarted which will hopefully get things back on track.