Amanda

Overview

Amanda is a free, open-source system for coordinating backups across networked computers from one administrator-managed server. It is best suited to Linux and Unix labs or test environments that can manage their own storage and support; its breadth is useful, but deployment depends on planning for a holding disk.

Key features

Central scheduling and media cataloging

Amanda schedules full and incremental backups across multiple hosts and spreads work across the backup cycle. That makes it a fit for administrators who want one coordinated routine rather than separate backup schedules on every machine. Its catalog records files and their media locations, identifies tapes needed for restores, and manages tapes to avoid overwriting the wrong one—practical safeguards for tape-based recovery.

Storage, security, and data handling

Backups can go to disk, tape drives or changers, and cloud storage. Bundled drivers support DVD-RW, RAIT, and Amazon S3, giving administrators options across established media and cloud storage. The trade-off is that teams must manage the underlying destination setup themselves.

Server-client communication can be secured with OpenSSH, archives can be encrypted with GPG or another encryption program, and Kerberos 5 is supported. Archives can be compressed before or after network transfer using compress, gzip, or a custom program. These choices suit administrators who need control over security and transfer handling, but they also require decisions about the tools and configuration to use.

Application and Windows support

The Application API allows custom backup handling for relational databases and special file systems, making Amanda more adaptable than a fixed file-only routine where application-aware work is needed. It also provides a native Windows client, and the project README says it backs up both 32-bit and 64-bit Windows machines. The project lists Linux, Mac OS X, and multiple Unix systems among tested client platforms and says Amanda should run on modern Unix systems that meet its requirements.

Operational constraint and support

Amanda works best with one or more large holding-disk partitions to buffer backups. Without a holding disk, backups run sequentially to the tape drive, which can make that setup a poor fit for environments expecting buffered throughput. Free support is unavailable; community users can turn to mailing lists and forums, while formal or commercial support may be available through vendors. Zmanda maintains the Community Edition, which continues to receive critical security updates, but the project provides it as-is.

Pricing

Amanda Community Edition: free. It is a free, open-source project provided as-is, with no paid tier or support entitlement described. That makes it suitable for labs and testing where administrators can handle deployment and troubleshooting; teams that require dependable formal support should consider a commercially supported option instead.

Platforms

Amanda is available for Linux, macOS, Windows, and self-hosted use. Its central-server model is intended to back up multiple networked hosts, with a native Windows client and tested client platforms including Linux, Mac OS X, and multiple Unix systems.

Who it's for

Amanda makes most sense for technically capable administrators in labs or test environments who need centralized scheduling, media tracking, and flexibility across disk, tape, and cloud destinations. Its application API and security options add value where backup workflows need customization. It is less suitable for teams that cannot provide holding-disk capacity, want support included, or need a managed service rather than an as-is project.

Pros and cons

• Centralized multi-host scheduling: full and incremental backups can be coordinated and spread over the cycle from one server.
• Broad media options with cataloging: disk, tape, and cloud targets pair with file and tape-location tracking that helps plan restores and protect tapes from accidental overwrite.
• Configurable protection and handling: OpenSSH, GPG-compatible encryption, Kerberos 5, and selectable compression tools let administrators shape security and transfer behavior.
• Requires storage planning: the system works best with large holding-disk partitions; without them, work proceeds sequentially to tape.
• As-is community support: free support is unavailable, leaving users to mailing lists and forums unless they obtain vendor support.

Alternatives

MSP360 Backup is worth considering for personal workstation backups if file- and image-based backup and forum support in its free plan matter more than Amanda's centralized network-host model.

Bareos is another open-source community-edition option if public repository access and complete source code are priorities.

Storware Backup & Recovery may suit users seeking a free license or a 60-day trial, with its free license excluding technical support.

Veeam Agent for Mac is a narrower choice for Mac users who need one backup job and do not need direct backup to object storage in the free edition.

Acronis Cyber Disaster Recovery Cloud is an option for readers considering a paid disaster-recovery service with a free trial.

Datto Endpoint Backup for Windows suits readers who prefer consumption-based, storage-use pricing and are prepared to request a quote.

AvePoint Cloud Backup is another paid option for readers prepared to seek custom pricing.

UrBackup is an open-source, self-hosted alternative for readers specifically seeking file and image backups.

Verdict

Choose Amanda if you administer a Linux- or Unix-oriented lab or test environment and want centralized control over multi-host backups, especially across tape and other mixed storage. Its media catalog, scheduling, and configurable security make it capable, but the holding-disk requirement and as-is support model are substantial operational costs.