InnoDB copy database from Server A to Server B, comes with error

xrz

So i rsynced InnoDB whole database from Server A to Server B, comes with error ->

this does not help either -> http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html

also rsync completed 100% files are 100% identical

2016-10-17T19:30:29.878799Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306

2016-10-17T19:30:29.878821Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2016-10-17T19:30:29.878868Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2016-10-17T19:30:29.890887Z 0 [Note] Event Scheduler: Loaded 0 events
2016-10-17T19:30:29.897539Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.15-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
2016-10-17T19:30:30.373786Z 2 [Note] Access denied for user 'root'@'localhost' (using password: NO)
2016-10-17T19:30:30.404281Z 0 [Note] InnoDB: Buffer pool(s) load completed at 161017 21:30:30
2016-10-17T19:30:34.294000Z 3 [ERROR] InnoDB: Page [page id: space=143, page number=237147] log sequence number 356694566313 is in the future! Current system log sequence number 356652097569.
2016-10-17T19:30:34.294025Z 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2016-10-17T19:30:34.294368Z 3 [ERROR] InnoDB: Page [page id: space=143, page number=1] log sequence number 356686127779 is in the future! Current system log sequence number 356652097569.
2016-10-17T19:30:34.294384Z 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2016-10-17T19:30:34.295221Z 3 [ERROR] InnoDB: Page [page id: space=124, page number=589114] log sequence number 356686336143 is in the future! Current system log sequence number 356652097569.
2016-10-17T19:30:34.295233Z 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2016-10-17T19:30:43.646667Z 4 [ERROR] InnoDB: Page [page id: space=143, page number=16385] log sequence number 356687735691 is in the future! Current system log sequence number 356652098307.
2016-10-17T19:30:43.646698Z 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.

ricardo

InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files.

Make sure you copy these

-rw-r-----  1 mysql mysql 13367246848 Oct 17 20:47 ibdata1
-rw-r-----  1 mysql mysql   536870912 Oct 17 20:47 ib_logfile0
-rw-r-----  1 mysql mysql   536870912 Oct  3 05:46 ib_logfile1

xrz

yes i did copied whole mysql data folder incl ibdata and logfile also when rsynced i stopped both mysql servers

ricardo

I came across the same thing a few years ago, IIRC it may just be differences the system's current dates. If it's a relatively small DB, just run the recovery process and it'll right itself, it may end up pruning some records but that may be easily managed/sorted.

xrz

yes there is different timezone, huh timezone matter ? i did never heard that

xrz

okay now how i can add other database from server C which is also innoDB? it wont recover or it does? as server C has another ib_logfile1

exception0x876

@xrz said:
okay now how i can add other database from server C which is also innoDB? it wont recover or it does? as server C has another ib_logfile1

Use mysqldump

xrz

done thx i mean before to copy ibd and frm files ...