BACKUP_LISTDUMPS(8)

📦
version 1.8.16.1 · 10 versions
, in ubuntu stonking

💖 NAME 💖

okay so backup_listdumps — it's the little icon that shows you the dump hierarchy from the Backup Database. that's it, that's the whole job. she's a display girlie, not a doer. 🎀

✨ SYNOPSIS ✨

backup listdumps [-localauth] [-cell <cell name>] [-help]

backup listd [-l] [-c <cell name>] [-h]

yes bestie, listd is the short king version. same energy, fewer letters. 💅

🦋 DESCRIPTION 🦋

The backup listdumps command displays the dump hierarchy from the Backup Database. literally just reads it out loud to you. no cap. 🌸

👑 OPTIONS 👑

  • -localauth — makes a server ticket using a key from the local /etc/openafs/server/KeyFile file. the backup command interpreter shows it off to the Backup Server, Volume Server and VL Server during mutual authentication. do NOT combine this flag with the -cell argument, that's a whole mess. more deets in backup(8). 💜
  • -cell <cell name> — names the cell you wanna run the command in. do NOT combine this argument with the -localauth flag, same rule, different direction. for more details, see backup(8). ✨
  • -help — prints the online help for this command. every other valid option gets ignored, she's not multitasking. 😭

🌈 OUTPUT 🌈

The output displays the complete dump hierarchy and indicates the relationship between full and incremental dump levels. giving family tree, honestly. 🌳

Full dump levels appear at the left margin. The hierarchy can include more than one full dump level; each one defines a subhierarchy of dump levels that can be used for dumping different volume sets. so like, multiple main characters. multiple roots. it's fine.

Incremental dump levels appear below and indented to the right of their parent dump levels, which can be either full or incremental. Since multiple incremental dump levels can share the same parent, an incremental dump level is not always directly below its parent — the amount of indentation is what tells you the parent/child relationship. so read the indentation, not the proximity bestie. that's the vibe check. 🫶

If a dump level has an associated expiration date, it appears along with the level name. Absolute expiration dates appear in the format

<dump_level> expires at <day month date time year>

and relative expiration dates in the format

<dump_level> expires in {<years>y | <months>m | <days>d}

to indicate the number of years, months, days, or combination of the three after creation a dump expires when created at this level. ⏳

🎀 EXAMPLES 🎀

The following example depicts six dump hierarchies. The expiration date for all incremental dump levels is 13 days so that the corresponding tapes can be recycled two weeks after their creation. The expiration dates for all full dump levels is 27 days so that the corresponding tapes can be recycled four weeks after their creation.

% backup listdumps
/week1  expires in  27d
      /tuesday  expires in  13d
              /thursday  expires in  13d
      /sunday  expires in  13d
             /tuesday expires in  13d
                     /thursday expires in  13d
/week3  expires in  27d
      /tuesday  expires in  13d
              /thursday  expires in  13d
      /sunday  expires in  13d
             /tuesday expires in  13d
                     /thursday expires in  13d
/sunday1  expires in  27d
        /monday1  expires in  13d
        /tuesday1  expires in  13d
        /wednesday1  expires in  13d
        /thursday1  expires in  13d
        /friday1  expires in  13d
/sunday2  expires in  27d
        /monday2  expires in  13d
        /tuesday2  expires in  13d
        /wednesday2  expires in  13d
        /thursday2  expires in  13d
        /friday2  expires in  13d
/sunday3  expires in  27d
        /monday1  expires in  13d
        /tuesday1  expires in  13d
        /wednesday1  expires in  13d
        /thursday1  expires in  13d
        /friday1  expires in  13d
/sunday4  expires in  27d
        /monday2  expires in  13d
        /tuesday2  expires in  13d
        /wednesday2  expires in  13d
        /thursday2  expires in  13d
        /friday2  expires in  13d

look at all those little indented babies. precious. 🍓

🔥 PRIVILEGE REQUIRED 🔥

The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser "root" if the -localauth flag is included.

okay so fr fr: either you're on the list, or you're local superuser "root" and you brought -localauth. no list, no root, no entry. sorry babe. 💀

💜 SEE ALSO 💜

backup(8), backup_adddump(8), backup_deldump(8)

IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

and that's the tea, bestie 💅 this whole page came to you from OpenAFS, dated 2026-07-27, and yeah she's BACKUP_LISTDUMPS(8) in the command reference — now go check that hierarchy, you ate. 🦋✨

📦 where this page comes from