Host-based backup of Microsoft Hyper-V VMs.
Post Reply
JohnDanger
Lurker
Posts: 2
Liked: never
Joined: May 03, 2017 11:16 pm
Full Name: Richard B
Contact:

One VM SLOW after upgrade

Post by JohnDanger »

I just upgraded to B&R 9.5.
I have 3 hyper-v hosts with 5 Vms that I backup with Veeam.

After the upgrade to 9.5, my backup's of an Exchange 2010 VM is unusable, extremely slow.
It's the only VM on that particular Host.
1mb /per sec or LESS!!!!

My other VM's seem to be ok.

Any suggestions?
Dima P.
Product Manager
Posts: 14716
Liked: 1702 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: One VM SLOW after upgrade

Post by Dima P. »

Hello and welcome to the community Richard,

Please clarify the bottleneck stats for the Exchange job? Thanks.
JohnDanger
Lurker
Posts: 2
Liked: never
Joined: May 03, 2017 11:16 pm
Full Name: Richard B
Contact:

Re: One VM SLOW after upgrade

Post by JohnDanger »

It says that the bottleneck is the network but all my VM backups go over the same network infrastructure, except the physical hosts nics of course. Nothing has changed with that regard though.
Mike Resseler
Product Manager
Posts: 8191
Liked: 1322 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: One VM SLOW after upgrade

Post by Mike Resseler »

Hi Richard,

So if I understand correctly, it is only that specific VM that is running on one Hyper-V host. All the other VMs on the two other hosts are still getting the normal speed. Correct?

Since VBR states that the bottleneck is the network, I would believe something has changed over there. So can you look at the following:

* Any windows installed (exchange server/ hyper-v host) that are not installed on the other servers (or vice versa)
* Difference in firmware for the NIC on the physical box?
* Can you use IPERF or Wireshark to test the speed between the VBR box and the VM?
* Nothing else that has changed just before you started seeing the issue?

If the output of IPERF or Wireshark is normal, then please log a support call. Maybe our engineers can figure out what is exactly wrong. We had many cases where an update, wrong NIC driver/ firmware or similar was causing the issue
thanks
Mike
Post Reply

Who is online

Users browsing this forum: Semrush [Bot] and 25 guests