[Borgbackup] best practices for repo access hardcopy

[Thomas Gries]

Am 05.03.22 um 15:35 schrieb Tamas Papp:
> Hi,
>
> I am wondering what others do to back up repository access information
> as hardcopy.
>
> I am using a borgbase remote repository. Currently I print
>
> 1. the borgmatic .yaml file and
> 2. the ssh key
>
> on paper, expecting to retype it in case a disaster happens to
> electronic copies (which I keep on a USB stick).
>
> I thought of
>
> 1. stripping the YAML comments,
>
> 2. making a tar.gz archive of the above,
>
> 3. printing it as a large QR code (with as much redundancy as allowed by
> the limits of QR).
>
> Suggestions appreciated.
>
> best,
>
> Tamas
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup

https://borgbackup.readthedocs.io/en/stable/usage/key.html

also lists the --qr-html option

There are three backup formats.

The normal backup format is suitable for digital storage as a file.
The |--paper| backup format is optimized for printing and typing in 
while importing, with per line checks to reduce problems with manual input.
The |--qr-html| creates a printable HTML template with a QR code and a 
copy of the |--paper|-formatted key.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220305/8d8c86ec/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 5DZXTVEpLjY7DJMs.jpeg
Type: image/jpeg
Size: 25320 bytes
Desc: not available
URL: <https://mail.python.org/pipermail/borgbackup/attachments/20220305/8d8c86ec/attachment-0001.jpeg>