Hi GabesVirtualWorld,
Unfortunately won't be able to tell why the backup failed specifically without a Support Case and a review of the debug logs.
However, I get that you're more about what is the best process for such upgrades here -- Veeam does periodic full rescans of the VMware environment and caches a lot of the information during incremental scans. But I'm doubtful that it's a best idea to try to time the rescan correctly, and instead probably setting a maintenance window for the backups would be best (gracefully shut down the backup server or simply disable the jobs (you can shift + click to select them all and then right-click and disable)
Once the maintenance on the VMware environment is done, then rescan the vCenter and re-enable the jobs.
Edit: fwiw, without seeing the logs and just that brief error you posted, my guess is the vcsa migrated between hosts and some lookup failed, but purely a guess.
Unfortunately won't be able to tell why the backup failed specifically without a Support Case and a review of the debug logs.
However, I get that you're more about what is the best process for such upgrades here -- Veeam does periodic full rescans of the VMware environment and caches a lot of the information during incremental scans. But I'm doubtful that it's a best idea to try to time the rescan correctly, and instead probably setting a maintenance window for the backups would be best (gracefully shut down the backup server or simply disable the jobs (you can shift + click to select them all and then right-click and disable)
Once the maintenance on the VMware environment is done, then rescan the vCenter and re-enable the jobs.
Edit: fwiw, without seeing the logs and just that brief error you posted, my guess is the vcsa migrated between hosts and some lookup failed, but purely a guess.
Statistics: Posted by david.domask — Sep 04, 2025 8:54 am
