You are looking at documentation for an older release. Not what you want? See the current release documentation.
The eXo Platform data consists of 2 parts:
data directories that can be backed up and restored using the OS utilities.
JCR, IDM and JPA datasources that can be backed up and restored using the DBMS tools.
These two parts need to be backed up and restored consistently. Inconsistency may lead to failures and exceptions at the eXo Platform runtime. During the backup, you should stop eXo Platform to make sure no write-process is performing.
You may back up periodically or on-demand, before an upgrade or a patch for instance. If you are planning to back up periodically, consider the following things:
How often the backup is performed? Remember that there is downtime during the backup.
How much disk space is used for backup storage? Less space, less archive.
Prepare for the tools that involve: copy (local and network), compress and decompress tools, SQL backup tools and automation.
If your backup takes long time and occupies a big memory space, here are some tips:
The downtime will be much shorter if you have File System data and SQL data located on different hard drives, and back up them in parallel.
Try optimizing your database server to restore faster.
You do not need full-backup all the time. There are 2 backup options: incremental and differential that may lower the space. The backup approaches are explained here. Linux rsync and Windows backup utilities can perform incremental/differential backup. Any SQL Database server should support incremental backup.
Think of automation which can be used for your backup.