Percona XtraBackup moved to https://jira.percona.com/projects/PXB

new feature: version info

Bug #1133017 reported by Matthew Kent on 2013-02-25

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Percona XtraBackup moved to https://jira.percona.com/projects/PXB	Fix Released	Wishlist	George Ormond Lorch III	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.2.1-alpha1
	2.1	Won't Fix	Wishlist	Unassigned
	2.2	Fix Released	Wishlist	George Ormond Lorch III	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.2.1-alpha1

Bug Description

Hi guys!

As we continue to expand the number of mysql versions we are using I'm finding myself in a position where I want to include the version information for mysql/xtrabackup/innobackex running at the time of backup. This is easy to write out to a file but impossible to include with the backup right now. To keep this tightly coupled with the backup data I'd like to include it within the copy/tar as well so it's impossible to lose.

For consideration is a patch to do just that, it adds a file, xtrabackup_backup_info, within the backup that includes the mysql, xtrabackup and innobackupex versions.

Wrote this against 2.0.5. Passes testrun.sh and includes it's own tests.

Tags:

Related branches

lp://staging/~gl-az/percona-xtrabackup/BT-32889-history-on-server-2.2

Merged into lp://staging/percona-xtrabackup/2.2 at revision 4879

Alexey Kopytov (community): Approve on 2013-09-25

Revision history for this message

Matthew Kent (mkent) wrote on 2013-02-25:

#1

0001-Write-out-xtrabackup-mysql-and-innobackupex-versions.patch Edit (7.3 KiB, text/plain)

Revision history for this message

Stewart Smith (stewart) wrote on 2013-02-26:

#2

Thanks for the patch! I'd like us to look at including this in the XtraBackup 2.1 tree.

Changed in percona-xtrabackup:
importance:	Undecided → Wishlist
status:	New → Fix Committed

Revision history for this message

Matthew Kent (mkent) wrote on 2013-03-13:

#3

Thanks! Looks like it's marked as fix committed but I can't see it upstream (or I'm misunderstanding how launchpad works). Is this still pending review?

Revision history for this message

Matthew Kent (mkent) wrote on 2013-03-18:

#4

Ping?

Revision history for this message

Laurynas Biveinis (laurynas-biveinis) wrote on 2013-03-19:

#5

Matthew -

Thank you for the patch. It is still pending review.

Revision history for this message

Alexey Kopytov (akopytov) wrote on 2013-03-19:

#6

Hi Matt,

This request is closely related to https://blueprints.launchpad.net/percona-xtrabackup/+spec/history-on-the-server. I've updated it with some comments referencing this bug and the contributed patch. I think it would be reasonable to implement this request along with the history-on-the-server BP.

Thanks.

Revision history for this message

Matthew Kent (mkent) wrote on 2013-06-10:

#7

2.1.3-backup-info.patch Edit (5.4 KiB, text/plain)

Rebased against 2.1.5.

Revision history for this message

Alexey Kopytov (akopytov) wrote on 2013-11-05:

#8

This has been implemented along with with https://blueprints.launchpad.net/percona-xtrabackup/+spec/history-on-the-server and will be available in XtraBackup 2.2.

Revision history for this message

Shahriyar Rzayev (rzayev-sehriyar) wrote on 2018-01-20:

#9

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

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Related blueprints

Store backup history on the server

Patches

Add patch

Remote bug watches

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