Slow backup via Direct SAN Access

[valneimelo]

Hi All,

I've run into a performance problem with my backup jobs.

My infrastructure is:

17 VMware hosts with ESXi 6.7 within 2 HPE Synergy 12000 connected to a Nexus SAN switch using 40GbE;;
2 Storages HP 3PAR 8200, one on each datacenter connected to a Nexus SAN switch using 16Gb FC;
The backup repository is a HPE StoreOnce 5100 connected to a Nexus SAN switch using 8Gb FC, this repository can be rescaned by Veeam in aproximatelly 20secs;

The Veeam B&R 9.5 Update 4b running on a physical machine HPE DL380p Gen8 (16 CPUs) with Windows 2016 Server. This machine is the proxy, gateway and media server.

I'd like to use direct SAN Access but the backup always take long time on the step like this: "Hard disk 4 (0.0 B) 0.0 B read at 0 KB/s [CBT]" then after took long time on this step for each disk, the backup finish successfully with processing rate between 50 MB/s and 90 MB/s.

3PAR and Veeam Backup server is zoned, I can see all LUNs on the Disk Managment;
StoreOnce and Veeam Backup server is also zoned on SAN switch;
Is there any zoning missing?

Any idea how to get shorter backup times?

Thank you for your help and let me know if you need further details.

[PetrM]

Hello Valnei,

I think debug logs analysis is required and may be some performance tests to figure out the root cause.
I suggest to open a support request and provide us with case number.

However, what is a speed in other transport modes and what is the "bottleneck" according to job session statistics?

Thanks!

[valneimelo]

Hi PetrM,

I've opened the case #03905841.
The bootleneck is always the "Source". See the example below:

Load: Source 98% > Proxy 9% > Network 5% > Target 3%

Using other transport modes the speed is much better.

Thanks for your reply.

[PetrM]

Ok, you can use another transport mode as temporal workaround while the case is under investigation.

Thanks!

[Ollo]

any solutions found?

[PetrM]

Hello,

Slow read is SAN mode can have different root causes depending on infrastructure specific and used hardware.
I'd recommend to contact our support team in order to continue troubleshooting.

Thanks!