Morro Migrate is an add-on app that manages the migration of files from an existing file server or Cloud storage bucket to a Morro Data share.  Morro Migrate has shorter offline times and automates the process of onboarding data that is larger than the cache capacity.


Requirements:

  • Activation Key to enable the feature
  • Source share must be a CIFS share or Cloud storage bucket
  • The source server must support SMB 2.1 or 3.x.  Support for SMB 1 or 2.0 is available upon request.
  • Available in Business Plan and Enterprise Plan


The Morro Migrate app is installed using an Activation Key. If you do not have an Activation Key, please contact your Account Manager or Customer Support.


Once you have the Activation Key, please refer to the article Manage Morro Account - Business Admin: Redeem Key.



Troubleshooting

To troubleshoot Migrate issues, please see the following article:


Morro Migrate Error Logs



Morro Migrate Setup - Create a Task

To use Morro Migrate, the administrator needs to create a migration task. To configure the task, specify the information for the Source Device and Share or Cloud bucket and the Destination CacheDrive and Share.


Local Source Device and Share


Enter the following information for the source device and share:

  • Hostname/IP Address - The hostname or IP address of the CIFS server.
  • Share Name - The name of the source CIFS share.
  • User Name - The user name used to access the share.
  • Password - The password for the user name.


Amazon S3 Bucket Source

Enter the following information for the Cloud bucket:

  • Select AmazonS3 as the Provider
  • Bucket Name
  • Key ID
  • Secret Key
  • Folder in Cloud Storage - The folder path for your source.  Use '/' for the root folder.
  • Server Side Encryption - The type of encryption used in the Cloud storage bucket.
  • Check the S3 China region checkbox if necessary.


For more information on the Bucket Name, Key ID, and Secret Key, please see:

https://support.morrodata.com/support/solutions/articles/14000093008


Backblaze Bucket Source


Enter the following information for the Cloud bucket:

  • Select Backblaze as the Provider
  • Bucket ID
  • Key ID
  • Application Key
  • Folder in Cloud Storage - The folder path for your source.  Use '/' for the root folder.


For more information on the Bucket ID, Key ID, and Application Key, please see:

https://support.morrodata.com/support/solutions/articles/14000097324


Destination CacheDrive and Share

Enter the following information for the Morro Data share to which the files will be migrated, then click Add to create the task.

  • Share Name - The name of a non-existing share.  Migrate will create the share and copy the files to it.
  • Storage Pool - Select the pool for the new share.  The Share Type field with be automatically populated based on the type of pool selected.
  • Gateway - The gateway device that will be the destination for the LAN transfer.  This device will also perform any necessary processing and uploading to cloud storage.
  • Migration Type - See below.
  • Ignore Error - While it is best to fix all errors found in the Scan phase, some errors can be safely ignored.  Select the type of errors to ignore during the Seed phase of the migration.
  • Error Number Limitation - Limit the number of errors accepted in the Scan and Seed phases.  Once this number is reached, the phase will fail.
  • Cache Files From - If there is enough space in the cache, this option will force the CacheDrive to keep migrated files that were modified after the selected date in the cache for better performance.
  • Incremental Migrate - Enable Incremental Migration which allows for multiple Seed and Upload Phases.  A final migration must be performed before the share will be available for access in the Morro Data system.


Migration Type (Local Source only)

There are two types of local migration:

  • Data Only (default)
  • Data and permissions (AD Mode)
    Note: This requires SMB 2.1 or 3.x access to the share.  SMB 1 and 2.0 support are available upon request.


"Data only" is the default type, which migrates data without retaining permissions from the source share. "Data only" migrations require less time to initialize in the SCAN phase. 


"Data and permissions (AD Mode)" requires that both the source and destination devices are joined to the same Active Directory domain. It will attempt to migrate users, groups, basic permissions, and Windows ACLs. The process requires more time to initialize in the SCAN phase.



Morro Migrate Process


The Morro Migrate task is divided into three phases:

  1. Scan
  2. Seed
  3. Upload


Phase 1 - Scan

Click SCAN to begin the Scan phase. During this phase, the system gathers information about the source share such as the number of files and folders, the amount of data, and checks file access permissions. The migration task will not start copying and uploading files, and SCAN can be run multiple times. 


Phase 2 - Seed

Standard Migration: Click MIGRATE to begin the Seed phase. During this phase, the source share should not be used. Changes to the source share cannot be migrated after the task is started and making changes to the source data could cause problems with the data migration.


Incremental Migration: Click MIGRATE to begin the Seed phase.  During this phase, the source share can still be used normally.  Changes to the source share will be migrated in subsequent Seed phase runs.  When you are ready to run the final migration, enable "Final Migrate" and do not use the source share until the migration is completed.  Note that changes to the source share after starting the final migrate cannot be transferred to the destination share using the Migrate app and may cause the final migration to fail.



Phase 3 - Upload

Standard Migration: When the upload phase begins, the CacheDrive will quickly recreate the source share's filesystem structure in the destination share.  Users may begin using the destination share soon after the phase begins.  The CacheDrive will automatically fetch requested files from the source share or the cloud if they are not in the cache.  The amount of time required to complete the upload phase depends on the amount of data to upload, available bandwidth, etc.  Replicate and Archive shares can use multiple threads to speed up the process.  The migrate window will show task progress, and can be used to suspend and re-active the process.


Incremental Migration: When the upload phase begins, the files will be uploaded from the CacheDrive to the cloud. The share will not be available on the CacheDrive until the Final Migrate is started.  During the final migrate, the share on the CacheDrive may be used normally and the source share should no longer be used.  Please see the Standard Migration section above for more details about the final migration upload.


Completed

Once the task is finished, the system will show the completed status. 


Delete the Task

Click on the red Trash Can icon to delete the Task. Deleting the task will cancel the job regardless of the task status.



Task Status

The Morro Migrate task uses an icon to indicate the status of each phase of the task.


IconDefinition
 Creating the Migrate Task
The Phase did not start
(Blinking)The Phase is running
  • The phase was completed successfully with ignored errors
The Incremental Phase was completed successfully
The Pase was completed successfully
The Phase is pending
The Task has entered the UPLOAD phase and is uploading data to the cloud
The Task has been suspended and can be activated again
The Phase has failed but will resume at a later time
The Phase has failed and will not resume


Errors

  • In the event of errors, Migrate will retry three times before exiting the task in the SCAN and the SEED phases. If the task exits with errors, please fix the error first then restart the phase manually.
  • If errors happen in the UPLOAD phase and after fixing the errors, the job can be resumed immediately by clicking 'Resume Now' button. Also the task would resume automatically after some time. 
  • Please refer to Migrate Error Log for details on erros.


Limitations

  • Migrate does not support DFS Volumes. Create migrate job for each DFS target folder separately.
  • The file server must support CIFS/SMB 2.1 or 3.x. If SMB 1 or 2.0 is required, please contact support.