@Hirosh
Veeam can only report that it is waiting on data from the Catalyst client. It does not report where the bottleneck is beyond the Catalyst Client.
Based on your description of your configuration, the bottleneck is likely to be the network between the Catalyst Client (inside Veeam Gateway) and the Catalyst Server (inside the StoreOnce). It is not unusual for us to find issues in customer FC SAN configurations resulting in sub-optimal performance.
The only way to progress this issue is to find the source of the bottleneck and see how it can be fixed, which means raising a support case with HPE support. They can analyse the Catalyst logs, and work with you to run diagnostic tools, to determine where the bottleneck is and work out how it can be fixed.
Veeam can only report that it is waiting on data from the Catalyst client. It does not report where the bottleneck is beyond the Catalyst Client.
Based on your description of your configuration, the bottleneck is likely to be the network between the Catalyst Client (inside Veeam Gateway) and the Catalyst Server (inside the StoreOnce). It is not unusual for us to find issues in customer FC SAN configurations resulting in sub-optimal performance.
The only way to progress this issue is to find the source of the bottleneck and see how it can be fixed, which means raising a support case with HPE support. They can analyse the Catalyst logs, and work with you to run diagnostic tools, to determine where the bottleneck is and work out how it can be fixed.
Statistics: Posted by pcan — Mar 11, 2024 10:08 am
