Foolproof backup suggestions
I am donating a server with Koha 3.12 on Debian 7 via packages for a school in Vanuatu and would like suggestions for a simple backup strategy. The 'server' will not actually be network connected, so it will be used as a standalone workstation (at least to begin with). There will be no technical support available. My first thought was to use koha-run-backups and change the location to the desktop of the user that will access Koha. With the thought they could drag and drop the backup folder to a usb drive when needed. But it appears the --location: argument does not work with koha-run-backups. Since I am a novice scripter I am reluctant to go this path for fear of making a mess that I can't fix from thousands of KMs away. I doubt the machine will run 24/7. Any suggestions would be gratefully received. A little of the backstory: http://www.edgazette.govt.nz/Articles/Article.aspx?ArticleId=8749 many thanks, Clint.
On 17 September 2013 09:39, clint.deckard <clint.deckard@frontiers.co.nz> wrote:
I am donating a server with Koha 3.12 on Debian 7 via packages for a school in Vanuatu and would like suggestions for a simple backup strategy. The 'server' will not actually be network connected, so it will be used as a standalone workstation (at least to begin with). There will be no technical support available. My first thought was to use koha-run-backups and change the location to the desktop of the user that will access Koha. With the thought they could drag and drop the backup folder to a usb drive when needed. But it appears the --location: argument does not work with koha-run-backups.
Since I am a novice scripter I am reluctant to go this path for fear of making a mess that I can't fix from thousands of KMs away.
Use ln -s to logically link that directory to the users home dir eg sudo ln -s /var/spool/koha/<sitename> /home/<username>/backups Or something very similar to that, and then train them to copy the files to a usb drive on a regular basis. It's not exactly foolproof, because it relies on them remembering to do it. Chris
clint.deckard schreef op di 17-09-2013 om 09:39 [+1200]:
My first thought was to use koha-run-backups and change the location to the desktop of the user that will access Koha. With the thought they could drag and drop the backup folder to a usb drive when needed. But it appears the --location: argument does not work with koha-run-backups.
That's a bug that ought to be fixed. However, an option would be to leave the backups where they are, but have a cron job that runs after the backup happens, and copies the files somewhere else (the desktop, an external harddrive, etc.) This also means that you have two backup copies: one on the server, and one in the location off the server that the files go to. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
I use a script with this name "automysqlbackup.sh.2.5" It will make backup of koha database. It will do the backup by day, by week and by month In the example above it will do it to the /backup folder but you can change it to any folder (Ex: a Dropbox folder to be uploaded automatically ;) ) *1- STEP:* Change the Username, Password, Backupdir and email Some of the fields have " others have ' and other have nothing. It is like that. # Username to access the MySQL server e.g. dbuser USERNAME=*mysql_root_user* # Username to access the MySQL server e.g. password PASSWORD=*'password_of_mysql_root' * # Host name (or IP address) of MySQL server e.g localhost DBHOST=localhost # List of DBNAMES for Daily/Weekly Backup e.g. "DB1 DB2 DB3" DBNAMES="koha" # Backup directory location e.g /backups BACKUPDIR=*"/backups"* # Mail setup # What would you like to be mailed to you? # - log : send only log file # - files : send log file and sql files as attachments (see docs) # - stdout : will simply output the log to the screen if run manually. # - quiet : Only send logs if an error occurs to the MAILADDR. MAILCONTENT="stdout" # Set the maximum allowed email size in k. (4000 = approx 5MB email [see docs]) MAXATTSIZE="4000" # Email Address to send mail to? (user@domain.com) MAILADDR=*"mail@test.com"* *2- STEP:* On terminal: sudo crontab -e Insert the 2ª line: # m h dom mon dow command 0 2 * * * /home/koha/./automysqlbackup.sh.2.5 ----- Koha version: 3.08.04 - - José Anjos -- View this message in context: http://koha.1045719.n5.nabble.com/Foolproof-backup-suggestions-tp5770635p577... Sent from the Koha-general mailing list archive at Nabble.com.
I'm sorry but the script was not complete so I'm sending a link to download: https://dl.dropboxusercontent.com/u/726404/automysqlbackup.sh.2.5 <https://dl.dropboxusercontent.com/u/726404/automysqlbackup.sh.2.5> ----- Koha version: 3.08.04 - - José Anjos -- View this message in context: http://koha.1045719.n5.nabble.com/Foolproof-backup-suggestions-tp5770635p577... Sent from the Koha-general mailing list archive at Nabble.com.
Hi, On Tue, Sep 17, 2013 at 3:09 AM, clint.deckard <clint.deckard@frontiers.co.nz> wrote:
I am donating a server with Koha 3.12 on Debian 7 via packages for a school in Vanuatu and would like suggestions for a simple backup strategy. The 'server' will not actually be network connected, so it will be used as a standalone workstation (at least to begin with). There will be no technical support available. My first thought was to use koha-run-backups and change the location to the desktop of the user that will access Koha. With the thought they could drag and drop the backup folder to a usb drive when needed. But it appears the --location: argument does not work with koha-run-backups.
Year and half back i faced field conditions very similar in terms of almost no post-deployment support. I cooked up a couple of scripts around koha-run-backups. Have a look at this video, if you thing something like this will be useful, I'll share the scripts and instructions on the Koha wiki http://www.youtube.com/watch?v=ZwuBs0KqlSw (apologies for the poor vidcap quality) cheers -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org
participants (5)
-
anjoze -
Chris Cormack -
clint.deckard -
Indranil Das Gupta -
Robin Sheat