I agree with Robin. I've seen another system that does database dumps during the middle of the day while the database server is running, and the increased server load is quite significant. I'm also guessing that locking takes place as sometimes the load will skyrocket during this time. Besides the huge lowering of performance, your data might be inaccurate or even corrupt anyway since you might be doing a backup midway through a script action.
David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -----Original Message----- > From: [email protected] [mailto:koha-devel- > [email protected]] On Behalf Of Robin Sheat > Sent: Thursday, 19 November 2015 10:16 AM > To: [email protected] > Subject: Re: [Koha-devel] incremental backup of the DB > > Paul A schreef op wo 18-11-2015 om 17:49 [-0500]: > > Very interesting, can you share more details? > > Not really, I didn't implement it. > > But essentially it provides an offsite database replicant that can then be > backed up using snapshotting or whatever. I think regularly dumping a > running database would not be best practice, as it puts a significant load on > the server, and also may lock certain actions (don't quote me on that > though.) > > -- > Robin Sheat > Catalyst IT Ltd. > ✆ +64 4 803 2204 > GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF _______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
