Amanda: Network-Wide Backup Management for Admins Who Want Centralized Control Without Vendor Lock-In
What Is It?
Amanda (Advanced Maryland Automatic Network Disk Archiver) is an open-source backup solution built for managing backups across many systems — from a single Linux server. It’s not a point-and-click desktop app. It’s infrastructure-level software designed to handle multiple hosts, support tape and disk targets, and operate on a strict schedule with predictable results.
Amanda can back up Linux, Unix, Windows, and macOS systems using native agents or the Zmanda Windows Client. It writes to local disk, network shares, or tape libraries, and it’s particularly useful in environments where data integrity, auditability, and retention policies actually matter.
This is a tool for admins — not end users.
Capabilities
| Feature | Description |
| Central Backup Server | One Amanda server controls backups across dozens or hundreds of clients |
| Tape, Disk, or Cloud Targets | Supports physical tapes, disk arrays, or cloud storage (with add-ons) |
| Open Formats | Uses standard tar and dump for archives — no proprietary lock-in |
| Scheduling Engine | Custom backup windows, levels (full/incremental), and quotas |
| Encryption Support | Supports OpenSSL-based encryption on the client side |
| Multi-Platform Agents | Works with Linux, Windows (via Zmanda client), BSD, Solaris, etc. |
| Restore Granularity | Supports file-level or full volume restores |
Deployment Notes
– Linux-only server: Amanda needs a Linux host for coordination and storage.
– Requires planning: Setup involves defining clients, schedules, holding disks, and retention policies in conf files.
– Network-centric: All communication is over TCP/UDP; firewall rules must be considered.
– Not cloud-native: Can be adapted, but designed for on-prem backup environments.
– Works well with tapes: One of the few still actively supporting tape libraries.
Installation Guide (on Debian/Ubuntu)
1. Install Server Components
sudo apt update
sudo apt install amanda-server amanda-client
2. Configure Backup Sets
– Edit /etc/amanda/DailySet1/amanda.conf, disklist, and tapelist.
3. Set Up Clients
– On each host, install amanda-client, configure .amandahosts.
4. Run Initial Backup
amdump DailySet1
5. Restore Files
amrecover DailySet1
6. Monitor via Logs
– Check /var/log/amanda for job status, errors, and performance stats.
Usage Scenarios
– Backing up a fleet of Linux/Unix servers on a fixed backup window with tape rotation.
– Managing long-term backups of application servers with strict retention policies.
– Centralizing backup jobs across departments from a single control point.
– Using open formats to ensure future compatibility and restore access.
– Running backups over LAN without relying on proprietary formats or vendor portals.