Forum Discussion

Marco_Schilder's avatar
Marco_Schilder
Copper Contributor
Aug 02, 2023

Storage Migration Services and NetApp

We're working on a migration of on-premises NetApp CIFS shares to on-premises Windows Server 2022 file servers. The NetApp consists a single FAS array with 110 CIFS shares and +/- 100TB of data.

 

In previous migration scenarios we've used Robocopy for this, but now we're looking to use Storage Migration Services. We've installed 3 of eventually 20 file servers with Storage Migration Service (proxy) and managed to connect to the NetApp. Validation was a pass, and then we've started a scan. The first scan 'stopped' at 62.9TB and 185,562,500 files, and didn't seem to do much anymore after that. Seeing that the CPU idle time was a bit high while the scan was running, we've added more vCPU's and tried again. This time the admin shares were excluded. The result was almost the same; 62,7TB and 185,925,104. We gave it a few days, but the count won't go up.

 

We've tried some registry tweaks (https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/faq#optimizing-inventory-and-transfer-performance) but that doesn't seem to do much for the scan performance. Also, event viewer (StorageMigrationService debug log) only gave us the following error at exactly midnight:

 

08-02-2023-00:00:00.933 [Erro] SeekToKey failed for opId=fa957bb1-e03e-493b-9d7d-4ae0ee7c9117 device=SVM_NAS.ADDOMAIN.LOCAL path= endpoint= gr=SeekGT pathOrder=    [d:\os\src\base\dms\datastore\EndpointTableManagerImpl.cs::SeekToKeyByPath::1943]

 

(I've changed the name of the AD Domain in the error). Not sure were the d:\os drive folder is related to? Any suggestions on how to complete a first scan?

1 Reply

  • Marco_Schilder's avatar
    Marco_Schilder
    Copper Contributor
    Aug 09, 2023
    Eventually, after 6 days the scan was finished with warnings. Didn't expect it to to actually come through, as progress stopped for 2 days.
    Now I have the next challenge; to divide the CIFS shares over multiple file servers. This doesn't seem to be possible, coming from 1 source. As we were already expecting for Storage Migration Services not to come through, we fell back to our original approach; Robocopy.

Resources