You can now configure globally whether or not to automatically cleanup failed backups. Previously, XBM would always cleanup after itself on a failure.
I am finding that when things fail, that I would like a chance to investigate and troubleshoot why and perhaps open an XtraBackup bug or try some experimentation to see what might get around the problem.
I have been finding it particularly frustrating when waiting 9 hours for a multi-terabyte system to backup and then have some failure occur right at the end -- with the previous auto-cleanup I was left with nothing to troubleshoot with! Now I can turn off the cleanup and have a chance to do some forensics myself.
At the moment this is a quick and dirty feature -- it is only configurable at the global level, not per backup host.
The option is cleanup_on_failure and is found in
The other feature that I added was the ability to configure how much memory XtraBackup Manager will tell XtraBackup to use when applying logs or merging incremental snapshots onto a full backup.
The default being used so far is 1G - so be careful about how much memory you have and consider how many possible concurrent backups you have configured.
This option is xtrabackup_use_memory and is also found in the config.php file as well as being a global feature only, not configurable per host.
These are not big features by any means, but they are certainly helpful for me and hopefully for others in the future.
That's it for today!
Lachlan
No comments:
Post a Comment