Alfresco Backup and Restore Step by Step

Alfresco Backup

Alfresco backup is a part of data security for any website or provider utilizing Alfresco CMS. Handy Backup allows Alfresco hot backup with all components including database, Solr 4 indexes and content folders, using different plug-ins to automatically access any data needed.

Download Handy Backup

Version 8.0.6, built on 2 October, 2019
105 MB

Advantages of Handy Backup as Alfresco Backup and Recovery Tool

Smart Alfresco Backup Tasks

Creating Smart Alfresco Backup Tasks

Set up your Alfresco backup and restore step by step with a convenient New Task Wizard, allowing you selecting any data you need, choose a storage for these data, tune up the backup operations such as incremental and differential backup, encrypt and compress stored data, schedule a task and so on.

Flexible Automating and Scheduling Policy

You can set up an Alfresco backup task to run at an exact time, with a repeating period from minutes to months, or force it to start when some crucial event happens (e.g. user logoff or USB drive insertion). In addition, you can keep many versions of the same dataset simultaneously, marked with time stamps.

Automatic Alfresco Backup

Cross-Platform Operations

The Cross-Platform Solution

You can make Alfresco backup from Windows or Linux machine by network, using either shared network resources or (preferably) a network-oriented Handy Backup solution as an Alfresco backup and recovery tool. Handy Backup supports native operations under Windows and Debian-based Linux.

Alfresco Backup Storages

With Handy Backup, you can feel free about selecting the backup storages for your Alfresco content. You can utilize such common data vaults as:

  • Local and external drives: USB, eSATA or FireWire drives, local drives and mapped disks.
  • FTP, SFTP and FTPS servers: any protocol for FTP exchanging with a data server and SSL/TLS.
  • Clouds: Google Drive, Amazon S3, Dropbox, Backblaze and any WebDAV cloud.
  • The dedicated backup vault: HBdrive service for safekeeping data (with a seeding option).
Storages for Alfresco Backup

Recommended Solution

Handy Backup Server Network

Version 8.0.6, built on 2 October, 2019. 105 MB
Backup Software from Novosoft LLC. 299 USD per license.

Handy Backup Server Network

The Server Network edition allows Alfresco backup and restore under the guidance of any modern Windows or Ubuntu-based Linux solution from a machine in a local network!
Free 30-days trial version!

How to Backup Alfresco Using Handy Backup

As for all CMS, the three main data components of Alfresco are the configuration, the database and the content. To make a consistent Alfresco backup, you must not only save these data but also preserve the relations between these data, as recommended on Alfresco official site!

The Logic of Alfresco Hot Backup

To ensure the good Alfresco backup and restore, you must perform the backup steps described above in a firmly established sequence, at least when the matters touch the “hot” backup! Swapping between these actions may cause inconsistences in the copies of Alfresco index files!

  • Save Solr 4 configuration files with the “Computer” plug-in (perhaps on a remote machine).

  • Adding the Computer Plug-in to Backup Set

  • Backup the Alfresco database using an appropriate plug-in from the “Database” group.

  • Adding the Database Plug-in to Backup Set

  • Finally, backup Alfresco content using the FTP, SFTP or FTPS plug-in for the content store folder.

  • Adding Data of the FTP Plug-in to Backup Set

Caveat: We are recommending you to create the three separate tasks for these steps, divided by scheduling for at least double time the program need to perform these operations (an exact time is completely a matter of current Alfresco content quantity and hardware efficiency).

You can get a detailed information about each step of creating a new task and using any of plug-ins mentioned above by studying the User Manual. Please take into account that, for Handy Backup, Alfresco backup operations have no principal differences among with any other backup activity.

Alfresco Recovery from Backup

We are strongly insisting that Alfresco recovery operations must not be scheduled (except planned cloning of Alfresco backup to another server!). An Alfresco recovery task can be fully automated by inside, although an administrator must always run it in a manual mode and be careful for consequences!

  • To recover Solr 4 indexes, firstly stop the Solr 4 server, then copy indexes and restart Solr 4.
  • The same is true to a database server (DBMS) utilized by Alfresco.

An advice: You can make the stop and restart actions automatic, by using the appropriate commands as the pre- and post-action at the Step 7 of the New Task Wizard!

Setting Pre- and Post- Actions

  • For the static content, you do not need for stopping and restarting. The main risk is to spoil the current content by replacing it with older files from backup having the same names.

As for Alfresco backup, the most convenient way to restore the CMS content is to create the three separate restoration tasks, each for one backup component, and run these tasks in a strict sequence described earlier to ensure the synchronization of restored information parts.

Note: Handy Backup preserves backups at native file formats (unless you select encryption and/or compression of your backup files). As a result, you can open, browse and even modify Alfresco backup folders, and extract the files you need from a backup with any file management tool!

Download Handy Backup

Version 8.0.6, built on 2 October, 2019
105 MB

Other Alfresco Backup and Restore Software

Alfresco has no internal backup and recovery tool. The user reference guide instructs to use an appropriate database backup tool to perform Alfresco backup. The Alfresco community develops some versions of a common backup script utilizing tools such as cron for scheduling and sh for making actions.

Caveat: These Alfresco community backup scripts are at least inconvenient and require significant skills to use properly, as well as lack an internal automation!

See also:


    Who uses our backup software?