Discussions specific to the VMware vSphere hypervisor
Post Reply
tomerl
Novice
Posts: 9
Liked: never
Joined: May 08, 2013 7:00 am
Full Name: Tomer Leibovich
Contact:

Veeam network configuration

Post by tomerl » Jan 01, 2014 12:53 pm

Hi,
We need to backup very large VM's (7TB each) and noticed that most of the time the backup job (Full) is extremely slow (30MB/s) due to network bottleneck.
This led us to check our network and indeed copying files over the network takes the same time, so we tested large file copy on Private VLAN and reached 400MB/s.
The question is what do we need to do in order to have Veeam work with this VLAN?

My infrastructure for clear understanding is:
VLAN 10 (192.168.10.x)
vCenter (192.168.10.100)
VBR (All-in-one server) - 192.168.10.32
Proxy1 (proxy server) - 192.168.10.35
Proxy2 (Repository and Proxy) - 192.168.10.34

Private VLAN (11) - 192.168.11.x

My guess is that the VBR server will be connected to the new network, change the network for the proxy and the repository to VLAN 11 and disable VBR as proxy and repository so all the backups will be on the other VM's.
Am I correct on this?

Gostev
SVP, Product Management
Posts: 24612
Liked: 3458 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Veeam network configuration

Post by Gostev » Jan 01, 2014 2:46 pm

Hello, yes you are correct. You can even keep proxy and repository on VBR, as you said your VBR server will also be connected to the new network. But make sure that
DNS names of all involved servers resolve to private VLAN IP address (unless you registered them all with B&R by private VLAN IP). Thanks!

tomerl
Novice
Posts: 9
Liked: never
Joined: May 08, 2013 7:00 am
Full Name: Tomer Leibovich
Contact:

Re: Veeam network configuration

Post by tomerl » Jan 01, 2014 2:48 pm

Great, thanks!

tomerl
Novice
Posts: 9
Liked: never
Joined: May 08, 2013 7:00 am
Full Name: Tomer Leibovich
Contact:

Re: Veeam network configuration

Post by tomerl » Jan 01, 2014 3:14 pm

Hmmm...well something is not working now.
I've done as suggested here but now I'm getting the following error:

1/1/2014 5:10:00 PM :: Error: Client error: Cannot get service content.
Soap fault. No DataDetail: 'get host by name failed in tcp_connect()', endpoint: 'https://vcenter:443/sdk'
SOAP connection is not available. Connection ID: [vcenter].
Failed to create NFC download stream. NFC path: [nfc://conn:vcenter,nfchost:host-7395,stg:datastore-147@XMBX02/XMBX02.vmx].

The VBR server is connected to 2 networks:VLAN 10 and VLAN1 and it is being able to connect to the vcenter.
Only servers that cannot reach the vcenter are the proxy servers.

I can connect another NIC on VLAN10 to the proxy, but I want the transport to work only on the private VLAN.

Update:
Turns out that I needed the proxy to be able to resolve the vcenter.
Got things working faster, 2 disks simultaneously, disk@80mb/s. Current bottleneck is target, any advice what can be done to speed it up?
If I will create the repository with RDM will it work faster?

Gostev
SVP, Product Management
Posts: 24612
Liked: 3458 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Veeam network configuration

Post by Gostev » Jan 01, 2014 6:13 pm

Glad you've got this working. The only way to speed up backup target is to use a faster storage device.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 13 guests