1. Home
  2. Windows App
  3. TechTips: Migrating Data From MS-Windows

TechTips: Migrating Data From MS-Windows

This application note guides you through some short preparation that will expedite migrating data from your laptop or local network. It also describes what you can expect during the data transfer and how to make it complete efficiently.

Preparing Your Job

1: Register for your Cloud FastPath account at www.cloudfastpath.com and then select the Register button. Follow the easy registration steps.

2: Ensure the data you want migrated to your cloud service provider is accessible to the dedicated Windows laptop/computer you will be using for this migration:

  1. The laptop/computer must remain “on” and connected to the network for the duration of your active migration.
  2. Your data must be either on one of your local drives or on a computer that is physically connected to the computer where the Cloud FastPath Windows app is installed. The Cloud FastPath Windows app does not currently support VPNs or WIFI connections.
  3. If your data is on the network, you will need to create a mapped drive for that server or shared folder.
  4. Schedule a time for the transfer when the files will not be accessed.  Editing, adding, or deleting files from the source or target folders during the data transfer may affect Cloud FastPath’s file syncing operations and result in incomplete or erroneous transfers.  If you are working in an environment where multiple users will have access to the files, it may be advisable to schedule the transfer during off hours.  Scheduling the transfer during off hours can also free up network resources, so your job runs faster.
  5. Log in to the Cloud FastPath web app via Chrome, Firefox or Internet Explorer to monitor your migration — start, pause, or resume a Data Motion Job at any time.  You can access the Cloud FastPath web app (https://www.cloudfastpath.com/cfp) to monitor and manage your job from any computer that is connected to the Internet.

3: Have your access credentials available for both your source data and cloud provider account(s).  You will need these to access the source data and to move the data into your cloud provider account.

Tips for the Ultimate Migration Experience and Results

1: Configuring the folders for your data on the target server: This is done when you create a new job or, if you have an existing job, you can edit it. See the Data Motion Jobs page for more info.

2: Migration performance is enhanced when the laptop/computer that has Cloud FastPath running on it is co-located with the source data and on the same network.  The closer the data is to your computer, the faster the transfer.

3: If possible, place all the files and folders you want migrated into a single source folder or a few folders.  While this is not essential, it makes the migration more automated and efficient.

4: You may run Cloud FastPath during any level of network activity and the solution will maximize throughput speeds via built-in WAN optimization technology. That said, Cloud FastPath moves data at higher speeds when your network traffic is minimal.  Also, be aware that a migration may slow down the network while your Data Motion Jobs are actively running.  Should this occur and be undesired, simply “pause” the active Data Migration Job and manually “resume” it later on when the network is under lower load.

5: Data Motion Jobs must be run one at a time.  You can manually initiate a Data Motion Job or schedule the Job so that it occurs during preferred times.  You may also arrange to have Data Motion Jobs run continuously, in sequential order, until the migration is complete.  Please ask Team Tervela for help with scheduling Data Motion Jobs if this is of interest.

6: Once you begin a Data Motion Job, please refrain from rearranging/moving source and target files or folders involved in that particular Job until the files or folders for the Data Motion Job says “Complete”.  This applies to files and folders at both your source system and in ShareFile.

7: Sometimes files are not migrated during the initial Data Motion Job because of network interruptions or temporary errors.  Cloud FastPath’s main dashboard will inform you when this occurs by labeling the job as “failed” instead of “complete”.

  1. IMPORTANT: A “failed” job does NOT mean you must start the migration from the beginning. Rather, it means there was at least 1 file that did not get successfully moved to the destination on the first pass of the migration. Cloud FastPath’s built-in synchronization and error handling capabilities will automatically move any files that don’t get successfully moved during the initial Data Motion Job attempt.
  2. Instructions:  To address Jobs in a “failed” state, first make sure no Data Motion Jobs are actively running. Then, simply click on the Play button next to a Data Motion Job that is labeled “failed”. Cloud FastPath will automatically migrate any files that were not migrated in the initial Data Motion Job run.  Click Play a third time if a Data Motion Job finishes and still says “failed”.  Please contact Tervela to troubleshoot if a Data Motion Job remains in a “failed” state after 3 attempts to complete the Job.

8: Cloud FastPath automatically generates a full report that shows you the files successfully (and unsuccessfully) migrated to your cloud provider. This report is automatically placed in a folder on the target (cloud provider) called CFP Transfer Logs. Please note that Cloud FastPath only moves a copy of the source data to your cloud provider and does NOT delete any data from the source. We recommend that you validate your data migration has occurred to your satisfaction before permanently deleting any source files.

9: Contact Tervela any time you have questions or comments.  We look forward to your successful migration with Cloud FastPath!

Updated on May 2, 2019

Was this article helpful?

Related Articles

Leave a Comment