https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31098 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|The option tohe option of |The options to "export |"export database" and |database" and "export |"export settings" are not |settings" are not available |available. | CC| |david@davidnind.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31098 --- Comment #2 from David Nind <david@davidnind.com> --- Hi victor. You've set things up to enable backups, but the actual backups need creating using koha-run-backups Example: koha-run-backups --days 2 --output /var/spool/koha Then the database and configuration backups will appear on the tabs to export the database and configuration. I'd imagine this could be setup as a cronjob. This is not documented in the manual, so I've added a documentation bug to do this: bug 31099 See also bug 14564 - there was some discussion there about allowing it or not, or removing the option. I'm not sure whether there needs to be a note or information on how to set this up, either: - in the koha-conf.xml file, or - on the export database and export configuration page. It definitely should be covered in the manual to help avoid confusion! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31098 --- Comment #3 from victor <vbovictor@gmail.com> --- is already defined in nano etc/cron.daily/koha-common koha-run-backups --days 2 --output /var/spool/koha however it is not generating backup koha-dump instance -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31098 --- Comment #5 from David Nind <david@davidnind.com> --- (In reply to victor from comment #4)

Would I need to set permission for /var/spool/koha ?

I think you are correct.

From bug 14564 comment 16 , then it set the permissions as root:kohadev-koha ownership and 640 permission.

This is so that the files can be read by the webserver for your Koha instance - kohadev-koha should be changed to whatever your instance name/file ownership persmissions should be - check the files under the koha to see what that should be. Not sure whether this is a regression, or it is something that needs to be set manually). I'm not the greatest at linux file permissions, so I might be worng! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31098 --- Comment #6 from David Nind <david@davidnind.com> --- A way to test could be to either: 1. run the command in the cron job manually to generate the backups and see if the files appear in the directory, or 2. create a file in the backup directory and see if you can see it in the staff interface, or If the files are in the directory, but you can't see them in the staff interface then it will be a permission problem. If the command doesn't generate the files, then check the logs for any errors (I'm not sure which logs to check..). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31098 Chris Cormack <chris@bigballofwax.co.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chris@bigballofwax.co.nz, | |gmcharlt@gmail.com Severity|critical |normal Component|bugs.koha-community.org |Staff Client -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.