May 24, 2012

Comment: How to recover a single InnoDB table from a Full Backup

… sequence number 6094071743825 InnoDB: is in the future! Current system log sequence number 6087296438643. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev…

Comment: Connecting orphaned .ibd files

… sequence number 30042909687 InnoDB: is in the future! Current system log sequence number 14824393635. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev… sequence number 34414181181 InnoDB: is in the future! Current system log sequence number 14824393635. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev…

Comment: Connecting orphaned .ibd files

… 56436. May 16 14:19:30 debian mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB May 16 14:19:30 debian mysqld: InnoDB: tablespace but not the InnoDB log files. See May 16 14:19:30 debian mysqld: InnoDB: http…

Post: When would you use SAN with MySQL ?

you have MySQL/server restart you may have warmup beingInnodb specifics ? First, in MySQL if you‘re looking for durable transactions the log write latency is triple important compared to other databasethe Firmware may have a glitch causing failure and data corruption

Post: Recovery beyond data restore

the master ? This is when you have master data lost, such as you have RAID or disk failure. Though it also can be things like Innodb corruption orbe one of these 3 protocols, but you can also take as shortcut) – for example you may have master or relay binary log corruption. Master or

Post: Using LVM for MySQL Backup and Replication Setup

Innodb if it is closer to you. In other cases snapshot may be implemented by tripple-mirroring. Ie you have RAID1 volume but there are 3 copies