search for: aaaac3nzac1

...ent/central-backup-server.html >> >> Tobias >> > Hi Tobias, > > How do you secure the process? Plain ssh: authorized_keys on the backup server: ``` ? command="borg serve --restrict-to-path /borgbackup/vm/host-name-of-backup-client --append-only" ssh-ed25519 AAAAC3NzaC1? root at host-name-of-backup-client ? ``` -- collect at shift.agency

...gt; How do you secure the process? >> >> Plain ssh: >> >> authorized_keys on the backup server: >> >> ``` >> ? >> command="borg serve --restrict-to-path >> /borgbackup/vm/host-name-of-backup-client --append-only" ssh-ed25519 >> AAAAC3NzaC1? root at host-name-of-backup-client >> ? >> ``` >> > Ok thank you but how do you run prune command if append-only is > enabled? Prune is startet on the client after each backup. Before we did it on the backup server at once. But borg recreated the whole index per repo ea...

...;> >> Hi Tobias, >> >> How do you secure the process? > > Plain ssh: > > authorized_keys on the backup server: > > ``` > ? > command="borg serve --restrict-to-path > /borgbackup/vm/host-name-of-backup-client --append-only" ssh-ed25519 > AAAAC3NzaC1? root at host-name-of-backup-client > ? > ``` > Ok thank you but how do you run prune command if append-only is enabled? Thanks in advance

On 1 Mar 2020, at 20:00, Gordon Messmer wrote: > On 3/1/20 12:40 AM, Alessandro Baggi wrote: >> borgbackup is a very interesting backup tool with a lot of features. >> It is ready for "production" or I should expect some bad surprise? > > > I don't know the answer to that, but to me that implies two questions: > 1) Are there failure conditions that it