Access Keys:
Skip to content (Access Key - 0)


1 About Backup and Restore

Print this page

Backup strategies for your configuration

To backup a Rhino SLEE, an administrator will typically use a combination of utilities, depending on backup requirements and the layout of Rhino nodes and the PostgreSQL instance. Common approaches include:

Backing up and restoring... using... to support...
individual nodes OS-level facilities such as LVM ...recovery after a node failure, by creating a snapshot of the volumes containing the Rhino installation and PostgreSQL data files.
This approach can be done on a per-node, per-database basis. (PostgreSQL may need to perform recovery when restoring from a disk snapshot.)
cluster-wide SLEE state the rhino-export utility (to save the management state of the SLEE), and the rhino-import utility (to restore the state to a new cluster) ...recovery from a cluster failure, recovery from data corruption, rolling back state to an earlier time, and migrating a cluster to a new version of Rhino.
You should also backup any modified or created files which are not stored in Rhino's management database (for example, using cron and tar). This applies to modified files under the Rhino installation (such as changes to security permissions or JVM options) and to any important generated output (such as CDR files).
subset of the SLEE state Partial imports ...restoring a subset of SLEE state, for example during development, after updating a set of SLEE components.
SLEE profile state Profile snapshots ...backing up only the state of SLEE profiles (a subset of the management state of the SLEE).
PostgreSQL database Standard PostgreSQL tools ...backing up the contents of the PostgreSQL management database.
For many deployments, the combination of disk-volume backups and rhino-export backups is sufficient.
Adaptavist Theme Builder Powered by Atlassian Confluence