From: Reindl Harald
Date: September 9 2011 9:18am
Subject: Re: running a duplicate database
List-Archive: http://lists.mysql.com/mysql/225686
Message-Id: <4E69D9D1.5030309@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig99FE7C76D1C47011D5B98D59"

--------------enig99FE7C76D1C47011D5B98D59
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 09.09.2011 11:09, schrieb Dave Dyer:
> Is there a halfway house between a single database and a full master-sl=
ave setup?
>
> I have a database with one "piggish" table, and I'd like to direct quer=
ies that search the pig to a duplicate database, where it won't affect al=
l the routine traffic. =20
>
> I could definitely do this by setting up a slave server, but for my pur=
poses it would be just as effective, and lots easier, if mysql could auto=
matically maintain a duplicate of the database.  Presumably this would wo=
rk internally like an internal auto-slave, with a binary log of changes t=
o the master database self-consumed to maintain the duplicate.
>
> As a bonus, I could backup the duplicate instead of the master, so that=
 won't affect the routine traffic either.

you can run as many slaves on the same machine as you want by
using a different port for all instances and stop/backup/start
one of them per script - doing this since years

it makes no sense "maintain a duplicate of the database"for backups
becasue mysqld have to be stooped for effective rsync-backups which
are much faster as dumps and here are we again at the point using
a slave on a different port


--------------enig99FE7C76D1C47011D5B98D59
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5p2dEACgkQhmBjz394Anln1QCfQ3S1+gLDg9+WxzGCUUDIpiuJ
oEsAn23JihnbseEW+eA4WPv2HXVDV2pM
=IGFZ
-----END PGP SIGNATURE-----

--------------enig99FE7C76D1C47011D5B98D59--