Skip to main content
NetApp Knowledge Base

MySQL services failed to start in AIQUM RHEL after restore from RHEL ReaR backup

  1. Last updated
  2. Save as PDF
Views:
40
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
OM
Last Updated:

Applies to

  • ActiveIQ Unified Manager (AIQUM) 9.x
  • RedHat Linux (RHEL)
  • Redhat Relax and Recover (ReaR)

Issue

  • MySQL services fail to start after reverting to the ReaR backup taken prior to upgrade
  • MySQL has several inconsistency issues with innodb/ibd files/redo log sequences
  • examples in error.log:
[ERROR] [MY-013171] [InnoDB] Cannot boot server version 80032 on data directory built by version 80034. Downgrade is not supported
mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )
[ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
[ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
[ERROR] [MY-010119] [Server] Aborting
[System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.32)  MySQL Community Server - GPL.
 
[System] [MY-013576] [InnoDB] InnoDB initialization has started.
[ERROR] [MY-013882] [InnoDB] Missing redo log file ./#innodb_redo/#ib_redo8390 (with start_lsn = 2002805893120).
[ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
[ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
[ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
[ERROR] [MY-010119] [Server] Aborting
[System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.32)  MySQL Community Server - GPL.
 
[ERROR] [MY-011971] [InnoDB] Tablespace 'netapp_model/volume' Page [page id: space=236467, page number=240] log sequence number 2002761396092 is in the future! Current system log sequence number 2002761312278.
[ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.0/...-recovery.html for information about forcing recovery.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.