witten reopened issue witten/borgmatic#316

14 hours ago

witten commented on issue witten/borgmatic#316

Ugh! Can I see the `borg create` invocation from the verbose output to make sure that the source directiories are getting de-duplicated correctly? Also, can you try `rm -fr /root/.borgmatic`, and then running borgmatic again to see if that makes the hang go away? If it does, then there's probably a stale named pipe sitting around. (Which would indicate borgmatic needs to do further cleanup before running `borg create`.)

14 hours ago

witten commented on issue witten/borgmatic#320

That's a great idea.. I've thought of something similiar with some of the existing hooks. For simplicity's sake, I could see just unconditionally passing in the repository path as the first parameter to the script (no `%h` needed). And then it's up to the script to do whatever it wants with that.

1 day ago

witten commented on issue witten/borgmatic#320

Okay, thanks!

1 day ago

witten commented on issue witten/borgmatic#320

Thank you for filing this ticket, and for the kind words! I could see adding a hook called `before_repo` or `before_repository`. Question though: Would it make sense to run regardless of actions specified (`create`, `prune`, `check`, etc.)? I imagine that for any action that needs to interact with the remote repository, you'd need the port knocking script to run first...?

1 day ago

witten commented on issue witten/borgmatic#319

Released in borgmatic 1.5.5!

3 days ago

witten commented on issue witten/borgmatic#316

Released in borgmatic 1.5.5!

3 days ago

witten commented on issue witten/borgmatic#315

Okay, the "fix" of forcing `one_file_system` is released with borgmatic 1.5.5!

3 days ago

witten commented on issue witten/borgmatic#314

Released in borgmatic 1.5.5!

3 days ago

witten pushed tag 1.5.5 to witten/borgmatic

3 days ago

witten commented on issue witten/borgmatic#306

Sorry for the delay here. A couple of different ideas: * Add a separate MySQL `list_options` configuration option to support passing additional options to the `mysql` command used for listing databases. That would allow you to manually specify `--defaults-file=whatever` for both `options` and `list_options`. * Or, add a MySQL `defaults_file` option to the configuration, so you can just set a value other than `.my.cnf`, and borgmatic will take care of passing it to both `mysql` and `mysqldump`. Have you confirmed that manually passing `--defaults-file=...` to `mysql` or `mysqldump` gets the desired behavior on your system?

3 days ago

witten closed issue witten/borgmatic#315

3 days ago

witten closed issue witten/borgmatic#319

3 days ago

witten commented on issue witten/borgmatic#319

A descriptive error makes sense to me!

6 days ago

witten commented on issue witten/borgmatic#319

Thanks so much for reporting this one. It definitely seems like the current behavior of issuing a `mysqldump` command with invalid parameters is not the right thing to do! The one problem I can envision if borgmatic doesn't error when there are no "all" databases to backup: A user may see backups succeeding and assume that everything is working, when in fact nothing is being backed up.. because there are no user databases on the system. Thoughts on that? In your particular case, I'm curious.. Why do you have the MySQL database hook enabled if no user databases are present? Are you planning to add databases later on?

6 days ago

witten closed issue witten/borgmatic#317

6 days ago

witten commented on issue witten/borgmatic#317

Glad to hear it's working!

6 days ago