Backup extremly slow

[jo_biblio]

Hi,

case ID : 04938670

We just got a new host server for our VMs and I installed Veeam Community Edition.

At the moment, we have 3 VMs on the server (only 2 need a backup).

The first is named 'SRVPRINT', I did a backup and it worked fine. (the warning doesn't matter, I just need to upgrade the VM hardware to version 8.0 or later, I will do it later).


But for the second named 'SRVWEB', first I had a 'Access refused', I had to use this commande : icacls "E:\Hyper-V\SRVWEB\Virtual Hard Disks\SRVWEB.vhdx" /grant "NT VIRTUAL MACHINE97c30cb-b2db-4f42-a290-938fc3d7c163":(F)
And now I don't have the access error anymore, the backup is very very slow compared to the 'SRVPRINT'. The job lasted 16 minutes for 'SRVPRINT', and here, after 2h for 'SRVWEB', it's still at 2%.


The configuration is the same for both job.
The volume is almost the same too.

And it's not a Hyper-V cluster. Is there an explanation?
(Sorry, my english isn't so good and I am a beginner with Hyper-V/Veeam)

Thank you !

[Egor Yakovlev]

Hi Jonathan,

Based on screenshot your job's bottleneck is Target, so that would be first thing to check.
You can select VM in Statistics window and that will reveal more detailed log on processing speed per disk.

/Thanks!

[jo_biblio]

Do you mean this window?


And what's the target?
The Veeam's server or the NAS I use to store backups?

[Vitaliy S.]

That's the NAS device. Can you please share how did you register it in VBR, as a CIFS share?

[jo_biblio]

In my Backup repositories, I see the type "SMB". And when I'm connected to my NAS, I see a CIFS connection between the NAS and the Veeam's server

[jo_biblio]

By the way, the old system is still running and it works.

New system = Host WS 2019 with Veeam (version 8.0) and Hyper-V (2 VMs -with backup job- on it for the moment)
Old system = Host WS 2012 R2 with Veeam (version community edition) and Hyper-V (3 VMs -with backup job- on it for the moment)
The same backup repository is used.

I tried to replicate Veeam's configuration from old to new server. (I mean that I did it by hand, I didn't use a .bco file)

[PetrM]

Hello,

It's worth checking the gateway server that is used to write data to NAS, probably it would make sense to have a static gateway server that is located as close to the backup repository as possible.

Thanks!

[jo_biblio]

Hi,

Thank you for your answer !

We don't use a gateway server in our infrastructure. I don't know if it's necessary in our case because the last configuration wasn't using a gateway server.

But I found something... Sending data from the server to anything on the network is low (even if I use a Windows shared folder). So I think the problem is caused by the server and it's not about Veeam or my NAS.
The problem is that I don't know how to fix it... I will make a search

[PetrM]

Hello,

The gateway server is always used with SMB/NFS repositories as we need a server on which the target Data Mover will be running. The gateway server can be selected either automatically or manually. Anyway, I believe you're on a right way and the source of the issue is related to network performance.

Thanks!

[jo_biblio]

Hello !

I found anything but I need to see over a longer time if it works or not...

I had to disable "Large Send Offload (LSO)" in my network adaptater
https://docs.microsoft.com/en-us/answer ... sting.html

I made full backups yesterday and incrementials this night and I have success jobs.

I will not rejoice too quickly, last week it worked only tuesday.

Let's see...

Thank you for you help !