Printing printers.

  • 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle



  • Rootiest@lemm.eetoSelfhosted@lemmy.worldHow to store backups?
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    I really love Kopia.

    I mostly use it for cloud backups but it also works great for local/network storage as well.

    It’s really fast and efficient, supports cutting edge encryption and compression algorithms and the de-duplication and file-splitting features will let you generate frequent snapshots while costing you minimal storage.

    Snapshots are also effortless to mount and it even supports error correction to protect against bit-flipping and other long-term storage risks.

    It’s also cross-platform and FOSS.

    De-duplication prevents duplicate bits of data from being stored twice. Even if they are different file names or even synced from different systems.

    The rolling hash/file-splitting means if you modify a 25GB file and only change a couple MB then only the changed couple MB will need to be stored. This means you can spend a month modifying small parts of a massive file thousands of times and avoid storing a new 25GB file thousands of times to archive those changes.


  • Use KeePass.

    My concern with using a text file is you have to defrost it to use it and whenever it’s not encrypted it’s potentially exposed. You are also vulnerable to keyloggers or clipboard captures

    KeePass works entirely locally, no cloud. And it’s far more secure/functional than a text file.

    I personally use KeePass, secured with a master password + YubiKey.

    Then I sync the database between devices using SyncThing over a Tailscale network.

    KeePass keeps the data secure at rest and transferring is always done P2P over SSL and always inside a WireGuard network so even on public networks it’s protected.

    You could just as easily leave out the Tailscale/SyncThing and just manually transfer your database using hardware air-gapped solutions instead but I am confident in the security of this solution for myself. Even if the database was intercepted during transit it’s useless without the combined password/hardware key.