I am using btrbk 0.32.5 on a server and 0.27.1 on a client and noticed that the validation of mbuffer on the server end is too strict.
Particularly, ssh_filter_btrbk enforces a verbosity level of mbuffer of 1, however, the client uses mbuffer without increased verbosity level. Thus, the client was rejected.
By making the parameter -v 1 in mbuffer_match in ssh_filter_btrbk.sh optional, the command is accepted:
I am using btrbk 0.32.5 on a server and 0.27.1 on a client and noticed that the validation of mbuffer on the server end is too strict.
Particularly, ssh_filter_btrbk enforces a verbosity level of mbuffer of 1, however, the client uses mbuffer without increased verbosity level. Thus, the client was rejected.
By making the parameter
-v 1inmbuffer_matchin ssh_filter_btrbk.sh optional, the command is accepted: