MRB(8)
πΎ MRB β the manual page, bestie edition πΎ
okay so you found the mrb(8) page β it lives in the System Manager's Manual section, which is the fancy way of saying "root stuff, admin vibes, main character energy for sysadmins." π«Ά
β¨ NAME β¨
mrb β manage incremental snapshots with rsync/make.
yes that's literally the whole name section, she's brief and she's iconic π
π SYNOPSIS π
mrb command
that's it. one command. no flags hanging off the front. slay. β¨
π¦ DESCRIPTION π¦
okay so mrb is a simple little helper for making efficient incremental snapshots of a set β or sets β of directories, like, whenever you feel like it. no cap. π
it's the kind of thing you can drop into a regular automated backup regime and just let it cook, OR you can run it by hand when you wanna manually checkpoint your changes at a convenient moment in time. both are valid. both are a vibe. π
π COMMANDS π
here's the thing β every command below uses MODULE, which is just the name of one of your snapshot definitions. plug yours in and go. π«Ά
new-MODULEβ makes a skeleton definition for a brand new snapshot calledMODULE. it's giving "blank canvas, first draft, we begin." β¨dest-MODULEβ creates the destination dir forMODULE. and like, heads up: this directory must already exist before you can create a snapshot. it's non-negotiable bestie. πsnap-MODULEβ creates an actual snapshot ofMODULE. the moment we've all been waiting for. πsyncβ creates snapshots of ALL your defined modules at once. and ooh β if you run it as root</>, it can be configured to include the modules of other users too (peepMRB_SYNC_USERSin~/.mrb/defaults). multi-user slay. πhelpβ shows mrb's own help text. when in doubt, ask the girl herself. πΈ
π CONFIGURATION FILES π
π§ Per-user configuration
these files are where you drop global and local config options. use them. they're useful. no cap.
/etc/default/mrbβ the system default configuration. the OG, the blueprint. π~/.mrb/defaultsβ your per-user configuration. this is YOUR house, YOUR rules. π
π Per-user options
these ones control how things behave for all of a user's modules at once. group settings, basically. π«Ά
MRB_SNAPSHOT_LOGβ an optional file path where transfer details get recorded. if it's unset, those details simply won't be logged. your call bestie. πMRB_SYNC_USERSβ a space separated list of users whose modules should get included in async. mostly this is a root-only flex, becausemrbwill assume the identity of each user before snapshotting their modules. if it's unset, only the invoking user's modules get sync'ed. periodt. πMRB_CONFDIRβ a space separated list of directories to search for module definition (*.mrc) files. they get searched in the order given, and new modules get added by default to the last one listed. honestly? there should be very few reasons to change the default value. leave her alone. π
πΈ Per-module configuration
the default MRB_CONFDIR value goes looking for module definitions in these two spots:
/etc/mrb/*.mrcβ the system-wide spot. ποΈ~/.mrb/*.mrcβ and this is the one β those created bynew-MODULEland in this latter location by default. π
β Per-module options
okay so in every single one of these, module means the name of the particular module the value applies to. these options go in a file named module.mrc. π
module_SRCβ a space separated list of the files and (top level) directories to include in the snapshots for this module. and yes, these can be remote urls. travel broadens the mind. πmodule_DESTβ the (local) directory root where snapshots ofmoduleget stored. keep it local, keep it cute. πmodule_INCLUDEβ an optional list ofrsync(1)include patterns. β¨module_EXCLUDEβ an optional list ofrsync(1)exclude patterns. bye girl πmodule_FILTERβ an optional list ofrsync(1)filter patterns. π§module_FILTER_FILEβ an optional filename forrsync(1)dir-merge filtering support. iykyk. πmodule_RSYNC_OPTIONSβ optional additionalrsync(1)options passed verbatim when it gets invoked. verbatim means verbatim, don't get creative. π«Άmodule_PRECOMMANDβ an optional shell command to run just before creating a new snapshot. and listen: if that command doesn't return a successful exit status, the snapshot creation gets aborted before it even begins. it's handy for mounting removable media or similar. no snapshot on a bad vibe. πmodule_POSTCOMMANDβ an optional shell command to execute after making the snapshot. heads up though: it won't be called if the snapshot creation failed at an earlier stage, and its return status may halt a sync operation if it fails while there are still more modules to process. you could use it to unmount removable media again, for example. π§Ήmodule_USERβ an optional user name to check thatmrbis running as, before performing a snapshot. this is how you make sure you've got the correct permission to access the files being mirrored before you get too far. check yourself before you wreck yourself. π
π SEE ALSO π
the holy trinity honestly π
π AUTHOR π
mrb was written by Ron <ron@debian.org>. king behaviour. π
and that's the whole page bestie β MRB(8) from the System Manager's Manual, dated May 9, 2006, and yes she's an old queen but she still eats π
β¨ go make some snapshots, you've got this π«Άπ
π¦ where this page comes from
- debian bookworm: mrb 0.3+nmu2
- ubuntu jammy: mrb 0.3+nmu1
- ubuntu noble: mrb 0.3+nmu3
- ubuntu questing: mrb 0.3+nmu3
- ubuntu resolute: mrb 0.5 Β· GPL-2.0-only
- ubuntu stonking: mrb 0.5 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms