I would like to use a cloud backup service on my home server. I am a complete beginner. I purchased a subscription for Proton Drive, but it looks like that just won’t work. Is there a secure cloud backup that works well on Linux? Bonus points if there’s a way to use proton drive. Extra bonus points, if I can set it up for automatic backups through a GUI.

  • Lupec@lemm.ee
    link
    fedilink
    English
    arrow-up
    8
    ·
    2 days ago

    Maybe consider a Hetzner storage box. They support borg, restic, rsync and probably more, there’s no ingress or egress fees and you get unlimited traffic. Very nice for off-site backups if, like myself, you’re on a limited budget.

    • Hiko0@feddit.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      2 days ago

      +1

      I‘ve been using a Hetzner Storage Box with Kopia via SFTP and was able to completely saturate my 500 Mbit/s upload.

  • grimer@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    2 days ago

    I’ve loved using Backblaze B2 buckets. Been using them for years and it’s very reasonable. Many different backup titles can use them.

  • pe1uca@lemmy.pe1uca.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 days ago

    I use rclone and duplicati depending on the needs of the backup.

    For long term I use duplicati, it has a GUI and you can upload it to several places (mines are spread between e2 and drive).
    You configure the backend, password for encryption, schedule, and version retention.

    rclone, with the crypt submodule, you use it to mount your backups as am external drive, so you need to manually handle the actual copy of the data into it, plus versioning and retention.

  • Moonrise2473@feddit.it
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    If you make a backup with a tool like Borg that creates encrypted archives, then using AWS S3 glacier is the cheapest.

    What’s bad about it: if you ever need those files again, it’s going to be VERY expensive to download them again, so it has to be treated as the “what if a nuke hits my city and all the local and off-site backups are vaporized” solution

    Also: it’s not recommended to directly host plain files, they need to be in an archive format with big chunks, as the API calls that are used to list them during sync are counted in a very expensive way