AMOVERVIEW(8)

✨ AMOVERVIEW(8) ✨

okay bestie, buckle up πŸ’– this is amoverview from section 8 of the manual (System Administration Commands, iykyk) β€” she shows you all the file systems Amanda has been chomping on over time. no cap.


πŸŽ€ NAME πŸŽ€

amoverview β€” display file systems processed by Amanda over time. literally that's her whole job πŸ’…


🌸 SYNOPSIS 🌸

amoverview [--hostwidth width] [--diskwidth width] [--skipmissed]
           [--last] [--num0] [--togo0] [--verbose] [--config ] config

πŸ¦‹ DESCRIPTION πŸ¦‹

So amoverview puts up a whole chart for you β€” hosts and file systems that Amanda processed, plus which backup level got performed each and every day. it's giving receipts πŸ“Š

If you want the full Amanda lore, go read the amanda(8) man page, bestie. that's where the details live.


πŸ’– OPTIONS πŸ’–

  • --config config β€” use configuration config. that's the one, periodt.
  • --hostwidth width β€” sets the host field column width to width characters instead of the default 8.
  • --diskwidth width β€” sets the disk field column width to width characters instead of the default 20.
  • --skipmissed β€” compacts the output by only printing stats for the days Amanda actually ran. no ghost days, no empty air 🫢
  • --last β€” outputs the last status of each disk at the start. obsessed with this one if you've got long tapecycles and/or sparse reports ✨
  • --num0 β€” outputs the number of level 0 dumps for each disk.
  • --togo0 β€” outputs the number of runs until the last level 0 dump gets overwritten. the countdown vibes ⏳
  • --verbose β€” amoverview can take a long while on large systems, ngl. this option reports intermediate steps while it's working so you're not just staring at a blank terminal wondering if it ghosted you.

πŸ‘‘ RESULTS πŸ‘‘

amoverview is basically a summary of the output of amadmin <config> find. whenever the last column of amadmin find contains anything other than "OK", amoverview translates that into an "E" for that day.

A number means the level of backup and it succeeded. An "E" means an error for that day. And you get an "E" for all the errors β€” failed to connect, datatimeout, computer crashed, etc. β€” but also for failing to write to tape. yeah. all of them. 😭

You can also have an "E" followed by a number, which happens if a filesystem ran into end-of-tape once (that gives you an "E"), and then later that same day you flush it to a second tape (that gives you a number: the level, indicating success). And if the flush failed too? you get a double "EE" for that day. πŸ’€

You can also get a double code if you've got two tapes in the changer and Amanda failed to write to tape the first time because it hit end of tape (resulting in "E0" for a full, "E1" for an incremental, etc.) or twice with error ("EE"), and maybe a successful flush afterwards giving maybe "EE0". (Only the latest 2 characters are printed, just so you know.)


🌈 EXAMPLE 🌈

This one shows the /home file system on host2 was backed up at level 3 on the 8th, 9th and 10th of December, had a full backup on the 11th, a level 1 on the 12th and a level 2 on the 13th. iconic behavior honestly πŸŽ€

# amoverview
                         date 12 12 12 12 12 12
host     disk                 08 09 10 11 12 13

host1    /                     0  1  1  1  1  1
host1    /var                  0  1  1  1  1  1
host2    /                     1  1  1  1  1  0
host2    /home                 3  3  3  0  1  2
host2    /opt                  1  1  1  1  1  1
host2    /var                  1  1  0  1  1  1

🧚 SEE ALSO 🧚

amanda(8), amadmin(8)

The Amanda Wiki: : http://wiki.zmanda.com/


πŸ’œ AUTHOR πŸ’œ

Stefan G. Weichinger <sgw@amanda.org> β€” king behavior, we thank him for his service πŸ™


okay that's the whole page, bestie πŸ’… Amanda 3.5.4, dated 08/26/2026 β€” go forth and overview your file systems, you absolute main character πŸ¦‹βœ¨
πŸ“¦ where this page comes from