Windows-Admin-Center-Ideas-and-Feedback
Windows-Admin-Center-Ideas-and-Feedback copied to clipboard
Storage Migration Service - Storage Migration Proxy is not used on clustered file shares when the cluster owner is not also the file share owner
Gateway Version: 2110.2: 1.3.2204.19002 Extension Version: 2.15.0
To Reproduce Steps to reproduce the behavior:
-
Configure a clustered file share (standard not scale out)
-
configure a storage migration to use the clustered file share
-
Ensure that the cluster core resources are hosted on a different node than the file share role
-
Start the migration
-
log into the server hosting the file share role
-
View resource monitor, witness that all traffic is coming from the server with the 'storage migration service' installed, rather than from the old file share server.
-
Stop the migration.
-
Move the cluster core resources so they are hosted on the same node as the file share role
-
Start the migration.
-
log into the server hosting the file share & cluster core resources
-
View resource monitor, witness that file transfer network traffic is now originating on the old file server rather than the storage migration service host server.
Expected behavior Storage migration proxy should be used to move the files directly from old->new regardless of where the cluster core resources are in relation to the file share cluter role.
Screenshots & Additional context Old File server: Server 2012R2 Cluster with file server role (not SOFS) New file server: Server 2022 cluster with file server role (not SOFS) Storage migration Service Server: Server 2019