borgbackup is a very interesting backup tool with a lot of features. It is ready for “production” or I should expect some bad surprise?
Anyone use it for work purpose?
Thanks in advance.
Alessandro.
9 thoughts on - Borgbackup Question
I don’t know the answer to that, but to me that implies two questions:
1) Are there failure conditions that it doesn’t handle, especially with an interrupted backup, and 2) Does it perform poorly under any specific circumstances. If anyone has experience with those questions, or is familiar enough with the implementation to explain why those should not be an issue, I’d be interested in their input as well.
I use borgbackup for several laptops backing up to a local file server with SSHFS, and that’s been good so far.
We have around 50 linux clients with borg backups to two different backup server, provisioned with Ansible. A new host is in the backup in around 30 seconds :) One backup server is internal for DMZ and LAN and one is for external hosts. The internal backup server syncs its backup to the external server. Storage is made with ZFS summed up to 16 TB each server.
This runs nicely for around two years without interruption. We learned a bit her e and there about some side effects with borg cache in the beginning and invested some time in hardening and Ansible role.
Before we choosed borg restic was on the list. Looks good too. Do not now anymore why we decided for borg. Maybe the name :)
It’s been working for me, too, but I think that people who’ve seen the tool fail are better equipped to answer whether a tool is “production ready” than those who haven’t.
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 each time. The mailing list was helpful with this. borg prune must run on the machine where the backup is created.
9 thoughts on - Borgbackup Question
I don’t know the answer to that, but to me that implies two questions:
1) Are there failure conditions that it doesn’t handle, especially with an interrupted backup, and 2) Does it perform poorly under any specific circumstances. If anyone has experience with those questions, or is familiar enough with the implementation to explain why those should not be an issue, I’d be interested in their input as well.
I use borgbackup for several laptops backing up to a local file server with SSHFS, and that’s been good so far.
We have around 50 linux clients with borg backups to two different backup server, provisioned with Ansible. A new host is in the backup in around 30 seconds :) One backup server is internal for DMZ and LAN and one is for external hosts. The internal backup server syncs its backup to the external server. Storage is made with ZFS summed up to 16 TB each server.
This runs nicely for around two years without interruption. We learned a bit her e and there about some side effects with borg cache in the beginning and invested some time in hardening and Ansible role.
Before we choosed borg restic was on the list. Looks good too. Do not now anymore why we decided for borg. Maybe the name :)
We startet here https://borgbackup.readthedocs.io/en/stable/deployment/central-backup-server.html
Tobias
—
collect@shift.agency
It’s been working for me, too, but I think that people who’ve seen the tool fail are better equipped to answer whether a tool is “production ready” than those who haven’t.
Il 01/03/20 20:18, Tobias Kirchhofer ha scritto:
How do you secure the process?
Thanks in advance
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@host-name-of-backup-client
…
“`
—
collect@shift.agency
On more thing – the borg mailing list is responsive. I had a question. Answer arrived directly
https://www.borgbackup.org/support/free.html
—
collect@shift.agency
Il 02/03/20 13:18, Tobias Kirchhofer ha scritto:
Thanks in advance
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 each time. The mailing list was helpful with this. borg prune must run on the machine where the backup is created.
append-only is not involved in borg prune.
—
collect@shift.agency
Il 02/03/20 13:50, Tobias Kirchhofer ha scritto:
Thank you for your answer.