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 copying files from a larger source to a smaller cache size.


Requirements:

  • Activation Key to enable feature
  • Source share must be a CIFS share or Cloud storage bucket
  • Enable SMBv1 on the source File Server
  • Available in Business Plan and Enterprise Plan


Installing Morro Migrate

Morro Migrate add-on is installed on the account using an Activation Key. If you do not have an Activation Key, please contact Customer Support.


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


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
  • Share Name
  • User Name
  • Password


Hostname/IP Address

The hostname or IP address of the CIFS server.


Share Name

The name of the CIFS share from the CIFS server from where the files will be migrated.


User Name

The user name of the user used to access the CIFS Server and Share.


Password

The password for the user name used to access the CIFS Server and Share.



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
  • Server Side Encryption
  • Check S3 China region checkbox if necessary.


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

https://support.morrodata.com/a/solutions/articles/14000093008?lang=en


Folder in Cloud Storage

Enter the folder path for your source.  Use '/' for the root folder.


Server Side Encryption

Select the type of encryption used in the Cloud storage bucket.



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


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

https://support.morrodata.com/a/solutions/articles/14000097324?lang=en


Folder in Cloud Storage

Enter the folder path for your source.  Use '/' for the root folder.



Destination CacheDrive and Share

Enter the following information for the Morro Data system to which the files will be migrated.

  • Share Name
  • Storage Pool
  • Gateway
  • Migration Type
  • Ignore Error
  • Error Number Limitation
  • Cache Files From
  • Incremental Migrate


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 where the new share will be created.  The Share Type field with be auto-populated based on the type of pool selected.


Folder in Cloud Storage (Archive Share Type Only)

Enter the folder name in "Folder in Cloud Storage", using '/' for root.


Server Side Encryption (Archive Share Type Only)

Select the encryption algorithm used in the Cloud storage backend for the pool in the "Server Side Encryption" dropdown.


Migration Type (Local Source only)

There are two types of local migration:

  • Data Only (default)
  • Data and permissions (AD Mode)
    Note: requires SMBv1 access to scan permissions


"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 START phase. 


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


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 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 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 enabled in the Morro Data system.


Click ADD to create the task.


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 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 and estimations 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.  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 files will be available from the CacheDrive share. The file structure is available on the CacheDrive and files that are not on the CacheDrive will be fetched from the source share or from the Morro Data cloud. The length of time the required for the third phase depends on the amount of files that are available. The process can be sped up by using multiple threads which is supported for Replicate and Archive shares. The migrate window will show the progress and the process can be suspended and activated via the SUSPEND and ACTIVE button.


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 a 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 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.



Notes:

  • In the event of an error, Migrate will retry three times before exiting the task. If the task exits in an error, the task must be recreated to try again.



Limitations

  • Migrate does not support migrate from DFS Volume. Create migrate job for each DFS target folder (version 4.1)
  • File Server must support CIFS/SMBv1 protocol. If SMBv1 is disabled on your server, please enable SMBv1 prior to Migration starts.