Could this be the same rogue snapshot problem encounterd when there is a long delay between the 'Using source proxy...' and 'Preparing guest for hot backup...' stages?
If so, it's likely that the there are references in the Veeam table VmWare.Snapshots to non-existent snapshots.
This causes a 30 sec delay between every attempt in Veeam to access the non-existent snapshot files. It can't find the snapshot then moves onto the next one. And it happens for every job! So if you have 60 references it creates a 30 minute delay between the two stages 'Using source proxy...' and 'Preparing guest for hot backup...'. So if you have 40 backup jobs that adds 20 hours to the backup time!
Shutdown Veeam services
Fire up MS SQL Server Express/Management Studio 2005/2008 (or whatever version you're using) and execute the SQL:
- Code: Select all
DELETE FROM VeeamEM.dbo.VmWareSnapshots
If it reports a number of rows deleted then there were references to rogue snapshots.
Hope that helps.