Slave backup(with InnoBackupEx) procedure requires additional options

Bug #1358450 reported by Denis M.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Opinion
Wishlist
Unassigned

Bug Description

Once base replication patchset lands, we would need to improve backuping procedure for InnoBackupEx strategy(see [1]).

We need to add additional attributes, such as:

 --slave-info option, for more info see [2].

 --safe-slave-backup option, for more info see [2].

Another thing we might take into account, see [3].

[1] Command that's being executed against generic Trove instance with mysql datastore:
see https://github.com/openstack/trove/blob/master/trove/guestagent/strategies/backup/mysql_impl.py

[2] xtrabackup CLI parameters:
see http://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/replication_ibk.html

[3] Advanced replication setup with xtrabackup
see http://www.percona.com/doc/percona-xtrabackup/2.1/howtos/setting_up_replication.html#replication-howto

Changed in trove:
importance: Undecided → Low
importance: Low → Wishlist
status: New → Triaged
Amrith Kumar (amrith)
Changed in trove:
status: Triaged → Opinion
milestone: ongoing → none
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.