"Galera Cluster backups can be performed just as regular MySQL backups, using a backup script. Since all the cluster nodes are identical, backing up one node backs up the entire cluster.
However, such backups will have no global transaction IDs associated with them. You can use these backups to recover data, but they cannot be used to recover a Galera Cluster node to a well-defined state. Furthermore, the backup procedure may block the cluster operation for the duration of backup, in the case of a blocking backup."
However
Blocking cluster operation can be avoided with wsrep_desync option which is present in resent versions of Galera Cluster
In case of rsync backup Global Transaction ID can be recovered from backed up InnoDB tablespace
Xtrabackup should have option to record GTID consistently
This section should be expanded to cover ways to take backups without the aid of garbd.
Issue by temeo Tuesday May 06, 2014 at 14:31 GMT Originally opened as https://github.com/codership/galera/issues/13
The page says:
"Galera Cluster backups can be performed just as regular MySQL backups, using a backup script. Since all the cluster nodes are identical, backing up one node backs up the entire cluster.
However, such backups will have no global transaction IDs associated with them. You can use these backups to recover data, but they cannot be used to recover a Galera Cluster node to a well-defined state. Furthermore, the backup procedure may block the cluster operation for the duration of backup, in the case of a blocking backup."
However
wsrep_desync
option which is present in resent versions of Galera ClusterThis section should be expanded to cover ways to take backups without the aid of garbd.