OOoopppsss! I do mean for recovery/continual backup. I will do it
manually, but basically get all the data on a USB disk and be able to
recover/move it (the data) on another machine, the same machine etc..
I hope I did not just open up a can of worms. We just went live and
this post gave me a rude
Am 21.11.2013 13:51, schrieb Paul Halliday:
> Had a system crash this morning and I can't seem to get mysql back up
> and running. This is the error:
>
> InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
> 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
>
2013/11/21 Reindl Harald
>
> Am 21.11.2013 13:51, schrieb Paul Halliday:
> > Had a system crash this morning and I can't seem to get mysql back up
> > and running. This is the error:
> >
> > InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
> > 18 19 20 21 22 23 24 25 26 27 2
Hello Nick,
On 11/21/2013 10:32 AM, Nick Cameo wrote:
OOoopppsss! I do mean for recovery/continual backup. I will do it
manually, but basically get all the data on a USB disk and be able to
recover/move it (the data) on another machine, the same machine etc..
I hope I did not just open up a can
What is the best way to backup your database. Which are the files that
I need to store on a usb disk
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
It was indeed corruption :/ what a day. I was able to move everything
over to another partition and have managed to get mysql up and running
again. There was a single file I could not, an .idb (the ,.frm is
there). Is it possible to fix this from ibdata or the logs?
Thanks.
On Thu, Nov 21, 2013
Am 21.11.2013 18:59, schrieb Paul Halliday:
> It was indeed corruption :/ what a day. I was able to move everything
> over to another partition and have managed to get mysql up and running
> again. There was a single file I could not, an .idb (the ,.frm is
> there). Is it possible to fix this fr
