Amanda

Overview

Amanda is a self-hosted backup system that lets an administrator coordinate backups for multiple networked computers from one server.

Its combination of scheduling, media cataloging, multiple destinations, and security options makes it capable of managing a varied backup setup. The trade-off is operational: without a holding disk, backups go sequentially to tape, and community users must turn to mailing lists or forums for help.

Key features

Centralized scheduling

Amanda schedules full and incremental backups across hosts and adjusts the schedule to distribute work over the backup cycle. That central control can help administrators coordinate a network-wide routine rather than handling each machine independently.

Destinations and media management

Backups can be written to disk, tape drives or changers, and cloud storage. Bundled device drivers support DVD-RW, RAIT, and Amazon S3. Amanda catalogs files and their media locations, identifies tapes needed for recovery, and manages tapes to reduce the risk of overwriting the wrong one. This breadth suits environments with established tape or mixed-media workflows, though it also leaves administrators responsible for managing the storage setup.

Security and data handling

Secure server-client communication can use OpenSSH, archives can be encrypted with GPG or another encryption program, and Kerberos 5 is supported. Compression with compress, gzip, or a custom program can happen before or after network transfer, giving administrators options to manage transfer and archive size.

Application support

The Application API allows custom backup handling for applications such as relational databases and special file systems. That flexibility is useful when a lab needs to protect data beyond ordinary files, but it implies configuration work rather than a turnkey application-specific workflow.

Holding-disk requirement

Amanda works best with one or more large holding-disk partitions for buffering. Without one, backups run sequentially to the tape drive, a meaningful constraint for administrators who need a workable throughput plan. Its design is a better fit for setups that can allocate this disk capacity than for environments unable to reserve space for staging.

Pricing

Amanda Community Edition costs nothing. It is a free open-source project provided as-is, with no paid tier or subscription term in the stated plan. The project says free support is unavailable; users can seek help through mailing lists and forums, while formal or commercial support may be available from vendors. This price suits labs and testing setups able to rely on community channels, but organizations requiring an included support commitment should consider a supported product instead.

Platforms

Amanda provides a native Windows client, and its README says it backs up both 32-bit and 64-bit Windows machines. Linux and Mac OS X are among its tested client platforms, as are multiple Unix systems; the project says it should run on modern Unix systems meeting its requirements. The listed platforms are Linux, macOS, self-hosted, and Windows. This mix supports a heterogeneous network, though the project frames the community edition primarily as a Linux and Unix backup option.

Who it's for

Amanda suits administrators in labs and testing environments who want centralized control across networked hosts, need disk, tape, or cloud destinations, and can provide holding-disk partitions. Media cataloging and security choices are useful where tape handling and protected transfers matter. It is a weaker fit for users seeking a managed, low-configuration service or support included with the free edition.

Pros and cons

• Pro: One server coordinates full and incremental backups across multiple hosts, reducing the need to schedule each computer separately.
• Pro: Disk, tape, and cloud destinations, plus media-location cataloging, give administrators options for varied storage environments.
• Pro: OpenSSH, GPG-compatible encryption, and Kerberos 5 provide several security mechanisms.
• Con: Large holding-disk partitions are recommended; without them, backups proceed sequentially to tape.
• Con: The free edition is provided as-is and has no free support, so troubleshooting depends on community channels unless vendor support is arranged.

Alternatives

Bareos is worth comparing for readers looking for another open-source community backup option across Linux, macOS, web, and Windows platforms.

MSP360 Backup may suit someone seeking a free personal workstation option with file and image-based backup and forum support, or a paid Pro plan for macOS and Linux.

Storware Backup & Recovery is an option for readers who want a free license without technical support or a 60-day trial capped at 20 virtual environments.

Veeam Agent for Mac is a Mac-specific alternative with a free edition limited to one backup job and no direct backup to object storage.

Datto Endpoint Backup for Windows uses consumption-based pricing tied to storage used, so it may suit readers who prefer a paid, usage-based model.

UrBackup offers an open-source, self-hosted server with file and image backups for readers comparing another community option.

AvePoint Cloud Backup has custom pricing and may suit readers looking for a paid cloud backup product.

Proxmox Backup Server is another freemium option for Linux and web platforms; its Community plan is €560 a year for unlimited backup storage and clients.

Browse Backup and Disaster Recovery Software or Backup software for more options.

Verdict

Choose Amanda if you administer a Linux-, Unix-, and Windows-capable network in a lab or testing setting, can allocate holding-disk space, and value centralized scheduling with media tracking and security options. Its free open-source edition is the draw; its holding-disk demands and lack of free support are the reasons to choose another system when predictable support or simpler operations matter more.