Allow backup history to be stored on a server different then the current one

Bug #1595431 reported by Ovais Tariq
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.3
Triaged
Wishlist
Unassigned
2.4
Triaged
Wishlist
Unassigned

Bug Description

Backup history is currently stored on the same server as the one doing the backup. It would be nice if xtrabackup would accept DSN so that the server where backup history is written can be changed. It would be specially useful in the cases where GTID replication is being used, and backup is taken on a slave and we want to write the backup history information to the master.

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

This is a reasonable request.

Revision history for this message
Ovais Tariq (ovais-tariq) wrote :

Is this something that can be looked at. This again prevents the use of the backup history feature, because if I do backups from the slave I would not want to write to slave for obvious operational reasons:
- slaves are read-only
- i don't want to have errant GTIDs
etc

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

Ovais,

This feature request is having low priority at the moment.

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-1024

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.