-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 10, 2010 4:07 am
- Full Name: Andy Roberts
- Contact:
Hot add is not supported for this disk since update
Hi,
Have been using Veeam for about 10 months now without any problems, works great! I was running it on a 2003 R2 VM and using the Virtual Appliance backup method to backup all my VMs and they always completed OK without errors.
A couple of weeks ago though, for some reason my VM just wouldn't mount the iSCSI drives anymore, kept giving driver errors and no matter what I did I couldn't get it to mount. So I ended up getting rid of the VM and rebuilding a new one, this time with 2008 R2 and the latest version of Veeam (5.0.2.230 64bit) where before I was on the previous version. This connected fine and I set all my jobs up the same and all good, the backups complete.
Now however, despite every job completing OK and in the same time frame/speed, each jobs shows up
Hot add is not supported for this disk, failing over to network mode...
Like I say, the speed/time hasn't changed so I'm not sure why this is coming up. Could it be it was always failing over before but just not logging it? If so is there a way I can try and stop it failing over to see if I can eeak out a bit more performance from the backups?
Thanks!
Andy
Have been using Veeam for about 10 months now without any problems, works great! I was running it on a 2003 R2 VM and using the Virtual Appliance backup method to backup all my VMs and they always completed OK without errors.
A couple of weeks ago though, for some reason my VM just wouldn't mount the iSCSI drives anymore, kept giving driver errors and no matter what I did I couldn't get it to mount. So I ended up getting rid of the VM and rebuilding a new one, this time with 2008 R2 and the latest version of Veeam (5.0.2.230 64bit) where before I was on the previous version. This connected fine and I set all my jobs up the same and all good, the backups complete.
Now however, despite every job completing OK and in the same time frame/speed, each jobs shows up
Hot add is not supported for this disk, failing over to network mode...
Like I say, the speed/time hasn't changed so I'm not sure why this is coming up. Could it be it was always failing over before but just not logging it? If so is there a way I can try and stop it failing over to see if I can eeak out a bit more performance from the backups?
Thanks!
Andy
-
- Chief Product Officer
- Posts: 31793
- Liked: 7295 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Hot add is not supported for this disk since update
Hi Andy, I believe that logging of this event was not in the product originally. So in earlier versions, the engine simply would not notify you about failover happening, but just failover silently.
The list of reasons why hot add may fail are listed in the sticky FAQ topic, if you can identify and remove the reason, then hot add should start working for this VM.
Thanks!
The list of reasons why hot add may fail are listed in the sticky FAQ topic, if you can identify and remove the reason, then hot add should start working for this VM.
Thanks!
-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 10, 2010 4:07 am
- Full Name: Andy Roberts
- Contact:
Re: Hot add is not supported for this disk since update
Awesome, thanks for the quick reply Gostev. Suspected it might have been a silent failover but thanks for confirming. I'll have a dig through the sticky and see if I can trace the cause.
Thanks!
Thanks!
-
- Novice
- Posts: 9
- Liked: never
- Joined: Feb 01, 2012 2:08 pm
- Full Name: Chris Tolhurst
- Contact:
Hot Add Not Supported
[merged]
Can anyone tell me what this warning means on my backup jobs? "Hot add is not supported for this disk, failing over to network mode..." I am running v6 with patch 2
Thanks
Chris
Can anyone tell me what this warning means on my backup jobs? "Hot add is not supported for this disk, failing over to network mode..." I am running v6 with patch 2
Thanks
Chris
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Feb 07, 2012 1:29 pm
- Contact:
Re: Hot add is not supported for this disk since update
I have the same problem.
Installed version : v6 + HF2 = build 164
HotAdd always failed !!
Does anyone have a solution ?
Installed version : v6 + HF2 = build 164
HotAdd always failed !!
Does anyone have a solution ?
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Hot add is not supported for this disk since update
Please read carefully through the Anton's post above.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Feb 08, 2012 10:28 am
- Full Name: Martin Jønch
- Contact:
Re: Hot add is not supported for this disk since update
Anton? Do you mean Andy? I still see no answer ...
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Hot add is not supported for this disk since update
And here is the direct link to that FAQ section.Gostev wrote:The list of reasons why hot add may fail are listed in the sticky FAQ topic, if you can identify and remove the reason, then hot add should start working for this VM.
-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 10, 2010 4:07 am
- Full Name: Andy Roberts
- Contact:
Re: Hot add is not supported for this disk since update
I haven't fixed my issue yet either, but being honest I haven't had time to look at it that much. The backups are working even with the hot add error, and are going the same speed as on the previous version when i didn't get the error, so I'm happy to leave it at that for the time being until I get more time being a 1 man IT sys admin for 60 users and 80 servers.
I think though my problem might be -
• LUN with Veeam Backup server is located should have capacity more than (or equal) the capacity of the disk which is being hot added. Actual free space can be less than hot added virtual disk size.
As I have my Veeam VM on a management LUN which is only 100Gb but only around 10Gb free of provisioned space, 40gb free actual, so I guess this might be the cause. Will confirm if I ever get chance.
I think though my problem might be -
• LUN with Veeam Backup server is located should have capacity more than (or equal) the capacity of the disk which is being hot added. Actual free space can be less than hot added virtual disk size.
As I have my Veeam VM on a management LUN which is only 100Gb but only around 10Gb free of provisioned space, 40gb free actual, so I guess this might be the cause. Will confirm if I ever get chance.
Who is online
Users browsing this forum: No registered users and 48 guests