Discussions specific to the VMware vSphere hypervisor
Post Reply
Posts: 80
Liked: 4 times
Joined: Apr 16, 2012 11:44 am
Full Name: Justin Adams
Location: United States

Hot add error on all jobs, rebooting Veeam server fixes it.

Post by jadams159 » Apr 16, 2012 11:54 am

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?

VP, Product Management
Posts: 5338
Liked: 2185 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler

Re: Hot add error on all jobs, rebooting Veeam server fixes

Post by tsightler » Apr 16, 2012 12:14 pm

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.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], redhorse and 19 guests