Borgbackup

Fleeting

• Référence externe : https://borgbackup.readthedocs.io/en/stable/usage/serve.html
• Référence externe : https://borgbackup.readthedocs.io/en/stable/usage/init.html

borg serve has special support for ssh forced commands (see authorized_keys example below): it will detect that you use such a forced command and extract the value of the –restrict-to-path option(s).

— https://borgbackup.readthedocs.io/en/stable/usage/serve.html

Allow an SSH keypair to only run borg, and only have access to /path/to/repo.

$ cat ~/.ssh/authorized_keys command=“borg serve –restrict-to-path /path/to/repo”,restrict ssh-rsa AAAAB3[…]

$ cat ~/.ssh/authorized_keys command=“export BORG_XXX=value; borg serve […]",restrict

— https://borgbackup.readthedocs.io/en/stable/usage/serve.html

For remote backups the encryption is done locally - the remote machine never sees your passphrase, your unencrypted key or your unencrypted files.

— https://borgbackup.readthedocs.io/en/stable/usage/init.html?highlight=repokey#encryption-mode-tldr

can I stop a backup without regrets?

• Référence externe : https://www.reddit.com/r/BorgBackup/comments/vspkak/can_i_stop_a_backup_without_regrets/

Good to go. Borg is designed to handle this situation gracefully. It will auto resume when restarted. It may roll back to the last checkpoint but those are defaulting to be fairly frequent unless you overrode the default. I use control c if I happen to be running on the command line, but kill will also work if it was scripted

— https://www.reddit.com/r/BorgBackup/comments/vspkak/can_i_stop_a_backup_without_regrets/

available space

The repository quota size is reached, what can I do?

The simplest solution is to increase or disable the quota and resume the backup: borg config /path/to/repo storage_quota 0

If you are bound to the quota, you have to free repository space. The first to try is running borg compact to free unused backup space (see also Separate compaction): borg compact /path/to/repo

— https://borgbackup.readthedocs.io/en/stable/faq.html

create progress

• Référence externe : https://borgbackup.readthedocs.io/en/stable/usage/create.html borgbackup

  The –progress option shows (from left to right)

  • Original (O),
  • Compressed (C),
  • and Deduplicated (D),
  • then the Number of files (N) processed so far,
  • followed by the currently processed path.

  — https://borgbackup.readthedocs.io/en/stable/usage/create.html

  –list outputs a list of all files, directories and other file system items it considered (no matter whether they had content changes or not). For each item, it prefixes a single-letter flag that indicates type and/or status of the item.

  If you are interested only in a subset of that output, you can give e.g. –filter=AME and it will only show regular files with A, M or E status (see below).

  A uppercase character represents the status of a regular file relative to the “files” cache (not relative to the repo – this is an issue if the files cache is not used). Metadata is stored in any case and for ‘A’ and ‘M’ also new data chunks are stored. For ‘U’ all data chunks refer to already existing chunks.

  • ‘A’ = regular file, added (see also I am seeing ‘A’ (added) status for an unchanged file!? in the FAQ)
  • ‘M’ = regular file, modified
  • ‘U’ = regular file, unchanged
  • ‘C’ = regular file, it changed while we backed it up
  • ‘E’ = regular file, an error happened while accessing/reading this file

  A lowercase character means a file type other than a regular file, borg usually just stores their metadata:

  • ‘d’ = directory
  • ‘b’ = block device
  • ‘c’ = char device
  • ‘h’ = regular file, hardlink (to already seen inodes)
  • ‘s’ = symlink
  • ‘f’ = fifo

  — https://borgbackup.readthedocs.io/en/stable/usage/create.html

Notes pointant ici

• how I organize my static files with IPFS and org-roam

Permalink