Open luxagen opened 11 months ago
After being mightily confused by the intermittency of this problem, I now understand what's going on.
Despite being invoked in snapshot
mode, btrbk
was using SSH as part of its logic for implementing the expiry policies, perhaps because it's trying to avoid eliminating the last common parent.
My solution/workaround is to use the -p
option to explicitly disable expiry logic when doing pure snapshotting.
If the author is satisfied that no further action is needed on this, I'm happy for it to be closed.
Sorry if this is a duplicate - I tried to search but didn't see anything obvious.
When I run
btrbk snapshot
, it tries to connect to SSH targets, but my key has a passphrase because I want to automate snapshot creation, NOT resume.I can't think of a valid reason for this behaviour. Surely snapshotting should be entirely local?