I didn't vote because none is best -- rather it is a question of "horses for courses", that is which best meets the requirements.
We used to use amanda, rdiff-backup and rsync. I personally use Bacula, rsync and SpiderOak (a cloud backup service).
We have now almost completed migrating away from amanda and rdiff-backup to rsync run by a script which adds retention. The motivation is that neither amanda nor rdiff-backup are robust when they are interrupted while they are running; that is a problem because some of our clients shut down their systems while backups are running and our Internet connections are not reliable.
Comparing the tools I know:
- amanda
- Compresssed backup files: yes
- Ease of configuration: yes
- Graphical interface: no
- Network loading: not known
- Point in time restore: yes
- Poor cousin to the commercial edition: yes
- Retention: yes
- Robust when interrupted: no
- bacula
- Compresssed backup files: yes
- Ease of configuration: no
- Graphical interface: yes
- Point in time restore: yes
- Network loading: not known
- Poor cousin to the commercial edition: no
- Retention: yes
- Robust when interrupted: not known
- rdiff-backup
- Compresssed backup files: no
- Ease of configuration: yes
- Graphical interface: no
- Network loading: minimal
- Point in time restore: yes
- Poor cousin to the commercial edition: not applicable
[*[Retention: yes
- Robust when interrupted: no
- rsync
- Compresssed backup files: no
- Ease of configuration: yes
- Graphical interface: no
- Network loading: minimal
- Point in time restore: no
- Poor cousin to the commercial edition: not applicable
- Retention: no
- Robust when interrupted: yes
Amanda's error handling seems less robust than bacula's and, being written in perl rather than compiled, it is at the mercy of changes in the perl interpreter. The last point is not academic; on ubuntu 12.04 a recent perl upgrade which includes stricter syntax checking has broken amanda.