xtrabackup: error: Tablespace keys are not reencrypted message each time while preparing backup

Bug #1582566 reported by Shahriyar Rzayev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Status tracked in 2.4
2.4
Fix Released
Medium
Sergei Glushchenko

Bug Description

Testing branch -> https://github.com/gl-sergei/percona-xtrabackup/tree/2.4-xb-re-encrypt

# Take Backup

/usr/local/xtrabackup/bin/xtrabackup --defaults-file=/etc/my.cnf --backup --keyring-file-data=/var/lib/mysql-keyring/keyring --server-id=0 --datadir=/var/lib/mysql/ --target-dir=/home/backup_dir/full/ --user=root --password=Baku12345# --no-version-check

# Prepare Backup

/usr/local/xtrabackup/bin/xtrabackup --defaults-file=/home/backup_dir/full/backup-my.cnf --prepare --keyring-file-data=/var/lib/mysql-keyring/keyring --reencrypt-for-server-id=5 --target-dir=/home/backup_dir/full

# Result:
InnoDB: 5.7.11 started; log sequence number 3848808469
xtrabackup: error: Tablespace keys are not reencrypted.
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 3848810432
160517 11:09:17 completed OK!

But I am able to recover from backup.

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-754

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.