Comprehensive data protection for all workloads
Post Reply
aschalk
Enthusiast
Posts: 31
Liked: 1 time
Joined: Sep 07, 2016 5:47 am
Contact:

Network Mode slow

Post by aschalk »

Hey Guys,

currently we are trying to set up Veeam Backup in our Environment.
Most of our VMs have VMDKs, which reside on SAN Storage.
For that we use a virtual job server and a physical proxy server and configured Direct Storage Access.
We also configured separte VLAN only for backup + plus own network components between the involved components to not interfere with production network.
It's working really great so far.

Some VMs however use storage from a NAS system. In this case backups are configured to
fall back to Network Mode. But the throughput is rather bad. The maximum read was about 85MB/s.

We configured vmkernel interface on the ESX Servers, put them in the backup VLAN and gave them one 10G interface each.
A Ping from the Proxy to the configured vmkernel interface of the ESX Servers works.
tracert reveals that no additional hops are involved.
Additonally I edited the hosts file on the proxy and the job server, and inserted the vmkernel ips + Hostname of the respective ESX Server.

Did we miss somthing?
aschalk
Enthusiast
Posts: 31
Liked: 1 time
Joined: Sep 07, 2016 5:47 am
Contact:

Re: Network Mode slow

Post by aschalk »

Support Case # 02114621
foggy
Veeam Software
Posts: 21139
Liked: 2141 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Network Mode slow

Post by foggy »

What are the bottleneck stats for those slow jobs? If it is source, then the NAS device isn't just able to provide data any faster.
aschalk
Enthusiast
Posts: 31
Liked: 1 time
Joined: Sep 07, 2016 5:47 am
Contact:

Re: Network Mode slow

Post by aschalk » 1 person likes this post

Bottleneck was indeed the source, but is was primarly due to a bad configured connection between esx and nas over iscsi. The ports were configured to use only 1G although they can handle 10G.
We switched them to 10G and now only the disks of the NAS are the bottleneck. But this is nothing veeam can help with i guess :-).
Post Reply

Who is online

Users browsing this forum: Sagindyk, sdv and 119 guests