A company has an on-premises file server named Server1 that is currently registered to a Storage Sync Service and configured as a server endpoint in SyncGroup1. You deploy a new on-premises server named Server2 to replace Server1.
You need to migrate the synchronization workload from Server1 to Server2 while ensuring users experience minimal disruption and no data is lost.
Which sequence of actions should you perform?
- 1Install the Azure File Sync agent on Server2 and register Server2 with the Storage Sync Service.
- 2Create a server endpoint for Server2 in SyncGroup1.
- 3Wait for the initial sync of the file metadata namespace to complete on Server2.
- 4Redirect user connections and network share mappings from Server1 to Server2.
- 5Remove the server endpoint for Server1 from SyncGroup1.
Answer
The correct sequence is: first, install the Azure File Sync agent on Server2 and register Server2 with the Storage Sync Service; second, create a server endpoint for Server2 in SyncGroup1; third, wait for the initial sync of the file metadata namespace to complete on Server2; fourth, redirect user connections and network share mappings from Server1 to Server2; and finally, remove the server endpoint for Server1 from SyncGroup1.
The correct migration path is to first register Server2 and create a server endpoint in the existing sync group. This allows Server2 to synchronize the namespace (metadata) from the cloud. Once namespace sync is complete, client connections are redirected to Server2. Finally, Server1's endpoint is removed from the sync group.
Step-by-Step Solution
Key Concept
Server retirement and replacement migration using Azure File Sync
Estimated Time:3m 0s