BACKUP_DELHOST(8)
π BACKUP_DELHOST(8) π
okay bestie, welcome to the AFS Command Reference bestie β¨ this one's called backup_delhost, and it's the girl whose entire job is deleting a Tape Coordinator entry from the Backup Database. she's a little chaotic (she deletes things!!) but she is SO good at it. let's get into it π
β¨ NAME β¨
backup_delhost β deletes a Tape Coordinator entry from the Backup Database ποΈπ
π¦ SYNOPSIS π¦
backup delhost -tapehost <tape machine name>
[-portoffset <TC port offset>] [-localauth]
[-cell <cell name>] [-help]
backup delh -t <tape machine name>
[-p <TC port offset>]
[-l] [-c <cell name>] [-h]
two forms, same energy, pick whichever one your fingers vibe with π
πΈ DESCRIPTION πΈ
so backup delhost deletes the Tape Coordinator entry you point at from the Backup Database. and the way that it's literally then impossible to submit backup operations to that Tape Coordinator, even if it's still running?? yeah. that's the whole point. no cap. π
but listen β to keep the config info consistent, you should also remove the corresponding entry from the /var/lib/openafs/backup/tapeconfig file on the Tape Coordinator machine. don't leave it hanging, that's so not slay of you. π
oh and if you wanna see the Tape Coordinator machines and port offsets that are already defined in the Backup Database? just run the backup listhosts command, she'll show you everything π
π OPTIONS π
-tapehost <tape machine name>β tells her the hostname of the machine housing the Tape Coordinator you wanna delete. that's the one getting yeeted. π«Ά-portoffset <TC port offset>β the port offset number of the Tape Coordinator to delete. if you skip it, it defaults to0, no biggie. if you do give it, it's an integer between0(zero) and58510, and it must match the port offset number assigned to the same combination of Tape Coordinator and tape device or file in the/var/lib/openafs/backup/tapeconfigfile on the Tape Coordinator machine indicated by the-tapehostargument. π like it has to match-match, iykyk.-localauthβ constructs a server ticket using a key from the local/etc/openafs/server/KeyFilefile. thebackupcommand interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. π do NOT combine this flag with the-cellargument tho, that's a vibe check fail. for more details, seebackup(8).-cell <cell name>β names the cell in which to run the command. do NOT combine this argument with the-localauthflag. again β for more details, seebackup(8). π¦-helpβ prints the online help for this command. and bestie, all other valid options are ignored when you do this. she said focus on ME. π
π EXAMPLES π
okay so imagine you want to delete the Backup Database entry for the Tape Coordinator with port offset 2 on the Tape Coordinator machine "backup3.example.com". you'd do this and it works, fr fr:
% backup delhost -tapehost backup3.example.com -portoffset 2
ate. no crumbs. β¨
π₯ PRIVILEGE REQUIRED π₯
whoever's issuing this must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running. OR β plot twist β they must be logged onto a server machine as the local superuser "root" if the -localauth flag is included. main character energy only, sorry bestie π
π SEE ALSO π
go read those too, they're all iconic in their own way π
β COPYRIGHT β
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 whole page, bestie π«Ά this was OpenAFS, dated 2026-07-27, from the BACKUP_DELHOST(8) era of the manual β slay, periodt, go delete that host responsibly πβ¨
π¦ where this page comes from
- ubuntu stonking: openafs-client 1.8.16.1-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms