Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
marsalapel
Starting Member
1 Post |
Posted - 2015-02-08 : 13:56:26
|
mysql log file see next message after starting:"InnoDB: Your database may be corrupt or you may have copied the InnoDB."How do I fix it?Thanks |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2015-02-08 : 14:03:59
|
I would post your question on a MySql forum site. SQLTeam is for Microsoft SQL Server.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
jeroennetters
Starting Member
1 Post |
Posted - 2015-04-26 : 19:43:25
|
Shutting Down and Restoring a Databasemysqladmin --defaults-file=/usr/local/mysql/my.cnf --user=root --password shutdownmysqlbackup --defaults-file=/usr/local/mysql/my.cnf --backup-dir=/export/backups/full copy-backNoteThe restored data includes the backup_history table, where MySQL Enterprise Backup records details of each backup. Restoring this table to its earlier state removes information about any subsequent backups that you did. This is the correct starting point for future incremental backups, particularly those using the --incremental-base option.ImportantBefore restoring a partial backup, you might need to delete first from the backup the .frm files associated with InnoDB tables that were not backed up.For more different ways for Innodb corruption issues see http://www.sqlservercentral.com/Forums/Topic1618894-2893-1.aspx |
|
|
|
|
|