When using the Morro Migrate app to onboard your data, please use this guide to make the process as easy as possible.

Things to Avoid

  • Seed phase: Do not modify the source share or access the destination share on the CacheDrive.
  • Upload phase: Do not modify or make unavailable the source share.  Users may create/access/modify files on the destination share on the CacheDrive.
  • Avoid mapping the shares to other CacheDrives until the migration process is complete.  This allows the devices to optimize sync requests into batches resulting in faster, more efficient syncing.
  • Try not to cancel a migration unless you intend to delete the target share and start over.  Cancelling a migration may cause issues when converting the target replicate share to a sync share.  If you run into issues during the migration, please contact Morro support.
  • Multiple migrate tasks can be run simultaneously with different destination gateways, but avoid running multiple tasks to a single gateway.

Using the Morro Migrate App

Use the following steps to migrate data from a share on a local file server or the cloud to a Morro CacheDrive.  For more detailed information, please see the in-app documentation or the Morro Migrate User Guide.

  1. Configure a migrate task and click Add.

  2. Progress through the Scan, Seed, and Upload Phases.

  3. Once the migration has completed successfully, convert the target share to a sync share.
    Navigation: From MCM -> Click File System -> Select share

  4. Enable access to the share from other CacheDrives.
    Navigation: From MCM -> Click File System -> Select share -> Click Permissions -> Click Gateway

Migration Example

Consider the case of migrating two shares on Windows File servers (SourceA and SourceB) to two CacheDrives (share DestinationA on CacheDriveA and share DestinationB on CacheDriveB).  We recommend the following procedure:

  1. Create two migration tasks:
    Task A - SourceA to DestinationA on CacheDriveA
    Task B - SourceB to DestinationB on CacheDriveB
  2. Start the Scan phase on both migration tasks.
  3. During an off-hours period, start the Seed phase for both migration tasks.  Note that users should not access the files on the source and destination shares during the Seed phase.
  4. Once the Seed phase is completed, the migration tasks will automatically start the Upload phase.  Users can now create/modify/access all files on DestinationA and DestinationB from CacheDriveA and CacheDriveB respectively.  DestinationA and DestinationB should not be made available on other CacheDrives yet.
  5. Once the Upload phase is completed, convert DestinationA and DestinationB to sync shares.
  6. Make DestinationA and DestinationB available to other CacheDrives.