I'm using the following mysqldump command within a for loop in a shell script to create
the dump. We have a centralized MySQL server that houses all of our databases, and some
are extremely large:
## this part of shell script creates an array of database names
databases=`/opt/pkgs/mysql/bin/mysql --user=$USER --password=$PASSWORD -e "SHOW
DATABASES;" | tr -d "| " | grep -v Database |grep -v searches |grep -v weeding`
## this part of shell script loops through the database array and creates the individual
for db in $databases; do
/opt/pkgs/mysql/bin/mysqldump --force --single-transaction --opt --user=$USER
--password=$PASSWORD --databases $db > "/apps/Dbbackup/jamen/$db.dmp"
And yes, we do have a mix of InnoDB & MyISAM engine types, but each database itself is
one or the other (so not a mix of tables with these), which I just discovered.
Systems Services Librarian
Vanderbilt University Library
From: Suresh Kuna [mailto:sureshkumarilu@stripped]
Sent: Monday, July 15, 2013 10:48 AM
To: Johan De Meersman
Cc: McGranahan, Jamen; Replication
Subject: Re: 2 slaves - one Master; continues to fail
Can you paste you backup mysqldump statement ? ( It should not occur if that is consistent
) and secondly I'm thinking about mixed engine types in a transaction can also cause such
Remember though we set slave's to read only, the super user's can still do the writes. So,
drop any such user's privileges.
On Mon, Jul 15, 2013 at 11:24 AM, Johan De Meersman
----- Original Message -----
> From: "Jamen McGranahan"
> Subject: RE: 2 slaves - one Master; continues to fail
> Thanks for this message. I'm assuming the percona tool needs to be
> installed on the MASTER host? Is that correct?
They're useful everywhere, really :-) For this usage, I do believe the master will
Unhappiness is discouraged and will be corrected with kitten pictures.
MySQL & MongoDB DBA