From: Derek Downey
Date: October 26 2012 2:35pm
Subject: Re: Recover dropped database
List-Archive: http://lists.mysql.com/mysql/228504
Message-Id: <61132768-6645-43C6-B971-BEE34C7646C5@orange-pants.com>
MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

I do agree with Reindl that it is highly unlikely to work, but without =
specifics of how busy your DB is and how much write activity you have, =
it will at least give a shot for perhaps some data.=20

Derek Downey


On Oct 26, 2012, at 10:29 AM, Reindl Harald <h.reindl@stripped> =
wrote:

>=20
>=20
> Am 26.10.2012 16:15, schrieb Lorenzo Milesi:
>>> innodb will not be consistent if there are parts overwritten
>>> in the meantime or small pieces are not recovered 100%
>>=20
>> I took a lvm snapshot few minutes after the happening, and the sql =
server is barely used so it shouldn't be overwritten..
>=20
> this does not help you in any way
>=20
> making a LVM snapshot while mysqld is running
> makes even a incosistent backup per design
>=20
> so after dropa database ANY change and write back innodb
> buffers will resue the table space and overwrite data
>=20
> innodb is a large file with internal structures and you said:
> "Storage is innodb, no separate files for tables, everything is in =
ibdata1"
>=20
> so how do you imageine restore PARTYL contents of a large
> file which has to be also consistent with ib_logfile*
>=20
> sorry, but there is not tool doing magic if someone is
> missing at least daily backups to restore in the case
> of mistakes like yours
>=20
>=20
>=20
>=20