Skip to content

Commit 10b4998

Browse files
authored
Update file-sync-share-to-share-migration.md
1 parent 2c698a2 commit 10b4998

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/storage/file-sync/file-sync-share-to-share-migration.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ Follow these instructions if cloud tiering is on and you're migrating to a file
109109

110110
You can now start the [initial copy](#initial-copy) between the source and target shares on the target Azure File Sync VM.
111111

112-
## Initial copy
112+
### Initial copy
113113

114114
Use Robocopy, a tool that's built into Windows, to copy the files from source to target shares.
115115

@@ -129,7 +129,7 @@ Use Robocopy, a tool that's built into Windows, to copy the files from source to
129129

130130
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)
131131

132-
## Sync final changes
132+
### Sync final changes
133133

134134
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.
135135

@@ -147,13 +147,13 @@ robocopy s:\ t:\target /mir /copyall /mt:16 /DCOPY:DAT
147147

148148
Once your IaaS VM sync completes, the local target agent will also be up to date.
149149

150-
## Enable sharing on the new server endpoint
150+
### Enable sharing on the new server endpoint
151151

152152
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.
153153

154154
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.
155155

156-
## Remove the old server endpoint and sync group
156+
### Remove the old server endpoint and sync group
157157

158158
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.
159159

0 commit comments

Comments
 (0)