Page 1 of 1

Backup strategy

PostPosted:Wed Jan 01, 2014 11:11 am
by JoergPalmer
For some time I'm using OpenKM for personal purposes. In terms of technology my archive sure is rather small, maybe in a range of <1000 documents ... but growing ;)

My question is, what do I need to backup to be able to restore after a disaster? Obviously the repository folder and everything below needs to be stored. What else would I need? Is the database part of the repository folders? The only other thing coming to my mind is the .cfg file. Please tell me from your experiences, what do you guys backup? Is there an "officially" blessed way of doing this?

Re: Backup strategy

PostPosted:Thu Jan 02, 2014 5:34 pm
by jllort
Here you got specific section talking about backup http://wiki.openkm.com/index.php/Installation_Guide I suggest take a look here http://wiki.openkm.com/index.php/Backup ... -_MySQL.29

If you have not installed OpenKM with MySQL and you're using default embeded database (HSQL) I suggest move to Mysql, because HSQL is not good election for middle, large repositories and with MySQL you'll get more control.

Re: Backup strategy

PostPosted:Fri Jan 03, 2014 9:14 am
by JoergPalmer
jllort wrote:Here you got specific section talking about backup http://wiki.openkm.com/index.php/Installation_Guide I suggest take a look here http://wiki.openkm.com/index.php/Backup ... -_MySQL.29

If you have not installed OpenKM with MySQL and you're using default embeded database (HSQL) I suggest move to Mysql, because HSQL is not good election for middle, large repositories and with MySQL you'll get more control.
Thank you for the link, I must have overlooked it :( I have moved to MySQL as the database now, following the procedure described here.

I also have activated the MySQL backup script. Now my backups should be complete ;-)

Re: Backup strategy

PostPosted:Sat Jan 04, 2014 11:11 am
by jllort
If you want to be completelly sure, good practice is restore backup to other server. That's a good way to certify you're doing things correctly.