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 β€” the FLUSH keyword.
  • 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, or 0.
  • STATUS β€” TODO or DONE.

πŸŽ€ 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 β€” the COPY keyword.
  • 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, or 0.
  • STATUS β€” TODO or DONE.

πŸ¦‹ 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 β€” the RESTORE keyword.
  • 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 β€” the HOLDING keyword.
  • 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, or 0.
  • STATUS β€” TODO or DONE.

πŸ‘€ 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