Slave backup(with InnoBackupEx) procedure requires additional options
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-
Another thing we might take into account, see [3].
[1] Command that's being executed against generic Trove instance with mysql datastore:
see https:/
[2] xtrabackup CLI parameters:
see http://
[3] Advanced replication setup with xtrabackup
see http://
Changed in trove: | |
importance: | Undecided → Low |
importance: | Low → Wishlist |
status: | New → Triaged |
Changed in trove: | |
status: | Triaged → Opinion |
milestone: | ongoing → none |