tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/2419-mysql-installation-configuration-doesnt-mention-innodb-binlogsCascade CMS: Discussion 2018-10-18T20:37:08Ztag:help-archives.hannonhill.com,2010-02-09:Comment/323136632014-03-28T19:35:44Z2014-03-28T19:35:44ZMySQL installation configuration doesn't mention InnoDB binlogs<div><p>I have noticed that the MySQL installation instructions make no
mention of InnoDB or its binary logs. While database type is
primarily an installer decision, MySQL has changed its default
database type from MyISAM to InnoDB for newer versions of MySQL. If
no prior MySQL installation on the selected Cascade DB server has
been done then a default InnoDB setup will not include any binary
logs. Repo (ib_logfile) files are included.</p>
<p>KnowledgeBase and Discussions search for "ib_logfile" fail to
find anything. So is there no recommendation, then, on using MySQL
binary log files when InnoDB is chosen (explicitly or by
default)?</p></div>leftfoottag:help-archives.hannonhill.com,2010-02-09:Comment/323136632014-03-28T19:55:36Z2014-03-28T19:55:36ZMySQL installation configuration doesn't mention InnoDB binlogs<div><p>Hi there,</p>
<p>I checked 2 possible pages that you may have found and they both
appear to mention that InnoDB is required. The pages I checked
are:</p>
<p><a href=
"http://help.hannonhill.com/kb/database/setting-up-the-database-mysql">
http://help.hannonhill.com/kb/database/setting-up-the-database-mysql</a><br>
<a href=
"http://www.hannonhill.com/kb/Database-Config/index.html">http://www.hannonhill.com/kb/Database-Config/index.html</a></p>
<p>You'll notice they both contain a line in Step 2:</p>
<blockquote>
<p>IMPORTANT: Make sure that your database is configured to use the
InnoDB storage engine.</p>
</blockquote>
<p>I agree that it is pretty easy to miss, so perhaps we need to
make this stand out more. Let me know if you've found other
instructions on our site that don't include that information.</p>
<p>As far as binary logging is concerned, we don't have any
information about it on these pages as you mentioned. I'm certainly
willing to add more information, it's just not something that has
come up often (not sure if that's good or bad!).</p>
<p>We use READ-COMMITTED isolation level on a very specific part of
the application and due to this, I don't believe statement-level
binary logging is compatible with the application if you happen to
be using statement-based replication. In the past, we've advised
others to use row-level binary logging with the software and this
seems to work fine for replication purposes.</p>
<p>Does that answer your question? Let me know if I can help any
further.</p>
<p>Thanks!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/323136632014-03-28T20:25:35Z2014-03-28T20:25:35ZMySQL installation configuration doesn't mention InnoDB binlogs<div><p>While MySQL binary logs are mentioned a lot with reference
to<br>
"replication", they also are mentioned relative to backups and
recovery, especially MySQL server crashes.</p>
<p>My primary interest at this point is in data backup. By default,
MySQL<br>
Repo (ib_logfile...) files are created and are recommended for
"crash<br>
recovery" but not so much for "normal" mysqldump and mysqlimport
though<br>
the MySQL manual does mention them being used if they exist.</p>
<p>However, having used MySQL bin logs in past local applications,
and<br>
knowing that they are "disk hogs" - I am wondering about the<br>
effectiveness of using them and whether I should consider changing
our<br>
Cascade CMS default MySQL configuration to make use of the bin logs
in<br>
addition the Repo logs. Will this provide a more comprehensive
backup<br>
and restore "landscape" or "scope" (without replication)?</p></div>leftfoottag:help-archives.hannonhill.com,2010-02-09:Comment/323136632014-03-31T14:24:57Z2014-03-31T14:24:57ZMySQL installation configuration doesn't mention InnoDB binlogs<div><p>I believe that the majority of our clients are running a
<code>mysqldump</code> operation nightly to create a full backup.
Then, if anything goes wrong and they have to restore a backup,
they know that they'll lose whatever changes have been made since
the last backup. This isn't necessarily a major problem because
it's a maximum of a day's worth of work being lost.</p>
<p>If you aren't performing nightly backups, I would consider
making use of the bin logs as they should allow for you to perform
point-in-time recovery. This way you could minimize the amount of
work lost should your database ever run into problems. Like you
mentioned, it does require a lot of disk space.</p>
<p>I'll be curious to see if any other clients can chime in here
based on their own MySQL environments.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/323136632014-03-31T15:08:09Z2014-03-31T15:08:09ZMySQL installation configuration doesn't mention InnoDB binlogs<div><p>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1</p>
<p>Right - I was thinking of providing "point-in-time" recovery
past a<br>
weekly DB dump, which "we" don't do right now. I do know that
using<br>
such bin logs needs to be carefully planned as they can get to
be<br>
quite huge and must be properly "trimmed".</p></div>leftfoottag:help-archives.hannonhill.com,2010-02-09:Comment/323136632014-03-31T21:47:48Z2014-03-31T21:47:48ZMySQL installation configuration doesn't mention InnoDB binlogs<div><p>One thing to note is that MySQL, as of a certain version (5.1?),
uses<br>
the InnoDB engine by default and no additional MySQL configuration
is<br>
required. Referring to the "MySQL Configuration" section might
be<br>
confusing, then, if someone believes that they are REQUIRED to use
all<br>
of the parameters shown in that MySQL document page "to enable
InnoDB".<br>
Where a version of MySQL does NOT use InnoDB as its "default
engine",<br>
THEN something needs to be done (MySQL command-line option, MySQL
DB<br>
setting, MySQL configuration file) to (force) the use of
InnoDB.</p>
<p>In "our" MySQL configuration files, running MySQL-5.1.71, there
are NO<br>
InnoDB parameters at all and ALL of the Cascade CMS tables have
an<br>
engine type of InnoDB:</p>
<p>use <code>cascade703</code>;</p>
<p>select table_name,Engine,table_rows from
information_schema.tables WHERE<br>
table_schema=DATABASE();<br>
+-------------------------------+--------+------------+ |
table_name | Engine | table_rows |
+-------------------------------+--------+------------+ |
DATABASECHANGELOG | InnoDB | 288 | | DATABASECHANGELOGLOCK | InnoDB
| 1 | | QRTZ_BLOB_TRIGGERS | InnoDB | 0 | ...</p>
<p>| cxml_workflowtriggerparameter | InnoDB | 0 | | cxml_xml |
InnoDB | 11913 |
+-------------------------------+--------+------------+ 93 rows in
set (2.27 sec)</p></div>leftfoot