From: Reindl Harald
Date: August 14 2012 8:08am
Subject: Re: Recovery from a MySQL dump is too long !
List-Archive: http://lists.mysql.com/mysql/227998
Message-Id: <502A0793.6030006@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigC7F1BC32E5660A43311C6473"

--------------enigC7F1BC32E5660A43311C6473
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable



Am 14.08.2012 09:42, schrieb Bob Sauvage:
> Hello *,=20
>=20
> My INNODB database has a size of 80GO. I've a replication setup on 3 sl=
aves and I backup my db from them.=20
> If a problem occurs on the database, a recovery from a dump takes aroun=
d 6H ! That's too long for us.=20
>=20
> 2 ideas :=20
> 1. Stop the slave and rsync the folder /var/lib/mysql to another server=

> 2. Stop the slave, take a dump and when it's finish, pull the dump in a=
nother MySQL instance daily.=20

i do the stop slave and rsync data-dir since many years
over WAN connections for offsite backups, never was a
friend of dumping databases to textfiles

if something is damaged due a power-interruption this
is also the fastest restore because rsync is much faster
even with --checksums as any dump


--------------enigC7F1BC32E5660A43311C6473
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.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAqB5MACgkQhmBjz394AnkcegCfVmINfF1Uuv5aY+sJOnPg1pIG
Zg0Anig3Tq18Q4Y6+5sMbtJlyd1QpQ6i
=YwMy
-----END PGP SIGNATURE-----

--------------enigC7F1BC32E5660A43311C6473--