Forum Discussion
Storage Migration Service - Procedure Clarifications
- Is there recommended maximum time i need to move between the 3 stages - Scan old server, Transfer Data, Cutoff?
The only real max is how long between reboots. A design limitation of SMS transfer is that it cannot resume a transfer job if the servers involved are rebooted. If following a normal patching schedule that means 30 days max. We're adding functionality to support resuming (it will likely be to WS2022, definitely WS2025, but not to WS2019, which is out of mainstream support).
- If I've done yesterday the scan on my old server and planning to do the transfer only in about 2 weeks - what about the files and permissions that will change in this period of time? do i need to run a new scan on my old server near the date I'm going to do the actual transfer? should i delete or clear something from the previous scan? (The scan took about 5 hours).
No, the inventory scan is just designed to give you some understanding of how big your migration is. The actual inventory runs again the moment you start the transfer (under the covers), in order to know what to transfer.
5 hours is a pretty long scan, tbh. I presume the source computer hosting a lot of files on very slow spinning drives.
- I understand that the process of the transfer takes care of changes that were made to the scanned file from the last scan done.
Yes see above. And rerunning a transfer will catch up any changes from the last transfer differentially.
- I plan to add the FSRM role to the new server and after the cutoff stage to import the FSRM settings from the old server to the new one using dirquota & filescrn - is that the way to do it? shall it work on server 2022 FSRM?
Yes those tools or the FSRM PowerShell. SMS has no knowledge of FSRM settings at all, so you will need to migrate those separately.