From: Reindl Harald
Date: October 26 2012 1:46pm
Subject: Re: Recover dropped database
List-Archive: http://lists.mysql.com/mysql/228500
Message-Id: <508A9420.8010608@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig0A1D1BCFD7656E38E38DC27D"

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



Am 26.10.2012 15:33, schrieb Lorenzo Milesi:
> Hi.
> Dramatic situation: unwanted database drop.
> Obviously I don't have a dump, because of other issues...
>=20
> Question: is it possible to recover something?
> Storage is innodb, no separate files for tables, everything is in ibdat=
a1.
> I started recovering .frm files using ext3grep, but the problem is the =
data itself.

forget it

innodb will not be consistent if there are parts overwritten
in the meantime or small pieces are not recovered 100%

sounds like learning backups the hard way


--------------enig0A1D1BCFD7656E38E38DC27D
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://www.enigmail.net/

iEYEARECAAYFAlCKlCAACgkQhmBjz394AnnggACeLbx3X4tB6a5DxiFiAMfyDJjh
b6QAn26ANgqWjaVFOtQhsUQoL6PcZCVt
=a1E7
-----END PGP SIGNATURE-----

--------------enig0A1D1BCFD7656E38E38DC27D--