Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are differences to jmfederico / run-xtrabackup.sh? #5

Open
cmonty14 opened this issue Jul 20, 2020 · 4 comments
Open

What are differences to jmfederico / run-xtrabackup.sh? #5

cmonty14 opened this issue Jul 20, 2020 · 4 comments

Comments

@cmonty14
Copy link

Hi,
you forked this backup script from jmfederico / run-xtrabackup.sh.

Question:
Is your script function wise identical to the original script?

THX

@omegazeng
Copy link
Owner

basically the same.
I want to find an easy way to backup databases then I get jmfederico/run-xtrabackup.sh.

mariabackup is a little different from xtrabackup. at first, I change the script for self-use.
Just add some documents and put it on Github.

THX

@mhaamann
Copy link

One big difference is the checks on line 105

Just learned by coincidence that this script does not exit with an error if the mariabackup cli fails, so be carefull with running this via cron unattended. Didn't loose any data but spotted this in a routine checkup of our cron jobs.

@cantoute
Copy link

cantoute commented Mar 19, 2021 via email

@omegazeng
Copy link
Owner

omegazeng commented Jul 28, 2021

Thanks for sharing this. To be honest I have given up using this script because it freezes the db during backups even for read access. Finally mysqldump seems more reliable and don't lock tables on read. Takes a bit more disk space, but reliable is what we want. Le 19 mars 2021 11:11:56 GMT-04:00, Matthias Haamann @.> a écrit :

One big difference is the checks on line 105 Just learned by coincidence that this script does not exit with an error if the mariabackup cli fails, so be carefull with running this via cron unattended. Didn't loose any data but spotted this in a routine checkup of our cron jobs. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #5 (comment)
-- Antony Gibbs @.
+591.7227.5988 +33 (0)9 72 11 71 25 +598 (0)9 9360 744

make sure you are using InnoDB table.

https://www.percona.com/doc/percona-xtrabackup/LATEST/how_xtrabackup_works.html
Locking is only done for MyISAM and other non-InnoDB tables after Percona XtraBackup finishes backing up all InnoDB/XtraDB data and logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants