borg-repo-delete(1)
π borg-repo-delete β bestie's guide to nuking a repo (manual name: borg-repo-delete(1))
β¨ NAME β¨
borg-repo-delete β okay so this one deletes a repository. That's it. That's the whole personality. π
πΈ SYNOPSIS πΈ
borg [common options] repo-delete [options]
π¦ DESCRIPTION π¦
This command deletes a complete repository. Fr fr. The whole thing. Gone. π
When you delete a complete repository, the security info and local cache for it (if any) are also deleted. Like, they go down with the ship, no survivors. But lowkey you do have options: you can delete just the local cache with the --cache-only option, or keep the security info around with the --keep-security-info option. Choose your fighter. π
--force also destroys a store that has no repository config, provided it looks like a borg store (it has the packs, archives, index and config namespaces). So like, if it's giving borg store but it lost its config, --force will still handle it. β¨
Deleting a repository needs its key, because locking it needs the key. No key, no lock, no delete. If the key is lost, the repository is useless and has to be deleted with the storage's own tools. It's giving "not me crying over a lost key." π
Always first use --dry-run --list to see what would be deleted. Ma'am. Please. Look before you leap. π
β OPTIONS β
See borg-common(1) for common options of Borg commands. (All the shared lore lives over there, iykyk.)
π options
-n,--dry-runβ do not change the repository. A little peek, no touching. π--listβ output a verbose list of archives. Receipts, basically.--forceβ do not ask for confirmation, just delete the repository. And yes, this also works if the repository is damaged to a point where its archives can not be listed anymore. Zero hesitation, zero questions. π--cache-onlyβ delete only the local cache for the given repository. Just the cache, nothing else, we're being gentle.--keep-security-infoβ keep the local security info when deleting a repository. So the security info survives the purge. π«Ά
π EXAMPLES π
# delete the whole repository and the related local cache:
$ borg repo-delete
You requested to DELETE the following repository completely *including* 2 archives it contains:
------------------------------------------------------------------------------
Repository ID: e7046adda9b2a76bb4fac8d707ab7dc12a836391c8c3612cc12d461e713c5bc1
Location: /path/to/repo
------------------------------------------------------------------------------
Type 'YES' if you understand this and want to continue: YES
π SEE ALSO π
π AUTHOR π
The Borg Collective β iconic behavior, honestly.
Sign-off time bestie: this page came from the borg backup tool, it's dated 2026-10-07, and its manual name is borg-repo-delete(1). Slay, stay backed up, and maybe don't delete anything without a --dry-run first. Periodt. π§π
π¦ where this page comes from
- ubuntu stonking: borgbackup2 2.0.0b25-4 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms