Encrypted files are not removed after innobackupex --decrypt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
High
|
Unassigned | ||
2.3 |
Triaged
|
High
|
Unassigned |
Bug Description
The bug https:/
If the encryption key is incorrect it could be detected by decrypting a file with predefined content before decrypting all files.
If encrypted files are not removed incremental backup failed:
innobackupex: Starting to copy non-InnoDB files in 'inc'
innobackupex: to the full backup directory '/srv/backup-
innobackupex: Copying 'inc/xtrabackup
innobackupex: got a fatal error with the following stacktrace: at /usr/bin/
Steps to reproduce:
innobackupex --encrypt=AES256 --encrypt-
Get LSN info from xtrabackup_info, because xtrabackup_
innobackupex --encrypt=AES256 --encrypt-
Decrypt both:
innobackupex --decrypt=AES256 --encrypt-
prepare full backup:
innobackupex --apply-log --redo-only .
apply incremental log:
innobackupex --apply-log . --incremental-
It will be fixed with implementation of https:/ /blueprints. launchpad. net/percona- xtrabackup/ +spec/checksum- unencrypted- chunk
Currently we don't have enough information to verify that decryption was successful.