Morro Duplicate is a CloudNAS app that manages backups from a CacheDrive share to a network share such as on a NAS.  It can handle full and incremental backups, one-time or recurring with a schedule.

Note: If the source contains data that is not in the cache, it will be fetched from the cloud during the Duplicate task. This may result in egress charges.


  • Activation Key to enable the feature for Enterprise Plan.
  • The destination share must be a CIFS share with sufficient space to store the data

Installing Morro Duplicate

The Morro Duplicate 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 Duplicate Setup - Create a Task

To use Morro Duplicate, the administrator needs to create a backup task. To configure the task, specify the information for the Source CacheDrive Share, Destination Device and Share, and optional schedule.

Source CacheDrive and Share

Enter the following information for the CacheDrive from which the files will be duplicated.

  • Share Name - The name of the source share.
  • Gateway - The CacheDrive that contains the source share.
  • Duplication Type - "Data Only" or "Data and permissions (AD Mode).  See below for more information. 
  • Incremental Duplicate - Enable Incremental Duplication which allows for multiple Seed and Upload Phases.  A final duplication must be performed before the task can be deleted.

Duplicate Types

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

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

Destination Device and Share

Enter the following information for the source device and share:

  • Hostname/IP Address - The hostname or IP address of the Destination CIFS server.
  • Share Name - The name of the CIFS share to be used as the duplication destination.
  • 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.
  • Schedule - Set a schedule for running incremental duplicate tasks.  See below for more information on setting a schedule.

Note that the destination share:

  • should not be used while a duplicate task is running.
  • must be empty when creating the task.
  • must support SMB2.1 or SMB3.  SMB1 support can be enabled upon request.


Set a schedule to perform incremental duplication tasks automatically at scheduled times.  To disable the schedule, set the "Select by:" field to None.


Use Weekly scheduling to run the task once or more per week.

Select the days of the week to run the Duplicate task, then select the start time.


Use Monthly scheduling to run the task once or more per month.

Two scheduling options are available:

  • The first option allows you to select a day of the month and run the task once every 1 to 6 months.
  • The second option allows you to select the first, second, third, or fourth occurrence of a day of the week and run the task every 1 to 6 months.

Morro Duplication Process

The Morro Duplication task is divided into three phases:

  1. Scan
  2. Seed
  3. Duplicate

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 file copy will not start and the Scan phase can be run multiple times. 

Phase 2 - Seed

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

Incremental Duplicate: Click Duplicate to begin the Seed phase.  During this phase, the source share can still be used normally.  Changes to the source share will be copied in subsequent seed phase runs.  When you are ready to run the final duplication, enable "Final Duplication" and do not use the source share.  Note that changes to the source share after starting the final duplication cannot be transferred to the destination share using the Duplicate app and may cause the final duplication to fail.

Note: Scheduled duplication tasks should use the incremental type.

Phase 3 - Duplicate

When the Duplicate phase begins, the files will be copied from the CacheDrive share to the destination share. The length of time required for the third phase depends on the amount of data that must be copied and how much out of cache data must be fetched from the cloud. The Duplicate window will show the progress and the process can be suspended and activated via the SUSPEND and ACTIVE buttons.

For standard duplication tasks, any modifications made to the source share will not be copied to the destination.

For incremental tasks, modifications will not be copied until the next duplication task run.


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.

Data Usage

The chart at the top of the page shows the amount of data copied using Duplicate.

Task Status

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

Task is being created.
Phase did not start.
Phase is scheduled to start at a later time.
(Blinking)Phase is running.
Incremental phase has completed successfully.
Phase has completed successfully.
Phase is waiting for another task to finish.
Task has entered the DUPLICATE phase and is copying data to the destination.
Phase has been suspended and can be re-activated.
Phase has failed, but will resume at a later time.
Phase has failed and will not resume.