TABLE OF CONTENTS

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: Make sure the share remains accessible during the entirety of the seed phase.  Do not modify the source share unless you are doing a non-final incremental migration.
  • Upload phase: Make sure that the source share remains accessible during the entirety of the upload phase. Do not modify the contents of the source share unless you are doing a non-final incremental migration. Users may create/access/modify files on the destination share on the CacheDrive during non-incremental or final migration incremental upload phases.
  • 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.

    For all migration types, the Scan phase can be run multiple times.

    For incremental migrations, the Seed and Upload phases can be run multiple times. Complete the incremental migration by running a final migration (select Final migration in the popup that appears after clicking Migrate). You may modify the contents of the source share before running the final migration. Once the final migration starts, any additional modifications will not be transferred over and may cause the migration job to fail.

    Note that shares will not be made available in MCM or over SMB until the final migration is completed.

    Use the "Cache Files From" option to keep files modified after the specified date in the local cache. This will improve performance the first time these files are accessed.


    For non-incremental migrations, the Seed and Upload phases can be run only once. Do not modify the contents of the source share.

  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.