Block Storage

Hello everyone,

Can someone provide an answer regarding the following:

An array was configured using Fibre Channel (FC) ports CL3-A and CL4-A on the Veeam resource. Each port is connected to an independent fabric (one fabric per port). It was also verified that all zoning is correctly configured.

Twenty unused LDEVs were added to the VBR_Veeam resource, associating them with ports CL3-A and CL4-A, as well as the corresponding host groups (VBR_proxy). Subsequently, integration with Veeam was performed.

A Linux proxy is being used, which also has multipath configured. Backup tests were then run using BFSS (Backup from Storage Snapshots), which completed successfully.

However, it was identified that provisioning the auxiliary volume to the proxy server is only being done through port CL4-A, without using the other available path (CL3-A).

Note: In all jobs, always use port CL4-A. If I disable port CL4-A and run the Jobs, they remain in a waiting state and never start.

My question is: Is this behavior expected, or should I be using both paths (CL3-A and CL4-A) to optimize the backup process? Or is any additional configuration needed at the storage, Linux proxy, or Veeam level to use both paths during BFSS backup execution?

Best regards.