I recently upgraded MySQL servers from 5.5 to 5.6.11. In the process, I discovered that I needed to upgrade XtraBackup to the 2.0+ release family. Now that I’m using 2.1.3 to do backups, I’m unable to restore a backup functionally on a different machine.
The target machine is of the exact same operating system level, MySQL version, and XtraBackup version. My process for testing went like this…
- Make a backup of the current system: innobackupex --user=xxxxx --pasword=xxxxx --no-timestamp --no-lock /backup/mybackup
- Go into the /backup/mybackup directory and apply the log: innobackupex --user=xxxxx --password=xxxxxxx --apply-log .
- Copy the resulting directory to the new MySQL server using “rsync -avprP -e ssh” (as describing in the docs about making a slave)
- Set the file ownerhips for the whole directory.
- Attempt to start MySQL.
At this point, I got an error from the startup script indicating a startup error with regard to the PID file. However, I discoverd that the service started anyway. When I connect to the server and attempt to select information from the tables, I get the error “table xxxx doesn’t exist”.
What am I doing wrong?