File Server Enablement (FSE) allows you to cloud-enable any folder on a machine and map it to a Team Share or a user account. You can also specify a UNC path as a source for File Server Enablement.
Migrating a File Server
In some instances, you might need to migrate a file server that has already been configured for File Server Enablement and mapped to Team Shares. To accomplish this, you will need to:
- Copy the files from the original file server to the new file server
- Configure File Server Enablement on the new file server
- Re-map existing Team Shares to the new file server
- Decommission the original file server
Step 1: Copy Files From the Original Server to the New Server
As a first step, you will need to copy the files from the original file server to the new file server, using your preferred migration method.
Step 2: Configure File Server Enablement on the New File Server
When the files have been successfully copied to the new file server, install the Anchor desktop client on the new file server, and then turn on File Server Enablement.
For complete instructions, please reference Step 1 – Step 6 of the How to Cloud-Enable a Server Using File Server Enablement Knowledgebase article.
Step 3: Re-Map Existing Team Shares to the New File Server
After you turn on File Server Enablement for the new file server, you can re-map the appropriate Team Shares to the new file server.
For complete instructions, please reference Step 7 – Step 9 of the How to Cloud-Enable a Server Using File Server Enablement Knowledgebase article.
Note: Collisions might occur if this step is performed while users are accessing data on the new file server. Please perform this step when users are not likely to be accessing the system (off-hours).
Note: Once mapping is complete, the agent GUI will show files 'syncing' - This is the GUI's display of the metadata rebuild process, not a re-sync of all of the data. Only new/changed files will sync, while the rest will simply be added in the local machines databases for metadata tracking.
For instruction on resolving collisions using the Overwrite Collisions option, please reference the How to Manually Resolve a File Sync Conflict Knowledgebase article.
Step 4: Decommission the Original File Server
Note: Before you decommission the original file server, you must remove mappings or unlink the desktop client installed on the server. If you decommission the original file server with active mappings, you will lose your Team Share data.
After the Team Shares are mapped to the new file server, you can decommission the original file server if needed. If users also access the original file server directly, you might also need to point these users to the new file server.