-
- Novice
- Posts: 3
- Liked: never
- Joined: Jun 28, 2016 3:47 pm
- Contact:
Proxy Server - Direct SAN slow read
Case # 03105878
Hello,
We are experience slow performance working with Physical Proxy Server, Windows Server 2016 (12CPU/96GB RAM). It reads VMDK files at 10 to 15 MB/s. Its
connected to HP 3PAR 7200 with two 8GB HBAs.
99% Source Bottleneck
#Infrastructure#
1 vCenter Server Appliance 6.0
4 ESXi hosts 6.0
(1) Backup Server 9.5U3 (8vcpu, 16GB RAM) - NET 1GB
(2) Proxy Server: One Physical (12core 96GB RAM) with 2 HBA(8GB) connected to HP 3PAR 7200, One Virtual (12vcpu, 16GB RAM)
(1) Repository Server: Virtual (12vcpu, 16GB RAM) with a REFs 64k partition - NET 1GB
Hello,
We are experience slow performance working with Physical Proxy Server, Windows Server 2016 (12CPU/96GB RAM). It reads VMDK files at 10 to 15 MB/s. Its
connected to HP 3PAR 7200 with two 8GB HBAs.
99% Source Bottleneck
#Infrastructure#
1 vCenter Server Appliance 6.0
4 ESXi hosts 6.0
(1) Backup Server 9.5U3 (8vcpu, 16GB RAM) - NET 1GB
(2) Proxy Server: One Physical (12core 96GB RAM) with 2 HBA(8GB) connected to HP 3PAR 7200, One Virtual (12vcpu, 16GB RAM)
(1) Repository Server: Virtual (12vcpu, 16GB RAM) with a REFs 64k partition - NET 1GB
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: Proxy Server - Direct SAN slow read
Hi esozio and welcome to the community!
Based on the bottleneck stats the issue comes from the source storage disk, as it means that the job spent most of the time on reading the data from storage.
You can review the sticky thread for additional information.
Please continue the investigation with the support team. Thanks!
Based on the bottleneck stats the issue comes from the source storage disk, as it means that the job spent most of the time on reading the data from storage.
You can review the sticky thread for additional information.
Please continue the investigation with the support team. Thanks!
-
- Novice
- Posts: 3
- Liked: never
- Joined: Jun 28, 2016 3:47 pm
- Contact:
Re: Proxy Server - Direct SAN slow read
Hi, DGrinev
The extrange thing is that now we change the repository (a simple Windows share) and the performance it's a lot better (150 MB/s)...but still not good enogout for direct san read access.
The extrange thing is that now we change the repository (a simple Windows share) and the performance it's a lot better (150 MB/s)...but still not good enogout for direct san read access.
-
- VeeaMVP
- Posts: 1007
- Liked: 314 times
- Joined: Jan 31, 2011 11:17 am
- Full Name: Max
- Contact:
Re: Proxy Server - Direct SAN slow read
Are the drivers and firmware of your backup server up to date?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Proxy Server - Direct SAN slow read
Can you please check the job session and make sure direct SAN is actually used (there's a [san] tag after the proxy server name)?
-
- Novice
- Posts: 3
- Liked: never
- Joined: Jun 28, 2016 3:47 pm
- Contact:
Re: Proxy Server - Direct SAN slow read
Yes foggy it´s working with direct [san]. Any ideas?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Proxy Server - Direct SAN slow read
I'd look at this from the storage perspective, provided the job reports source to be primary bottleneck.
-
- VeeaMVP
- Posts: 1007
- Liked: 314 times
- Joined: Jan 31, 2011 11:17 am
- Full Name: Max
- Contact:
Re: Proxy Server - Direct SAN slow read
I'm quoting myselfRegnor wrote:Are the drivers and firmware of your backup server up to date?
I've had some cases were old drivers or firmware on HPE equipment were causing performance issues. Please also try to set your server to high performance in the BIOS energy settings.
Who is online
Users browsing this forum: No registered users and 51 guests