Any user of the Migration App.
This product is currently in Limited Availability. We invite any Customers interested in using the product to engage Egnyte Professional Services or their Customer Success Manager to have it enabled for their domain.
Q: What does it mean that Migration App is in Limited Availability?
A: While it has already proven effective at migrating thousands of TB of data for dozens of customers, Migration App is not yet Generally Available (GA). The Limited Availability Program allows us to enable Migration App for a subset of Egnyte Professional Services customers and other more technical customers who wish to use the product while we address scalability of the product.
Q: What version is the Migration App Agent currently?
A: The Migration App Agent is presently on version 3.8. The Agent now autonomously updates whenever a new version is available. It will wait to update until after your Agent has finished running any active Migration Jobs.
If you need to manually install a new Agent, please ensure no Migration Jobs are actively running. After the Agent updates, you will be able to keep running your existing Migration Jobs as before.
Q: What types of domains can be enabled with Migration App?
A: There are various types of Egnyte domains, but Migration App cannot be enabled for all types.
- Trial domains: In general, Migration App cannot be enabled Trial Domains. Trial domains are ineligible due to the storage limitations imposed by the trial program. One exception may be for Enterprise Trials, which eliminate the storage limitations.
- Archive domains: Yes.
- Vanity domains: No. An example of a vanity domain is myfiles.companyname.com which is essentially an alias from your standard Egnyte domain companyname.egnyte.com. To use Migration App, you must have it enabled on your standard domain and run all your migrations there.
- Egnytegov.com domains: Yes. Also known as FedRamp domains. Note that Egnyte is currently designated "FedRamp-Ready" and has not yet been fully FedRamp certified.
Q: How do I get to the Migration App once it has been enabled for my domain?
A: You can find Migration under the hamburger menu on your domain interface.
Q: Once enabled, does Migration remain enabled for a domain indefinitely?
A: Currently, access to the Migration App is controlled via a flag on the back end of the Egnyte platform so that it can be enabled or disabled as needed. There is no set policy for disabling Migration App, once it has been disabled. However, customers may request to have it disabled to eliminate confusion after onboarding is complete.
Q: Is there anything special I need to do to “upgrade” from the CMM Agent CLI tool to Migration App?
A: Yes, check out this Helpdesk article for an important prerequisite.
Q: What are the firewall requirements for Migration App?
A: If you have a firewall set up for outbound access, you will need to whitelist the following URLs before running the Migration App.
- https://io-us.egnyte.com:443(US datacenters)
- https://io-eu.egnyte.com:443(EU datacenters)
For more detailed setup information for Migration App, please see the Product Guide.
Q: While installing the Agent for the first time, what if it stalls at "Power Save is Enabled"?
A: You need to disable the sleep mode entirely. Unfortunately, the way the power settings are handled depends on the Windows version. Go to your Windows search field and type Power. Open Power & Sleep settings. Every option for going to sleep or turning off the machine should be set to Never.
Q: How can I find my Agent ID?
A: See this Helpdesk article How do I Get the Cloud Migration Manager Agent ID?
Q: Why do I need to provide my Windows Login credentials to set up my Agent?
A: Migration App requires information to identify both the Source and the Destination. Your Windows Login defines the Source, so you need both the username and password for the identity that has access to network shares. The Destination is defined by the domain and the Admin’s user name. For more information, see this Helpdesk Article.
Q: is the Agent Setup form case-sensitive?
A: Yes and no. Egnyte user name is not case-sensitive. But Windows AD user names are case-sensitive.
Q: What do I do if my Agent becomes disconnected from the Cloud?
A: See this Helpdesk article Reconnecting the Cloud Migration Manager Agent to the Cloud.
Q: What version is the Migration App Agent currently?
A: The Migration App Agent is presently on version 3.8.0. If you are using an earlier version of Migration App, please go to your Migration Dashboard, click on your Source and download the most up-to-date agent version to initiate the update as son as possible.
Please ensure no Migration Jobs are actively running before you install the new agent. After updating the Agent, you will be able to keep running your existing Migration Jobs as before.
Q: How can I tell what version of the Agent I have running?
A: View it in System Settings.
- From Windows search, type Add.
- Select Add or remove programs in System Settings.
- Scroll down to Cloud Migration Manager Agent.
- Click on it to view the version number.
Q: What if I see a message on the Migration Dashboard that a Source is inactive because the Version is unsupported?
A: Periodically, we will release an updated version of the Agent to address bug fixes and feature enhancements. There’s a simple process for updating the Agent detailed in the Helpdesk article Manually Updating the CMM Agent. Be sure to finish or stop any Migration Jobs that are running before you update the agent.
Q: Can I update the Migration App Agent when a Migration Job is running?
A: No. You need to be sure no jobs are running before you update the Agent. For more information, see this Helpdesk article.
Q: I had to change my Windows password, and now my Agent is running but doesn't seem to have access to any network shares.
A: If you change the user password for the Windows user associated with the Agent, you will need to change it on the Agent settings as well. You can follow the steps explained in Using Migration App to Migrate Content from a Network Share to change your password and restart the Agent.
Q: Can I install more than one Agent on my Windows host machine?
A: No. There's no reason why you'd even need to. One Agent is all you need for a single Source, and one Source can support the creation of multiple Migration Jobs. However, we recommend you run no more than 3-4 Migration Jobs concurrently.
However, for more complex migration projects, you can use your Migration Dashboard to create additional Sources, which would require separate Windows hosts, each with a different agent installed.
The Migrations Dashboard
Q: How can I clean up my dashboard and remove some Sources and Jobs that are no longer needed?
A: See this Helpdesk article Deleting Sources and Migration Jobs from the Migration Dashboard.
Q: When would I see more than one Source on my dashboard?
A: The Migrations Dashboard allows for multiple Sources. However, only one Agent can be installed per Windows host machine, so in most cases you will only have one Source activated. The only time you would see multiple Sources would be when you are using the dashboard to run migrations from multiple Windows host machines. In this case, each host would have their own installed Agent running migrations from different locations to your Egnyte domain.
Q: How do I know what an Error or Status Code means?
A: See this Helpdesk article Migration App Status and Error Codes for a complete listing. This can be helpful in troubleshooting and if you need to request technical support.
Q: Where can I find Migration Reports?
A: On the dashboard for any Migration Job, there’s a blue link in the upper right corner to Download report. Click on that to be redirected to the /Shared/Migrations folder on your Egnyte file server, where the report will be posted. From there, right-click on the file to download it and open it in Excel.
Q: My migration job says “Data migration succeeded,” but the progress bar still shows only partial progress. Why is that?
A: This will occur when you do a True-Up data migration, because the majority of the files for the job had already been migrated previously. So the progress bar is illustrating only the files migrated during this particular run: the deltas. You can always double-check in the destination on Egnyte. There you can see all of your source data minus any files that may have failed to be migrated, as indicated in the Migration Report.
Creating a Migration Job
Q: Can I create a Migration Job where the source is a mapped drive letter?
A: Yes. You can create a job where the source is either a mapped drive letter, an absolute path or a UNC path. To determine a UNC path:
- Hold down the Windows key + R, type cmd and click OK.
- In the command window type net use then hit Enter.
- Make a note of the required path, then type Exit, then hit Enter.
Q: When I create a Migration Job, how do I specify the destination?
A: The destination needs to be a valid Egnyte folder path. The destination must be specified as /Shared/<filename> or /Private/username/<filename>. Migration App will create the folder named <filename> within the respective root folder. Folder names in the path cannot be empty, contain special characters ( * ? \ < > ), or start or end with a space, symbol or period.
Q: I just created a Migration Job but I'm getting an error “Unable to validate source path.” What do I do?
A: This occurs if the correct permissions for either the Source or the Destination aren’t in place. Instead, you need to run it as the local User who has the permission to read from the Source, and you must also be an Egnyte Admin to access the Destination.
Q: Are there any special considerations for a Windows workstation mapped to a Mac for source data?
A: Yes. We've seen this work successfully, when the Mac is assigned a drive letter on a network. However this requires the Mac OS be updated to at least High Sierra 10.13.
What Gets Migrated
Q: Are there any limits to the size of migration jobs with Migration App?
A: We recommend a maximum of 1TB and 1 million objects per migration job. While Migration App itself doesn't impose a limit on migration jobs, we recommend parsing jobs into smaller subsets to facilitate ingress into the Egnyte back end. Moreover, there are default limits for each domain that are quite a bit higher than 1TB/1M objects. See Maximum Migration Job Size for more information.
Q: Why doesn’t the Migration App migrate empty folders?
A: This was not originally prioritized for the launch of the Migration App, but it is on our roadmap.
Q: Migration App failed to migrate some folders in the job. Why would that be?
A: If folders are empty they will not be migrated. Another reason might be that the user who registered the Agent doesn’t have the necessary permissions to view those folders. And finally, there are limitations to what Migration App can migrate. More information may be found in this Helpdesk article Filtered and Unsupported Objects with Migration App.
Q: If there are folders with more than 50K objects in them, can they still be migrated? Are 50K objects a hard limit or just a suggested limit for performance reasons?
A: 50K objects is a hard limit on the Egnyte platform, not of Migration App. You will need to break your folders down into smaller subsets to use Egnyte.
Q: Can I use the Migration App to migrate additional content into folders on my Egnyte domain that already contains data?
A: Yes, you can. In fact, that's an excellent use case for Migration App. See the Helpdesk article Using Migration App to Sync Data to Existing Folders in Egnyte.
Q: Can I use Migration App to migrate from a Flash drive?
A: Yes. A flash drive (USB drive) works the same way as any local drive. It can be a bit slower when compared to an internal SSD, but you should still be able to create and operate jobs sourcing the connected drive.
True-Ups or Syncing
Q: How do I run a True-Up?
A: The first time you Migrate Data using a Migration Job, the app copies all the content from the source to the destination. The next time you return to that same migration job and click Migrate Data, the app runs a True-Up.
Q: What's the difference between Migrating Data and running a True-Up?
A: The current Migration App user interface doesn't provide a visual distinction between the initial Data Migration and subsequent True-Ups. You click the button "Migrate Data" in both cases. But they do behave differently. If there is any content on the Destination, Migration App will perform a True-Up, which synchronizes or mirrors the Source and the Destination. It does so through a four-step process:
- It first scans the source.
- It then scans the destination.
- Next, it compares the source and the destination to build a table of Deltas - anything that's new, deleted, or has been changed on the source.
- Next, it migrates the Deltas to the destination.
- Finally, it deletes any files on the destination that no longer exist on the source. This action is called "Syncing Deletes" is an important action to be aware of.
Note that only in Step 4 does the Migration Job dashboard provide an estimated time of completion. This may be confusing, since the command can be running for an extended period of time without showing any progress. We are working on improvements to the User Interface to provide better visibility into where a given Migration Job is in the process, as well as the ability to control whether or not to "Sync Deletes."
Q: If I re-run a migration job to True-up data, does it create duplicates of what was already copied previously?
A: The Migrate Data command does not per-se create duplicates. But there are some considerations to keep in mind. Let’s look at a couple of different scenarios when running Migration App for True-ups:
- If a file is exactly the same at both the Source and the Destination, Migration App checks the size and mtime (mtime is a file attribute that records the time and date a file was last modified) of the file at Destination and does not re-send.
- However, if a user renames or moves a folder to a different location on the Source, Migration App creates the new folder at the Destination and does not delete the old folder. That's when you get into a duplication scenario.
- Alternatively, if a user deletes a folder on the Source that has already been migrated, the next time Migration App runs, it will delete that folder on the Destination. That’s because the Migration App is mirroring the two locations.
Q: For True-ups, what explains the discrepancy between the amount of data scanned on the source versus the amount of data migrated? What accounts for the discrepancy in the migrated data?
A: When you do a true-up, only the deltas will report as migrated. For example, you might have 90TB on the source, but only 20TB is new or changed. So only 20TB needs to be migrated as part of the true-up or synchronization process. We recognize this creates some confusion and look forward to improving our user interface as our product matures.
Q: How do I run the Sanitize command?
A: Sanitization is no longer a standalone (atomic) command. It is not an optional component of Data Migration. Clicking on Migrate Data brings up a modal where you select whether or not you want to santize the source.
Q: Does Migration App change long file path names when we run the Sanitize command?
A: No, it does not change file names or path names that are too long. These files and pathnames are merely flagged during Scan and can’t be migrated unless the user makes the necessary changes on the source. For more information about Egnyte path limits, see the Helpdesk article Unsupported Characters and File Types.
Q: What does the sanitization function do?
A: Opting in for sanitization changes any unsupported characters in filenames on the Source to an underscore. Once sanitization is complete, Migration App proceeds to migrate those files.
If you don’t want to change file names on the Source, do not opt in to sanitize. But be advised that if you don't select sanitize, those offending files and folders will NOT be migrated and you will have to handle them manually.
For more information about substitutions for unsupported characters, see this Helpdesk article Understanding the Sanitize Command in Migration App.
Q: How does Migration App migrate permissions?
A: Permissions migration involves three steps.
- Extracting the permissions from the source
- Mapping them to what they should look like at the Egnyte side
- Applying the permissions to the files on Egnyte
Q: How long does it take to migrate permissions?
A: It can take as long or longer to migrate permissions as it does to migrate the data itself.
Q: How does Migration App map permissions?
A: See this Helpdesk article Permission Translation with Migration App.
Q: Can I modify how permissions are mapped with Migration App?
A: No, not currently, although this is on our roadmap.
Q: Does Migration App migrate permissions at both the folder level and the file level?
A: Not exactly. Migration App migrates permissions for folders. The files contained therein inherit the parent folder's permissions.
Q: Are there any limitations for Migration App to migrate permissions?
A: Only that the Users and Groups must already exist on Egnyte.
Q: What happens if I migrate permissions but a User or Group has not been created on Egnyte?
A: The Migration Report provides a worksheet for both Missing Users and Missing Groups. Once you have created those Users and Groups on Egnyte, you may run Permissions Migration again. See this Helpdesk article Permission Translation with Migration App.
Q: Can I “sync” or True-Up permissions with Migration App?
A: No. In Migration App, Permissions Migration is an all-or-nothing command. We recommend you run Permissions migration at the very end of a Migration Job, right before you cut over all your users from using the Source to using Egnyte. If you run it multiple times, it will just execute a full operation multiple times.
Q: What is the estimated speed for permissions to be applied in Migration App?
A: Once permissions are scanned and extracted from the source and mapped to Egnyte (the first two steps), they are then applied at a rate of one folder per second, regardless of the number of permissions aligned with each folder.
Q: Why doesn't Migration App provide any progress information in the Status Bar while permissions are migrating?
A: Permissions migration involves three distinct steps, and each step takes some time. In the current version, during the first and second steps no information is communicated through the Migration Dashboard to the user. Only once the permissions are being applied to the files on Egnyte (Step Three) does the progress bar show any movement.
Q: If I migrate content into Shared, but it has different permissions on the Source than those set on the Destination (Egnyte), which permissions prevail?
A: This is controlled by the Egnyte CFS (Cloud File System) at the domain level. It defaults to "keep source permissions" but can be changed in Settings.
Speed, Bandwidth, and Throughput
Q: How can I estimate how long my Migrations Job will take?
A: You can first check out the speed test for your domain. Go to https://<domainname>.egnyte.com/speed-test/ (replacing <domainname> with your domain).
Keep in mind there are a lot of factors at play, but this will at least give you a baseline. If you’re reading from a network share, that will also impact your upload speed. For more information, see How Long Will it Take to Upload, Backup, or Download my Files?
Q: Why does the estimated time to complete a migration job keep changing on the dashboard?
A: For every file, Migration App does a metadata operation on the background, so the ETA is a function of the number of objects in the migration (folders and files combined.) For a total payload of similar size, if it comprises lots of small files, it takes longer than if the migration comprised a few larger files. As a given Migration job works through the files, the estimated time will continue to change based on the size of the current files being moved.
Q: How many migrations can run concurrently from the same Agent?
A: This depends on the capacity of the host machine where the Agent is running. Each migration job takes around 250 MB of memory. Depending on your host machine CPU/memory, you run three or four concurrent migration jobs. We don’t recommend running more than four jobs at one time. The limitation here is not the Migration App itself but rather the Egnyte system back end.
Q. Is there a minimum bandwidth requirement for the Migration App?
A: No. Migration Jobs will see higher throughput the more bandwidth you have. But high latency/low bandwidth is one of the use cases for Migration App. These jobs will take more time.
Q: What to do about improving upload speeds for migration jobs? Is it possible to set a number of threads for the Migration App to increase the throughput?
A: We don’t yet have a mechanism available to change parameters like the number of threads, although it is on our roadmap. Currently, Migration App can only use the default threads (4 transfer and 4 checkers). We do plan to expose such configurable parameters as part of the migration job configuration in the future. For more information, see How Long Will it Take to Upload, Backup, or Download my Files?
Q: What if the credentials to register the Agent won't allow me to access the network share source server?
A: You must ensure the Windows host machine is on the same AD domain as the network share resources. Check out this Helpdesk article Ensuring Windows Host Machine and Source Are on the Same AD Domain.
Q: What if a Migration Job hangs?
A: Check out this Helpdesk article What if a Migration Job Hangs?
Q: What if the Agent Registration hangs?
A: Check out this Helpdesk article What if Agent Registration is Hanging?
Q: What if I’m unable to execute any commands?
A: Check out this Helpdesk article What if I Am Unable to Execute Any Commands in Migration App?
Q: Can any Egnyte User use Migration App?
A: No, only Administrators should use the Migration App. Power Users can view the Migration Dashboard but cannot successfully run jobs without a workaround. Ask your CSM or Professional Services Agent for assistance if you wish to designate specific Power Users to use Migration App.
Q: Can Migration App be limited to be available to only certain Admin users on a domain?
A: No. Currently, Migration App is enabled for all Administrators on a given domain.
Q: Can any Administrator monitor migration jobs created by another Administrator?
A: No. Migration jobs are tied to the User/Domain. This becomes the key to each job and therefore only a given User can see their own Agents and Migration Jobs in the dashboard.
Q: If I need to stop a migration for some reason, can I restart it later? I don’t want to be using all the bandwidth during the day when it may impact other users doing their work.
A Yes. You can stop and restart a Migration Job at any time. However, any time you restart a Migration Job, it needs to do a complete scan of both the source and the destination. This allows it to identify what, if any, data has already been migrated. Actual movement of the data begins where it left off previously.
Q: If I need to restart a migration job, what do I need to do?
A: Return to the Migration Dashboard, click on Details for the migration job, and then click Migrate Data again. It will pick up where it left off.
Q: Where can I find my migration job logs?
A: It depends on how you’re logged into the Agent.
If you’re logged in as the Local System:
If you are logged in as the Local User:
Q: What if I have a feature request?
A: If you have feature suggestions or requests, feel free to submit them here, and make sure you mention Migration App in the text.
For more complex requests that would benefit from providing screen shots or other attachments, you may submit them to firstname.lastname@example.org. Be sure to include Migration App in the email title. Our Support team will push your comments to the Product team for consideration.
Q: Is there a way to get a quick question answered?