Is your feature request related to a problem? Please describe?
Currently, XCOPY-based migrations only support SCSI-attached storage across all vendors. Fibre Channel (FC) storage is not supported, which prevents customers using FC SAN environments from leveraging XCOPY-based migrations.
This ticket proposes adding Fibre Channel support for XCOPY operations so that migrations can run efficiently in FC-backed environments.
Detailed Description
The current implementation assumes SCSI-backed devices for XCOPY-based migrations. Many enterprise environments use Fibre Channel SAN storage, particularly with Pure Storage arrays.
Because FC devices are not currently supported:
XCOPY-based migrations fail or are skipped.
Customers using FC storage cannot take advantage of offloaded data copy operations.
Migration performance is significantly slower because it falls back to host-based copying.
Anything else you would like to add?
No response
Is your feature request related to a problem? Please describe?
Currently, XCOPY-based migrations only support SCSI-attached storage across all vendors. Fibre Channel (FC) storage is not supported, which prevents customers using FC SAN environments from leveraging XCOPY-based migrations.
This ticket proposes adding Fibre Channel support for XCOPY operations so that migrations can run efficiently in FC-backed environments.
Detailed Description
The current implementation assumes SCSI-backed devices for XCOPY-based migrations. Many enterprise environments use Fibre Channel SAN storage, particularly with Pure Storage arrays.
Because FC devices are not currently supported:
XCOPY-based migrations fail or are skipped.
Customers using FC storage cannot take advantage of offloaded data copy operations.
Migration performance is significantly slower because it falls back to host-based copying.
Anything else you would like to add?
No response