Topic: Back Up Procedures For Kete
Topic type: Topic
Once you have Kete installed you will want to ensure that you set up a regular back up policy.
The following assumes that you have root (sudo) access or an account on your kete server with sufficient privileges. It also assumes that you have followed the suggested Deployment file hierarchy as outlined in these documents:
and
1) Backup /home/kete
This will backup almost everything including the Zebra DB and the source files. The suggestion is to do an incremental backup, rather than an try to do the entire mirror each night, as over time this will likely get quite large because of uploaded files.
2) Backup your Subversion repository
We suggest that your project's Subversion repository is backed up separately. This is where all the Kete source files and edits are stored case we want to easily restore the svn repository, without having to restore the rest of the directory structure (assuming that your SVN repository is on your production server). In some cases, you may already done this by doing step 1.
3) Dump your MySQL data bases. .
This could be either nightly dumps, as shown. Or you could setup a remote mirror. MySQL has some nice realtime replication that you can use if you have a second server that you can use.
mysqldump -udatabaseusername -pdatabasepassword --opt databasename
You probably want to dump your "mysql" database as well, since it keeps track of the various databases, db users, and their permissions.
4) The nginx web access logs and configuration files. If you followed the suggested installation, they are all under this directory:
/usr/local/nginx/
The nginx web access logs and configuration files are the only Kete specific thing, apart form the databases, that is stored outside of /home/kete.
5) Your Kete host(s) configuration. This is something beyond the scope of this document, but obviously you want to make sure you can recreate your Kete host(s) from scratch if necessary, given your backups, so make sure to figure out how your Kete host varies from default settings and back it up. On Debian, most of this stuff will be under /etc.
These things may be housed on a single host or multiple ones, but as long as they are backed up, you should be covered.
This guide was originally written by Russel Garlick with guidance and revision from Walter McGinnis, Kete Project Lead for Katipo.
