The Synchronization module is used to synchronize a target instance with a source instance. It allows you to activate large amounts of content selectively. Only previously activated content is transferred to the target instance. You can use the module to create new public instances without shutting down your existing instances or impacting their ability to serve content.

Synchronization module benefits:

  • Traverses the node tree and activates only previously activated content. This ensures that content that was never activated is not published during synchronization.
  • If content was versioned upon activation (Magnolia default behavior), the module activates the last known version, making it possible to recover even modified content.
  • You can use the module to prepare additional public instances that are identical copies of current instances.


Download the Synchronization module from Magnolia Store or Nexus repository.


Synchronization an enterprise module. It is included in the add-ons folder of the Enterprise Edition bundle. To install the module , see the general module installation instructions.


See the general module uninstalling instructions and advice.

Use cases

Public instance failure

Imagine that you have two public Magnolia instances. Due to hardware failure one of them is out of operation for a few days. As you try to publish content during the outage, Transactional Activation tells you that the content cannot be activated because one of the public instances is down.

Since you really need to publish new content to the remaining public instance, you make a conscious decision to switch off the subscriber that suffered the hardware failure. Now you can publish the content while waiting for the failed hardware to be replaced.

A few days later hardware on the failed public instance has been replaced and the server is up again. You re-enable the subscriber so that all new content is activated to both public instances. But you still have a problem what to do with all the content that was published while the instance was down. Your options are:

  • Republish everything to both instances. This is a time-consuming process, generates high load, and slows down your site during publishing.
  • If you kept a list of the published pages, you know exactly what to activate to get them on both instances. This works well for small deployments with infrequent updates and a single editor.
  • Use the Synchronization module. Set the previously broken public instance as a synchronization subscriber and Magnolia will take care of synching the missing content.

Public instance blackout

All public instances are corrupted, broken or compromised. No instances exist to serve content. A small site can deal with this by creating a new public instance and publishing all content to it. This is difficult in large deployments that have many editors, where content has already been modified since the blackout took effect, and where some pages are not yet ready to be published across the site. Use the Synchronization module to activate any previously activated versions of content, even if the content was modified further, and skip any pages that were not previously activated.

High load

You have a sudden high load on your site. You need to add a new public instance to deal with the load.

  • You cannot shut down any of the existing public instances because you need them to deal with the load. This prevents taking a snapshot for cloning.
  • You cannot activate all content from the author instance to public instances since this would unnecessarily flush the cache on them and increase load when the servers are already busy.

The solution is to create a new empty public instance and use the Synchronization module to publish content only to that instance while the existing public instances keep serving content.


The Synchronization module is configured in /modules/synchronization.

Note that the mgnlSystem and mgnlVersion workspaces cannot be synchronized using the Synchronization module or Synchronization tool tool.

Synchronization command

Synchronization is controlled by the SynchronizationCommand (extends BaseActivationCommand) registered in /modules/synchronization/commands/synchronization:

Synchronization subscribers

Target instances are configured as synchronization subscribers. A synchronization subscriber is different from a normal subscriber and configured in a different place.

A number of example synchronization subscriber configurations are provided in /modules/synchronization/commands/synchronization/synchronize/subscribers/subscriptions. Individual synchronization subscriptions are configured in in exactly the same way as normal subscriptions

To configure a synchronization subscriber, copy and adapt an example configuration.


  • fromURIPath on the author instance from which the content is activated.  
  • repositoryName of the workspace.
  • toURI: Target instance path.
  • active: Set to true to enable the synchronization subscriber.

Manual synchronization

The Synchronization tool allows you to manually synchronize content between author and a single public instance. The operation is performed asynchronously. You can access the tool at Tools > Synchronization.

To perform a manual synchronization:

  1. Select the workspace.
  2. Type the path to be activated.
  3. Optionally select the checkbox to activate all child nodes recursively
  4. Click Start Synchronization. Synchronization starts within one minute of execution.
  5. Refresh to see the current status of the synchronization.

Path examples:








All website pages.




history page only




All pages under about page.




User jsmith only.




All admin level users.

Before synchronizing the data workspace, make sure the data type root path ( / ) is activated.

Scheduling synchronization

You can schedule synchronization jobs using the Scheduler module. The purpose of scheduling is not to synchronize an instance repeatedly, because this leads to unnecessary flushing of the cache and increases load. The aim is to schedule the sync to occur at a convenient later time such as during low traffic volume.

To configure a synchronization subscriber, copy the /modules/scheduler/config/jobs/demo node and edit its properties.


  • <job name>: Name of the job, sync-news in our example.
    • params: Parameters passes to the command. SynchronizationCommand expects/allows the following parameters
      • path: Path to the content, for example demo-project/news-and-events.
      • recursive: Set to true to synchronize the node and subnodes.
      • repository: Workspace where the content resides, for example website.
    • active: Set to true to enable the job.
    • catalog: Name of the catalog where the command resides. The synchronize command resides in the synchronization folder.
    • command: Name of the command definition node, synchronize.
    • cron: Schedule that indicates the execution time, written as a CRON expression. In our example 0 0 1 5 2 ? 2014 will run the job on February 5 at 01:00 am.
    • description: Job description.

Test the synchronize command un-scheduled first. If it runs correctly, schedule it to publish to a new public instance after one minute (CRON expression: 0 * * * * ?). If this works correctly too, point the subscriber configuration to the out-of-sync target instance and modify the CRON schedule as required.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))