xtrabackup failed to write metadata but the backup still succeeded
Bug #1623210 reported by
Julien Deloubes
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.2 |
Won't Fix
|
Undecided
|
Unassigned | |||
2.3 |
Fix Released
|
Medium
|
Sergei Glushchenko | |||
2.4 |
Fix Released
|
Medium
|
Sergei Glushchenko |
Bug Description
Hello,
using xtrabackup 2.4.4 on ubuntu server 14.04.
I'm trying to do a full backup of my percona DB on a remote machine using tar and extra-lsn-dir
Here is my command:
# innobackupex --defaults-
When doing this the directory /srv/extrabacku
No file containing the LSN info can be found.
Got the rights permissions on the folder, and log of the backup is saying that it had used the extra-lsn-dir option.
Is it a bug or just a syntax error?
tags: | added: xtrabackup-2.4 |
summary: |
- --extra-lsndir is empty + xtrabackup failed to write metadata but backup still succeeds |
summary: |
- xtrabackup failed to write metadata but backup still succeeds + xtrabackup failed to write metadata but backup still succeeded |
summary: |
- xtrabackup failed to write metadata but backup still succeeded + xtrabackup failed to write metadata but the backup still succeeded |
To post a comment you must log in.
Cannot reproduce with following command:
> innobackupex --extra- lsndir= $topdir/ lsn --stream=tar $topdir > /dev/null
> cat $topdir/ lsn/xtrabackup_ checkpoints
backup_type = full-backuped
from_lsn = 0
to_lsn = 1625987
last_lsn = 1625997
compact = 0
recover_binlog_info = 0