Doing backups is not part of Gentics Content.Node – doing backups 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.
The following steps may vary, depending on your system. Please adapt your steps accordingly.
1 Database Backup
Create a backup of your MySQL database.
# stop Gentics Content.Node /Node/bin/nodectl stop # stop Apache service service apache2 stop # dump the database mysqldump --max_allowed_packet=512M -u root -h 127.0.0.1 -P 42006 -p node_utf8 > /Node/tmp/node_utf8.sql # NOTE: You can decide if want to backup any contentrepositories # mysqldump --max_allowed_packet=512M -u root -h 127.0.0.1 -P 42006 -p contentrepository > /Node/tmp/cr.sql
2 File Backup
This is the recommended way to backup your system
Backup your database first
# 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
3 Differential Backup
Backup your database first
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