BBACKUPD(8)

πŸ’– BBACKUPD(8) β€” Box Backup's client daemon, bestie edition πŸŽ€

okay so picture this: it's bbackupd, it's the Box Backup client daemon, and it is literally the hardest-working girlie on your machine. let's get into it πŸ’…


✨ SYNOPSIS ✨

bbackupd [-DFkqvVT] [-c config-file] [-t tag]

πŸ¦‹ DESCRIPTION πŸ¦‹

so bbackupd runs on client computers, chilling in the background, out here finding new files to back up. no cap. and when it is time for a backup, bbackupd will connect to the server (bbstored) to upload the files. iconic behavior fr fr πŸ’–

a running bbackupd daemon can be controlled with the bbackupctl command β€” to make it shut down, reload its configuration, or start an immediate backup. queen stays manageable πŸ‘‘

bbackupd needs to be configured to tell it which files to back up, how often, and to which server (running bbstored). see the Client Configuration page for more information. for this, you must write a configuration file. you must either place it in the default location, or tell bbackupd where to find it. no config, no service, that's the vibe check 🫢

you can check the default location with the -h option. the default on Unix systems is usually /etc/box/bbackupd.conf. on Windows systems, it is bbackupd.conf in the same directory where bbackupd.exe is located. and if bbackupd cannot find or read the configuration file, it will log an error message and exit. πŸ’€ (rip)

bbackupd usually writes log messages to the system logs, using the facility local5, which you can use to filter them to send them to a separate file. it can also write them to the console, see options below. and bestie, listen β€” if bbackupd is not doing what you expect, please check the logs first of all. the logs know everything, they're the main character of debugging 🌸

πŸŽ€ Options πŸŽ€

  • -c config-file β€” use the specified configuration file. if -c is omitted, the last argument is the configuration file. if none is specified, the default is used (see above). pick your fighter ✨
  • -D β€” Debugging mode. do not fork into the background (do not run as a daemon). not available on Windows.
  • -F β€” No-fork mode. same as -D for bbackupd. not available on Windows.
  • -k β€” keep console open after fork, keep writing log messages to it. not available on Windows.
  • -q β€” run more quietly. reduce verbosity level by one. available levels are NOTHING, FATAL, ERROR, WARNING, NOTICE, INFO, TRACE, EVERYTHING. default level is NOTICE in non-debugging builds. use once to drop to WARNING level, twice for ERROR level, four times for no logging at all. shhhh 🀫
  • -v β€” run more verbosely. increase verbosity level by one. use once to raise to INFO level, twice for TRACE level, three times for EVERYTHING (currently the same as TRACE). yes queen, tell me everything πŸ—£οΈ
  • -V β€” run at maximum verbosity (EVERYTHING level). the loudest setting, it's giving full transparency πŸ’…
  • -t tag β€” tag each console message with specified marker. mainly useful in testing when running multiple daemons on the same console. name tags but for daemons 🏷️
  • -T β€” timestamp each line of console output. ⏰

πŸ“ FILES πŸ“

  • /etc/box/bbackupd.conf

πŸ‘€ SEE ALSO πŸ‘€

bbackupd.conf(5), bbackupd-config(8), bbackupctl(8)

go read those too, they're part of the friend group 🫢


πŸ‘‘ AUTHORS πŸ‘‘

  • Ben Summers
  • Per Thomsen
  • James O'Gorman

absolute legends, every single one 🌈


and that's the whole page bestie!! this was Box Backup 0.11, dated 06/06/2024, and it's the BBACKUPD(8) manual. slay, stay backed up, and check those logs πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from