AMANDA-COMMAND-FIL(5)
AMANDA-COMMAND-FIL(5) πΈ
okay bestie, welcome to amanda-command-file β that's the page we're on, from the Amanda manual, section 5 (file formats and conventions). Sit down, grab a strawberry π, we're gonna learn about the little text file that keeps receipts on all your outgoing dle commands. it's giving organized. it's giving bookkeeping queen. let's go π
β¨ NAME β¨
amanda-command-file β keeps the status of outgoing dle commands π«Ά
π DESCRIPTION π
So the command-file file holds the tea β on your outgoing dump commands. Like, all of these:
- dumps that need to be flushed from holding disk over to storage
- dumps that need to be copied (vaulted) from one storage to another
- dumps that have an outgoing restore request
The file is plain text, no cap. The first line is the version of the file. The second line is an id that increments every single time something new gets inserted into the file. growth mindset fr fr π
Every line after that starts with an id, and then one of these keywords:
FLUSHβ an entry that lists a holding file and a storage, and says where that file must be flushed to.COPYβ an entry that lists a dump from a storage and a storage to copy it to (vault).RESTOREβ an entry that lists a dump from a storage that has a restore request. Heads up: an entry gets automatically removed 24 hours after it's created. poof, gone, expired like my attention span π
π¨ Important, no skimming: Amanda never overwrites a volume if one of its dumps has a command in the command-file. That volume is taken, okay? respect the commitment π
π° FLUSH LINE π°
id FLUSH config holding-file hostname diskname dump-timestamp dump-level storage WORKING:pid STATUS.fi
Here's what every single field is doing at the party:
idβ the id of the command.FLUSHβ theFLUSHkeyword.configβ the config this command applies to.holding-fileβ the holding-file to flush.hostnameβ the hostname of the dump.disknameβ the diskname of the dump.dump-timestampβ the timestamp of the dump.dump-levelβ the level of the dump.storageβ the storage where the dump gets flushed to.WORKING:pidβ the pid of the process doing the flush, or0.STATUSβTODOorDONE.
π COPY LINE π
id COPY config src-storage src-pool src-label src-fileno src-labels-str start-time hostname diskname dump-timestamp dump-level dest-storage WORKING:pid STATUS.fi
Field-by-field, because we do not skip β:
idβ the id of the command.COPYβ theCOPYkeyword.configβ the config this command applies to.src-srorageβ the storage where the dump is found.src-poolβ the pool where the dump is found.src-labelβ the label of the first part of the dump.src-filenoβ the fileno of the first part of the dump.src-labels-strβ the list of all source labels required.start-timeβ when to start the copy.hostnameβ the hostname of the dump.disknameβ the diskname of the dump.dump-timestampβ the timestamp of the dump.dump-levelβ the level of the dump.dest-storageβ the storage where the dump gets copied to.WORKING:pidβ the pid of the process doing the copy, or0.STATUSβTODOorDONE.
π¦ RESTORE LINE π¦
Two flavours, bestie, pick your fighter.
To restore from a storage:
id RESTORE config src-storage src-pool src-label src-fileno expire hostname diskname dump-timestamp dump-level WORKING:pid STATUS.fi
Or, to restore from a holding file:
id RESTORE config HOLDING HOLDING holding-file 0 expire hostname diskname dump-timestamp dump-level WORKING:pid STATUS.fi
And the fields, all of them, every last one:
idβ the id of the command.RESTOREβ theRESTOREkeyword.configβ the config this command applies to.src-srorageβ the storage where the dump is found.src-poolβ the pool where the dump is found.src-labelβ the label of the first part of the dump.HOLDINGβ theHOLDINGkeyword.holding-fileβ the full path of the holding file.src-filenoβ the fileno of the first part of the dump.expireβ when this command expires and can be automatically removed from the file.src-labels-strβ the list of all source labels required.start-timeβ when to start the copy.hostnameβ the hostname of the dump.disknameβ the diskname of the dump.dump-timestampβ the timestamp of the dump.dump-levelβ the level of the dump.WORKING:pidβ the pid of the process doing the copy, or0.STATUSβTODOorDONE.
π SEE ALSO π
The Amanda Wiki: : http://wiki.zmanda.com/ β¨
π AUTHOR π
Jean-Louis Martineau <martineau@zmanda.com> Zmanda, Inc. (http://www.zmanda.com)
okay that's the whole thing, you ate it, no crumbs left π½οΈπ
this was Amanda 3.5.4, dated 08/26/2026, and yes the page is literally called AMANDA-COMMAND-FIL(5) β go forth and never overwrite a volume that has a command pending, mwah ππ
π¦ where this page comes from
- ubuntu stonking: amanda-common 1:3.5.4-2.1ubuntu1 Β· Custom
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms