Hi everyone,
I'm having the following setup
So far so good, I don't expect the performance to be fantastic, it just should work. To my big surprise, the stats in the backup job say that "proxy" is the bottleneck - how could that be? It should be clearly the network. Is it just a misinterpretation or is it true??
Thanks!
-
- Veeam Legend
- Posts: 851
- Liked: 180 times
- Joined: Jul 19, 2016 8:39 am
- Full Name: Michael
- Location: Rheintal, Austria
- Contact:
-
- Veeam Software
- Posts: 3264
- Liked: 528 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: bottleneck proxy when it should be network?
Hi Michael,
Please open a support case and ask our engineers to analyze logs and performance statistics from all nodes of the backup infrastructure. I cannot make any conclusion based on the diagram above only but the word "proxy" here most likely means the source server load (on which VAW is running) as the main compute operations (f.g. compression) are carried out on this server.
Also, don't forget to share a support case ID.
Thanks!
Please open a support case and ask our engineers to analyze logs and performance statistics from all nodes of the backup infrastructure. I cannot make any conclusion based on the diagram above only but the word "proxy" here most likely means the source server load (on which VAW is running) as the main compute operations (f.g. compression) are carried out on this server.
Also, don't forget to share a support case ID.
Thanks!
Who is online
Users browsing this forum: No registered users and 9 guests