[...]including a hard-coded host-specific retention prefix.
Yes, but I need two of those prefixes when I change the naming scheme for archives for one and the same host.
I do wonder though: Why not prune all hosts at the same time with a single borgmatic/Borg invocation? In other words, why do you need to only prune the archives for a particular host instead of…
borgmatic runs borg serve on the central backup server and (remotely via SSH) runs borg create on a machine to be backed up
Almost, it's important that I have 3 hosts: The ones to be backed…
generate-borgmatic-config override existing files.
borg debug supported as arbitrary borg command?
nohup ssh -F ${PATH_LOCAL_SSH_CFG} -f -n ${HOST_OTHER} ${cmd} < '/dev/null' > "${PATH_LOCAL_MNT2}/${db_name}" 2> '/dev/null' &
The above is wrong, if one wants to really have…
Made some progress.... The following are the running process when the backup software doesn't move forward. All of the bash processes at the bottom contain my started SSH instances most likely,…
And when you run borgmatic, it hangs on that before_backup step for five seconds while it's waiting for that command's output. But if you change it to this ...
Waiting on the started hook…
Hmm.. I'm not following why that's the case. borgmatic's database dumping support can be used with either a local or remote database server. So in theory, you could expose the VM database on a…
Trying to ask some other people with more knowldge of Python than me as well... :-)
I've updated BGM to 1.5.24 and still see the same behaviour. I have the feeling theat either Python provides too many processes to BGM or BGM already knows about all those children and wrongly…
What I observe seems to really be some Python specific behaviour, others have it as well:
--max-duration for checks supported by YAML already?