Linux command
amdump 命令
文本
复制后可按需替换文件名、目录或参数。
常用示例
Run a full backup
amdump [config_name]
Back up specific hosts
amdump [config_name] [host1] [host2]
Back up a specific disk
amdump [config_name] [hostname] [/path/to/disk]
Run backup to holding disk only
amdump --no-taper [config_name]
Override a configuration option
amdump -o [runtapes=2] [config_name]
Use exact host/disk matching
amdump --exact-match [config_name] [hostname] [diskname]
说明
amdump is the main command for running Amanda backups. It loads the specified configuration and backs up every disk listed in the disklist file, or a subset if specific hosts and disks are provided on the command line. The command is typically executed via cron for scheduled nightly backups. It coordinates the entire backup process: contacting client hosts, transferring data to holding disk, and writing to tape or other storage media. Amanda's scheduling algorithm determines which filesystems receive full versus incremental backups based on the configured dump cycle. If a file named hold exists in the configuration directory, amdump waits until it is removed before starting, checking every minute. This allows administrators to delay scheduled backups when the tape device is in use elsewhere. When problems occur, amdump may enter "degraded mode" where backups continue to holding disk but tape writing is skipped. The --no-taper option forces this mode intentionally.
参数
- --no-taper
- Dump to holding disk only without writing to tape; enters degraded mode immediately
- --exact-match
- Parse host and disk arguments as exact values rather than expressions
- -o _name=value_
- Override a configuration option from amanda.conf
FAQ
What is the amdump command used for?
amdump is the main command for running Amanda backups. It loads the specified configuration and backs up every disk listed in the disklist file, or a subset if specific hosts and disks are provided on the command line. The command is typically executed via cron for scheduled nightly backups. It coordinates the entire backup process: contacting client hosts, transferring data to holding disk, and writing to tape or other storage media. Amanda's scheduling algorithm determines which filesystems receive full versus incremental backups based on the configured dump cycle. If a file named hold exists in the configuration directory, amdump waits until it is removed before starting, checking every minute. This allows administrators to delay scheduled backups when the tape device is in use elsewhere. When problems occur, amdump may enter "degraded mode" where backups continue to holding disk but tape writing is skipped. The --no-taper option forces this mode intentionally.
How do I run a basic amdump example?
Run `amdump [config_name]` in a terminal, then adjust file names, paths, flags, or remote targets for your system.
What does --no-taper do in amdump?
Dump to holding disk only without writing to tape; enters degraded mode immediately