We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
borgbackup emits as few information as possible to the remote end (borg-hive in this case). Discussion to this is here: borgbackup/borg#5173
Alternativ idea to log or provide more information to borg-hive is a client side hook. borgmatic provides a hook system, which could be extended for borg-hive. https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/
this opens the possibility to store the borgmatic output in borg-hive or parse the repository information from it:
A server-side way would be more flexible and would avoid specific implementations for clients.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
borgbackup emits as few information as possible to the remote end (borg-hive in this case).
Discussion to this is here: borgbackup/borg#5173
Alternativ idea to log or provide more information to borg-hive is a client side hook. borgmatic provides a hook system, which could be extended for borg-hive.
https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/
this opens the possibility to store the borgmatic output in borg-hive or parse the repository information from it:
A server-side way would be more flexible and would avoid specific implementations for clients.
The text was updated successfully, but these errors were encountered: