social.dk-libre.fr is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Search results for tag #borg

[?]Domdel AKA Data » 🌐
@domdel@mastodon.social

@celfred Alors, J'utilisais . Demain je teste le et au vu de ce que j'ai lu, je pense l'adopter.

    [?]Rocketman [he/him, they/them] » 🌐
    @slothrop@chaos.social

    Borg frontends for Gnome that aren’t DejaDup*

    Suggestions?

    * because no earthly power can bring DejaDup to remember my credentials, and my time is too precious to deal with this shit

      [?]Cyril Brulebois » 🌐
      @CyrilBrulebois@mamot.fr

      Correction:

      - using two `mv` saves time because copying is not needed;
      - using two `mv` avoids risking `ENOSPC` during the sync;
      - using two `mv` does *not* help with the backup part.

      Toying with a little more, even after a clean `mv` of the parent directory, it goes through all files again, and I'm looking at 14+ minutes again.

      All that with NVMe on the left, SSD on the right, and a somewhat limited machine on the right side (running borg): 2 cores (Pentium G3240 @ 3.10GHz).

        [?]Cyril Brulebois » 🌐
        @CyrilBrulebois@mamot.fr

        And of course, because of the copy aspect, create (with --progress and --stats for good measure) actually needs to chug through all those (big) files to see which chunks are new etc. so that's also taking a long while.

        Enough to let me learn how to parse this:

        151.33 GB O 148.94 GB C 993.03 kB D 281558 N

        and to start thinking everything is going to be fine (almost everything being Compressed already, almost nothing Deduplicated).

          [?]Cyril Brulebois » 🌐
          @CyrilBrulebois@mamot.fr

          I thought I'd verify what I thought I was remembering.

          But yeah, if you know you're renaming stuff, it makes sense to:

          - run unison;
          - rename on the left;
          - rename on the right;
          - run unison (to confirm).

          Renaming on one side leads to lengthy comparison operations, until:

          new dir ----> new-name
          deleted ----> old-name

          But everything is *copied*, not moved, even with the “shortcut” optimization.

          Hopefully I don't have a tip to share in a few minutes…

            1 ★ 0 ↺

            [?]oldsysops » 🌐
            @oldsysops@social.dk-libre.fr

            @Beurt@mamot.fr c'est moins mais ca marche™.
            les restaurations se passent bien, l'option mount permet de chercher quand on sait plus et on peut configuré facilement la retention.

            et quelque part ca reste dans le principe faire une seule chose et le faire bien !

              [?]patpro » 🌐
              @patpro@social.patpro.net

              @Beurt suis sur Borg depuis des années (2 macOS, 2 freebsd, 1 linux) vers différentes cibles.
              J'ai écrit là dessus il y'a longtemps : https://www.patpro.net/blog/index.php/2019/04/30/3201-moving-to-borgbackup/
              Et plus récemment j'ai longuement comparé #Borg, #Restic et #Kopia : https://www.patpro.net/blog/index.php/2024/03/07/3576-borg-kopia-restic-un-comparatif/

              Mais parfois, ça part en sucette et il faut le garder à l'esprit : https://www.patpro.net/blog/index.php/2024/02/11/3564-borgbackup-its-complicated/

              Dans tous les cas je ne suis pas prêt à changer de crèmerie, je suis bien avec Borg.