Audience
Any user of the Migration App.
Context
In Migration App, empty folders can be automatically created on the destination as the final step of every Migration command. Note that an empty folder is not actually "migrated" but rather "created," as it’s simply a directory path.
Default Behavior for Opting-In to Empty Folders
By default, users will be offered the option to select this feature every time they initiate a data migration command.
How it Works
- When empty folders creation starts, the estimated completion time and the progress bar for job completion will appear static. Still, the spinning circles in the details sections below will indicate that something is happening in the background.
- Once the command is complete, the UI is updated with stats showing how many empty folders were created.
-
Migration Report contains additional information about empty folder creation, which can be found in the last worksheet titled Empty Folders.
Timing
The “Create Empty Folders” step in the Data Migration metacommand adds some additional time to the overall command completion. The new metacommand sequence will be:
Initial Data Migration
- Scan the source
- Sanitize the source (optional)
- Rescan the source (if sanitize was included)
- Migrate the data
- Build empty folders on the destination
True-Ups
- Scan the source
- Sanitize the source (optional)
- Rescan the source (if sanitize was included)
- Scan the destination
- Compare the source and destination to build a table of deltas
- Migrate the deltas
- Delete any data and empty folders from the destination that are no longer on the source
- Build empty folders on the destination
Note that Steps 1-5 for the Initial Migration and 7-8 of the True-Up do not involve copying files, so that no movement will be visible on the progress bar in the UI. As a result, the ETA for completion will stop updating after finishing Step 4 for an Initial Migration or Step 6 for a True-Up.
Then there will be a brief period while folders are being created on the destination where it will appear on the UI that nothing is happening. However, once the entire metacommand is complete, Migration Report can be accessed to view the folders created.
What if There is a Folder on the Source Containing Only Unsupported Files?
This is an edge case, but it has been observed in several instances.
If the user has a folder on the source that contains only unsupported files, none of these files will be migrated. As a result, this folder will not be created on the destination. Moreover, as this folder is not empty on the source, it will not be created as part of the empty folder migration step.
So, in the end, this folder will always be missing in destination. There is no way presently to migrate it.
The only solution would be to put something inside that folder that can be migrated and run a True-Up. It will then appear on the destination containing only the one item that is supported.
Questions? Feature Requests? Other Feedback?
For any feature suggestions or requests, feel free to submit them here, and mention Migration App in the text.
For more complex requests that would benefit from providing screenshots or other attachments, submit them to support@egnyte.com. Be sure to include Migration App in the email title. The Support team will push the comments to the Product team for consideration.