Slow backup

[berlie]

Good day

We have 2 core servers, When you run backups from the server veeam is installed on its fast but when you run backup from the other core its extremely slow.
We are using a SAN.

Any ideas

[DGrinev]

Hi Grant,

Can you please tell us your bottleneck stats for both job runs? Also, provide a brief description of the backup infrastructure. If I get it right, you are using Direct SAN Access mode?

Thanks!

[berlie]

Hi we have 2 windows 2012 servers and we are running 2 vms on both of them. If we do backup on first server then it runs at 60mb/s. But on second machine its 2mb/s.

If you move the vm to the fist machine from second it backups at 60 move it back to second 2. The 2 servers is exactly the same the only difference is that first one is connected to the backup device with scsi cable. Bottleneck is source.

[foggy]

Does the slower job also report bottleneck as source?

[berlie]

Yes . So basically when you run a backup from the server locally or from a vm on the server its slow. But if you do it on the other server its fast.

[Delo123]

Probably your second host is swithing to NBD (network backup mode) and using some slow link. Maybe you can Hot-add (it would use your veeam server as proxy).
Maybe read this first: https://helpcenter.veeam.com/backup/80/ ... iance.html and have a look what the job stats are telling you on the right side.

[berlie]

Now both is slow again

[Delo123]

Could you post a screenjob/info of the job actions gui? things like:
- which proxy is being used (is this the right machine? It should be the one with the "best" connections to source and destination)
- which transport method is being used? like [NDB] or [SAN Direct]
- is CBT being used? (you should be able to read this next to the disk read speeds)
- Bottleneck stats: It will say Busy: Source,Proxy, Network, Target. How are these values?

Probably a shot in the dark, but could it be you have tried to configure jumbo frames? Not doing this everywhere can lead to very strange results / performance

[foggy]

(Guido, this is Hyper-V, if I'm getting the OP right.)

Try to copy some large file to the same target server from both hosts and compare performance.

[mpark]

Try file copy to both hosts as foggy's suggestion above. Feels like either of the following scenario seems applicable:
1. Assuming you are using a gigabit connection on the first host, your connection from the second host (slow one) to the SAN may not be using gigabit connection, rather 100mbit. Depending on the switch you have you may want to review your port settings.

2. Host 2 has more than one network connection connected and Veeam is using the slower connection somehow. If this is the case, try setting the throttling to only allow connection from the larger pipe connection from the second host.