PLAKAR-BACKUP(1)
πΎ plakar-backup(1) β aka the plakar-backup manual page, bestie π
okay so real talk, this is the general commands manual for plakar-backup, and I'm gonna walk you through it like we're texting at 2am. grab a snack π
πΈ NAME πΈ
plakar-backup β literally creates a new snapshot in a Kloset store. that's the whole vibe. no cap. β¨
π¦ SYNOPSIS π¦
plakar backup [-cache path] [-category category] [-check] [-dry-run]
[-environment environment] [-force-timestamp timestamp]
[-ignore pattern] [-ignore-file file] [-job job] [-name name]
[-no-progress] [-no-xattr] [-o option=value] [-packfiles path]
[-perimeter perimeter] [-tag tag] [place ...]
look at all those flags. she's got range π
π DESCRIPTION π
so plakar backup makes a shiny new snapshot of place, or of the current directory if you don't say otherwise. and yeah, snapshots can be filtered to ignore specific files or directories based on patterns you hand over through the options. slay.
place can be any of these three icons:
- a path
- a URI
- a label in the form
@namethat references a source connector you configured withplakar-source(1)
the alias can ALSO be in the form @name[:path-override] if you wanna override the alias path right there on the command line β main character energy fr fr. here's the rule: if path-override starts with /, the whole path gets replaced with the override. otherwise it gets appended to the existing path. iykyk.
you can give multiple places too, as long as they all refer to different paths on the same remote β like different files or different prefixes on the same bucket. πͺ£ but heads up, not all importer connectors support this feature, so go read their documentation before you come for me π
The options are as follows:
β¨ OPTIONS β¨
-cachepath β tell it where to stash the vfs cache. special valuenodisables caching entirely, and special valuevfsuses the in-memory vfs cache (which is the default, periodt).-categorycategory β set the snapshot category. cute little label, love that for you π-checkβ do a full check on the backup after it succeeds. like a little vibe check but for your data β-dry-runβ do NOT write a snapshot. instead, do a dry run and print out the list of files and directories that would have been included. it respects all exclude patterns and the other options, but makes zero changes to the Kloset store. zero. none. it's giving window shopping ποΈ-environmentenvironment β set the snapshot environment.-force-timestamptimestamp β force a fixed timestamp (in ISO 8601 or relative human format) for the snapshot. super useful if you wanna reimport an existing backup with the same timestamp. lowkey iconic.-ignorepattern β drop in individual gitignore exclusion patterns to ignore files or directories in the backup. and yes, this option can be repeated β stack 'em π₯-ignore-filefile β point at a file full of gitignore exclusion patterns, one per line, to ignore files or directories in the backup.-jobjob β name the snapshot job.-namename β name the snapshot.-no-progressβ don't compute or display progress. here's the lore: by defaultplakar backupdoes two passes on the source β one to count the items, and a second to actually process them. this flag kills that first counting pass. it's also set implicitly for some importer connectors that just don't support the two-passes thing. not their fault tbh π-no-xattrβ skip extended attributes (xattrs) when creating the backup. bye bestie π-ooption=value β pass extra arguments to the source connector. the option you give here takes precedence over the configuration file. she said my rules π-packfilespath β choose where to put the temporary packfiles instead of building them in the default temporary directory. if you pass the special valuememory, the packfiles get built in memory. fast girl summer π-perimeterperimeter β set the snapshot perimeter.-tagtag β comma-separated list of tags to apply to the snapshot. tag it like you mean it π·οΈ
πΏ ENVIRONMENT πΏ
PLAKAR_TAGSβ comma-separated list of tags to apply to the snapshot during backup. but plot twist: it gets overridden by the-tagcommand-line flag. command line stays winning π
π EXIT STATUS π
plakar-backup exits 0 on success, and >0 if an error occurs. that's it. that's the whole story.
π§ EXAMPLES π§
okay these are the good part, the actual demonstrations π
create a snapshot of the current directory with two tags:
$ plakar backup -tag daily-backup,production
ignore files using patterns in a given file:
$ plakar backup -ignore-file ~/my-ignore-file /var/www
ignore files using patterns in one or more files, or from the command line β or honestly both, why not:
$ plakar backup -ignore-file ~/.plkignore -ignore "*.tmp" /var/www
define an alias for an s3 bucket and then back up multiple path prefixes. multi-place queen π:
$ plakar source add bucket s3://example.com \
access_key=... secret_access_key=...
$ plakar backup @bucket:/assets @bucket:/uploads @bucket:/logs
pass an option to the importer β in this case, to NOT traverse mount points:
$ plakar backup -o dont_traverse_fs=true /
π₯ SEE ALSO π₯
plakar(1), plakar-source(1) β go read those too, they're besties with this one π«Ά
ngl this page is from Debian, dated July 23, 2026, and it's the PLAKAR-BACKUP(1) general commands manual page. now go back up your stuff, bestie ππβ¨
π¦ where this page comes from
- nixpkgs unstable: plakar 1.1.7
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms