Hello Guys,
I've just noticed a trange beawiour on my new veeam setup.
I've two physical proxy accessing production storage in direct SAN and both acting as a gateway for a DDBoost over fc repository.
Sometimes some session have the data ridden from proxy A and written by proxy B - this is expected.
both proxy are connected to a 20Gbit LACP PO and iperf is performing correctly.
when this situation happen i saw lots of discarded packet and retransmit at the NIC level:
but the backup is perfoming well, with about 600MBps average throughput.
I'm assuming that discarded packet might be caused by the fack that reding from the production storage is way faster that writing on the dedupe appliace,
some buffer eventually get full and the receiving proxy start discarting packet.
Can anyone confirm that this is an "expected behaviour" and we can ignore this?
Thanks
L
I've just noticed a trange beawiour on my new veeam setup.
I've two physical proxy accessing production storage in direct SAN and both acting as a gateway for a DDBoost over fc repository.
Sometimes some session have the data ridden from proxy A and written by proxy B - this is expected.
both proxy are connected to a 20Gbit LACP PO and iperf is performing correctly.
when this situation happen i saw lots of discarded packet and retransmit at the NIC level:
Code:
PS C:\Users\f56945a_adm> netstat -eInterface Statistics Received SentBytes 1475080611 1108576590Unicast packets 2652122594 3973294747Non-unicast packets 1330555 26870Discards 5452026 0Errors 0 0Unknown protocols 0PS C:\Users\f56945a_adm> netstat -s -p tcpTCP Statistics for IPv4 Active Opens = 2060 Passive Opens = 951 Failed Connection Attempts = 39 Reset Connections = 1119 Current Connections = 107 Segments Received = 264737393 Segments Sent = 709599594 Segments Retransmitted = 83710061I'm assuming that discarded packet might be caused by the fack that reding from the production storage is way faster that writing on the dedupe appliace,
some buffer eventually get full and the receiving proxy start discarting packet.
Can anyone confirm that this is an "expected behaviour" and we can ignore this?
Thanks
L
Statistics: Posted by maol — Feb 17, 2024 4:25 pm
