OpenVZ Forum


Home » General » Support » openvz6 ploop backups and mysql innodb corruption
openvz6 ploop backups and mysql innodb corruption [message #53204] Mon, 12 March 2018 19:06 Go to previous message
Jcats is currently offline  Jcats
Messages: 15
Registered: May 2011
Location: FL
Junior Member
From: *cmdnnj.fios.verizon.net
Hello,

We are suffering from a critical issue with ploop backups.

Basically, in some instances, when restoring a ploop backup, MySQL fails to start because of Innodb corruption, example:

2018-03-12 18:04:35 7fd3d4864900 InnoDB: Error: page 818 log sequence number 71622558711
InnoDB: is in the future! Current system log sequence number 71620133300.
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.mysql.com/doc/refman/5.6/en/forcing-innodb-recove ry.html
InnoDB: for more information.

We use the following method to perform the backups:

https://openvz.org/Ploop/Backup#Image-based_backup

What would be the proper way to perform the backups to ensure we do not run into this problem? We fear if we ever had fatal issue with the node where all containers needed to be restored we would be stuck with many containers with innodb corruption.

[Updated on: Mon, 12 March 2018 19:06]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Previous Topic: OpenVZ7 - Migrate options: vzmigrate, ovztransfer.sh or prlctl migrate?
Next Topic: OpenVZ Maintenance Partnership program
Goto Forum:
  


Current Time: Thu Dec 13 15:52:19 GMT 2018