@witten Thanks for the pointers. Especially the latter sounds like a nice and easy workaround.
It's possible Borg only prints the name of a file after it's done being backed up. In which case the actual file causing the hang might be another file that's not listed. You could try `sudo…
It's possible Borg only prints the name of a file after it's done being backed up. In which case the actual file causing the hang might be another file that's not listed. You could try `sudo…
Ok, this is still very strange. I can reliably solve the issue when I remove all the database hooks from the config.yaml even though the issue seems to be elsewhere.
@witten Can you come up…
Thanks for reporting this. A little context: borgmatic streams database backups to Borg via a named pipe. Specifically, that
postgresfile (notice the "p" at the start of the line), so it…
I had a look at the code to see how the two things (using optional identifier for database configs and check environment for db user/password) could be implemented. It doesn't look too complicated…
I'm curious how you have this working! Here's a quote from the borgmatic database docs under limitations: "borgmatic does not currently support backing up or restoring multiple databases that share…
Or maybe letting borgmatic check for the env variables MYSQL_PWD_ and MYSQL_USER_ automatically would be a solution?
On second thought, the name of the db is not unique and…
Or maybe letting borgmatic check for the env variables MYSQL_PWD_<dbname> and MYSQL_USER_<dbname> automatically would be a solution?
I'd like to do the exact same thing as described above: reuse the exising database credentials in the environment and pass them to borgmatic. Though in my case I would need to support multiple…