Backup is not part of Gentics Content.Node – backup is part of each customer’s liability.
Backing up database tables while Gentics Content.Node is up and running will most certainly lead to data inconsistencies.
1 Full Backup
This is the recommended way to backup your system
# stop Gentics Content.Node /Node/bin/nodectl stop # create a full backup tar cvfz /backup/Node-`date +%F`.tar.gz /Node # start Gentics Content.Node /Node/bin/nodectl start
2 Differential Backup
rdiff-backup
allows you to restore the system to a state at a given point in time.
# stop Gentics Content.Node /Node/bin/nodectl stop # create backup using rdiff-backup rdiff-backup /Node/ /backup/Node # start Gentics Content.Node /Node/bin/nodectl start
3 Individual Backup Script
If you choose this method to backup your system Gentics Content.Node only parts of Gentics Content.Node will be backed up. Restoring this kind of backup to a newer version of Gentics Content.Node may fail as database table structures change with ongoing development of the product.
This type of backup can lead to an inconsistent state as editors may be able to modify data during mysqldump
is still running. Also changes to files stored in Gentics Content.Node are backed up in a second step – thus inconsistencies may be created using this method.
# create a database dump mysqldump -e -u root > /Node/tmp/node_utf8.sql # backup data files tar cvfz /backup/Node-`date +%F`.tar.gz /Node/etc/ /Node/node/ /Node/tmp/node_utf8.sql /Node/apache/htdocs