Replication: VMware to VMware
Source Linux proxy: Direct storage access (NFS)
Destination Linux proxy: Virtual appliance
Job says bottleneck is "Proxy" but which one? When I check CPU/RAM/IO, I see very little consumption. How do I identify which proxy is the bottleneck so at least I can dig into it more closely?
-
TitaniumCoder477
- Veteran
- Posts: 316
- Liked: 48 times
- Joined: Apr 07, 2015 1:53 pm
- Full Name: James Wilmoth
- Location: Kannapolis, North Carolina, USA
- Contact:
-
Andreas Neufert
- VP, Product Management
- Posts: 7081
- Liked: 1511 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
-
TitaniumCoder477
- Veteran
- Posts: 316
- Liked: 48 times
- Joined: Apr 07, 2015 1:53 pm
- Full Name: James Wilmoth
- Location: Kannapolis, North Carolina, USA
- Contact:
Re: Which proxy is the bottleneck?
Ummm... thanks for a KB I already read? I am posting here for clarification because it says, "Proxy — backup proxy component responsible for processing VM data," but both proxies are involved unless the keyword is "processing" and would refer to source side proxy?
-
Gostev
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
-
foggy
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Which proxy is the bottleneck?
...as the keyword 'Target' refers to the 'target disk writer component (backup storage or replica datastore)'.
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 42 guests