Reply to thread

Message

Since the switch of MySQL to 5.6 and the usage of InnoDB I'm experiancing that after a crash or forcefully restart without closing the Server properly you have a rather good chace to "kill" some of the tables in your db's. Most of teh time aRapir will help - anyway - with InnoDB it seems to be a little tricky as the standard repair task does not doe certain tasks as it did with myisam.

Anyway - I thought if someone has the same issues I post the solution for me - repair and backup.

Repair Task:

cd c:\Program Files\MySQL\MySQL Server 5.6\bin
mysqlcheck.exe -u root -pMediaPortal --auto-repair --all-databases

Backup:

For the backup I found a good working batchfile originating here: RED OLIVE INC. - www.redolive.com which only needed some small modifications (the get date was not working so I have included another routine). Basically what it does is to dump your databases to a defined location with date and time and compress them to a zipfile. The configuration steps are explained in the batchfile.

<blockquote data-quote="pur_berger" data-source="post: 1122685" data-attributes="member: 50701">Since the switch of MySQL to 5.6 and the usage of InnoDB I'm experiancing that after a crash or forcefully restart without closing the Server properly you have a rather good chace to &quot;kill&quot; some of the tables in your db's. Most of teh time aRapir will help - anyway - with InnoDB it seems to be a little tricky as the standard repair task does not doe certain tasks as it did with myisam.Anyway - I thought if someone has the same issues I post the solution for me - repair and backup.Repair Task:cd c:\Program Files\MySQL\MySQL Server 5.6\binmysqlcheck.exe -u root -pMediaPortal --auto-repair --all-databasesBackup:For the backup I found a good working batchfile originating here:&nbsp; <a href="http://www.redolive.com/utah-web-designers-blog/automated-mysql-backup-for-windows/" target="_blank">RED OLIVE INC.&nbsp; - www.redolive.com</a> which only needed some small modifications (the get date was not working so I have included another routine). Basically what it does is to dump your databases to a defined location with date and time and compress them to a zipfile. The configuration steps are explained in the batchfile.</blockquote>

[QUOTE="pur_berger, post: 1122685, member: 50701"] Since the switch of MySQL to 5.6 and the usage of InnoDB I'm experiancing that after a crash or forcefully restart without closing the Server properly you have a rather good chace to "kill" some of the tables in your db's. Most of teh time aRapir will help - anyway - with InnoDB it seems to be a little tricky as the standard repair task does not doe certain tasks as it did with myisam. Anyway - I thought if someone has the same issues I post the solution for me - repair and backup. Repair Task: cd c:\Program Files\MySQL\MySQL Server 5.6\bin mysqlcheck.exe -u root -pMediaPortal --auto-repair --all-databases Backup: For the backup I found a good working batchfile originating here: [URL='http://www.redolive.com/utah-web-designers-blog/automated-mysql-backup-for-windows/']RED OLIVE INC. - www.redolive.com[/URL] which only needed some small modifications (the get date was not working so I have included another routine). Basically what it does is to dump your databases to a defined location with date and time and compress them to a zipfile. The configuration steps are explained in the batchfile. [/QUOTE]