You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/file-sync/file-sync-share-to-share-migration.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ Follow these instructions if cloud tiering is on and you're migrating to a file
109
109
110
110
You can now start the [initial copy](#initial-copy) between the source and target shares on the target Azure File Sync VM.
111
111
112
-
## Initial copy
112
+
###Initial copy
113
113
114
114
Use Robocopy, a tool that's built into Windows, to copy the files from source to target shares.
115
115
@@ -129,7 +129,7 @@ Use Robocopy, a tool that's built into Windows, to copy the files from source to
129
129
130
130
1. Wait for the initial Robocopy run to complete successfully and for the sync from source to target to complete. We recommend waiting for one additional hour to make sure all remaining changes are synced. To check that all changes have been synced, see [How do I monitor the progress of a current sync session?](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?tabs=portal1%2Cazure-portal#how-do-i-monitor-the-progress-of-a-current-sync-session)
131
131
132
-
## Sync final changes
132
+
###Sync final changes
133
133
134
134
Before syncing the final changes, turn off SMB sharing for the existing share or at least make it read-only. After turning off SMB sharing, wait one hour to make sure all remaining changes are synced to Azure.
Once your IaaS VM sync completes, the local target agent will also be up to date.
149
149
150
-
## Enable sharing on the new server endpoint
150
+
###Enable sharing on the new server endpoint
151
151
152
152
If you're migrating to a new Azure File Sync server, you should rename the old server to a random name, then rename the new server to the same name as the old server. This way, the file share URL will be the same for your end users.
153
153
154
154
Enable the new share T:\cache. All the same file ACLs will be there. You'll need to recreate any share-level permissions that existed on the old share.
155
155
156
-
## Remove the old server endpoint and sync group
156
+
###Remove the old server endpoint and sync group
157
157
158
158
Once you've confirmed everything is working correctly with the new sync group, you can deprovision the old sync group. [Remove the server endpoints](file-sync-server-endpoint-delete.md) first. You don't need to recall all the data to the old server before removing the server endpoint.
0 commit comments