amadmin

amadmin config subcommand [options...] [arguments...]

The config argument refers to the name of the Amanda configuration to operate on.

status
    Displays the overall status of the specified Amanda configuration, including the last run, pending DLEs, and tape status.

daily [options...]
    Initiates a full Amanda daily backup run for the specified configuration. This subcommand is typically invoked by cron.

find [options...] host [disk...]
    Locates specific backups in the Amanda index, allowing administrators to find where a particular DLE's backup resides.

force [options...] host [disk...]
    Marks one or more DLEs to receive a full backup during the next scheduled run, regardless of their normal backup level.

unforce [options...] host [disk...]
    Removes the 'forced full backup' status from specified DLEs.

label label [options...]
    Labels a tape or other backup media for use by Amanda.

tape [options...]
    Provides various operations related to tape media, such as listing tapes in the changer, or showing the contents of a tape.

estimate [options...] host [disk...]
    Performs an estimate of the size of the data that would be backed up for the specified DLEs.

vault [options...] vault-set
    Manages vaulting operations, allowing for copying backups from the main storage to a vaulting set for offsite storage.

version
    Displays the version of the Amanda client and server software.

The amadmin command is the primary command-line utility for administering an Amanda (Advanced Maryland Automatic Network Disk Archiver) backup system. It allows administrators to interact with Amanda's daily operations, view status, trigger manual actions, and manage backup media (tapes/disks).

Its functions include checking the status of backup runs, forcing or unforcing backups of specific DLEs (Disk List Entries), finding specific backups in the index, managing tape labels and media, and performing maintenance tasks. It operates on a specific Amanda "configuration," which groups together DLEs, tape devices, and other settings.

Using amadmin requires a correctly installed and configured Amanda backup system. The user executing the command must have appropriate permissions (typically the `amanda` user or root with `sudo`). A solid understanding of Amanda concepts like configurations, DLEs, and storage strategies is crucial for effective and safe use, as incorrect commands can lead to backup failures or difficulties in restoring data.

Every amadmin command requires a config parameter. This name corresponds to a specific Amanda configuration directory (e.g., `/etc/amanda/config`). This design allows a single Amanda installation to manage multiple independent backup sets, each with its own policies, Disk List Entries (DLEs), and storage targets. Choosing the correct configuration name is paramount for all amadmin operations to ensure commands are applied to the intended backup environment.

Amanda was originally developed at the University of Maryland in the late 1980s and early 1990s as a robust, open-source network backup solution for Unix-like systems. amadmin has been a fundamental administrative utility since Amanda's inception, providing the primary command-line interface for managing backup operations, configurations, and media within its client-server architecture. Its continuous development reflects the evolving needs for enterprise-grade backup management.

amanda(8), amdump(8), amcheck(8), amgetconf(8), amtape(8), amrestore(8)