Every once in a while all of my backup jobs will start returning "Hot add is not supported for this disk, failing over to network mode..." for every VM in each job. If I reboot the Veeam Server, the error ceases to occur. It has happened twice now, so it still feels random, but I'm sure it's not a random thing.
The Veeam server is the proxy and repository server, writing to local Windows disks. vCenter is 5.0 U1, but the hosts are currently ESX4.1 U1.
Has anyone encountered this?
-
jadams159
- Enthusiast
- Posts: 80
- Liked: 4 times
- Joined: Apr 16, 2012 11:44 am
- Full Name: Justin Adams
- Location: United States
- Contact:
-
tsightler
- VP, Product Management
- Posts: 6035
- Liked: 2860 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
- Contact:
Re: Hot add error on all jobs, rebooting Veeam server fixes
I think you are describing the same issue that is discussed here. Typically hot add starts failing after performing any file level recovery or instant recovery and will resume after a reboot. I believe this is actually being triggered by a bug in the vStorage API but support has a hotfix available that implements a workaround for this issue.
Who is online
Users browsing this forum: Bing [Bot], fspadaro, Google [Bot], RocketSam, Semrush [Bot], veremin and 11 guests