Hello, Le mercredi 02 mars 2011 21:30:17, Phil Stracchino a écrit : > > You have to know that until mysql 5.1.21 and with a special configuration > > option that breaks the replication (if used), you can't run two batch > > insertion process at the same time on innodb. > > > > see > > http://sf.net/apps/wordpress/bacula/2009/11/12/handle-multiple-jobs-in- > > parallel-with-innodb/ > > Just looked at that. I note that innodb_autoinc_lock_mode=2 does not > *break* MySQL replication per se, but is unsafe with statement-based > replication. It is entirely safe with row-based replication. I don't > actually know how it interacts with replication mode MIXED, which > permits both row and statement replication events at MySQL's discretion, > but I will see what I can find out.
Ok, it doesn't *break* all forms of MySQL replication, but as this option can create problems with replication, I just advise to read carefully the MySQL documentation to ensure that everything is ok with the choosen replication process. Nothing worst than skipping the Catalog backup because we have a nice replication process, and discover after a problem (that can be replicated too), that the slave database is corrupted... Bye -- Need professional help and support for Bacula ? Visit http://www.baculasystems.com ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
