<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    We have one more tool. glusterfind!<br>
    <br>
    This tool comes with gluster installaton, if you are using Gluster
    3.7.  glusterfind enables Changelogging(Journal) to Gluster Volume
    and uses that information to detect the changes happened in the
    Volume. <br>
    <br>
    1. Create a glusterfind session using, glusterfind create
    &lt;SESSION_NAME&gt; &lt;VOLUME_NAME&gt;<br>
    2. Do a full backup.<br>
    3. Run glusterfind pre command to generate the output file with the
    list of changes happened in Gluster Volume after glusterfind create.
    For usage information glusterfind pre --help<br>
    4. Consume that output file and backup only the files listed in
    output file.<br>
    5. After consuming the output file, run glusterfind post command.
    (glusterfind post --help)<br>
    <br>
    Doc link:
<a class="moz-txt-link-freetext" href="http://gluster.readthedocs.org/en/latest/GlusterFS%20Tools/glusterfind/index.html">http://gluster.readthedocs.org/en/latest/GlusterFS%20Tools/glusterfind/index.html</a><br>
    <br>
    This tool is newly released with Gluster release 3.7, please report
    issues or request for features here
    <a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS">https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS</a><br>
    <pre class="moz-signature" cols="72">regards
Aravinda</pre>
    <div class="moz-cite-prefix">On 09/06/2015 12:37 AM, Mathieu Chateau
      wrote:<br>
    </div>
    <blockquote
cite="mid:CACpSnaJb5ceRnF1TwP7e=e1VAeWzU+zbm0MsRo0ZV7g0icB04g@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hello,
        <div><br>
        </div>
        <div>for my needs, it's about having a simple "photo" of files
          present 5 days ago for example.</div>
        <div>But i do not want to store file data twice, as most file
          didn't change.</div>
        <div>Using snapshot is convenient of course, but it's risky as
          you loose both data and snapshot in case of failure (snapshot
          only contains delta blocks).</div>
        <div>Rsync with hardlink is more resistant (inode stay until
          last reference is removed)</div>
        <div><br>
        </div>
        <div>But interested to hear about production setup relying on it</div>
      </div>
      <div class="gmail_extra"><br clear="all">
        <div>
          <div class="gmail_signature">Cordialement,<br>
            Mathieu CHATEAU<br>
            <a moz-do-not-send="true" href="http://www.lotp.fr"
              target="_blank">http://www.lotp.fr</a></div>
        </div>
        <br>
        <div class="gmail_quote">2015-09-05 21:03 GMT+02:00 M S
          Vishwanath Bhat <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:msvbhat@gmail.com" target="_blank">msvbhat@gmail.com</a>&gt;</span>:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <p dir="ltr">MS<span class=""><br>
                On 5 Sep 2015 12:57 am, "Mathieu Chateau" &lt;<a
                  moz-do-not-send="true"
                  href="mailto:mathieu.chateau@lotp.fr" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:mathieu.chateau@lotp.fr">mathieu.chateau@lotp.fr</a></a>&gt;
                wrote:<br>
                &gt;<br>
                &gt; Hello,<br>
                &gt;<br>
                &gt; so far I use rsnapshot. This script do rsync with
                rotation, and most important same files are stored only
                once through hard link (inode). I save space, but still
                rsync need to parse all folders to know for new files.<br>
                &gt;<br>
                &gt; I am also interested in solution 1), but need to be
                stored on distinct drives/servers. We can't afford to
                loose data and snapshot in case of human error or
                disaster.<br>
                &gt;<br>
                &gt;<br>
                &gt;<br>
                &gt; Cordialement,<br>
                &gt; Mathieu CHATEAU<br>
                &gt; <a moz-do-not-send="true"
                  href="http://www.lotp.fr" target="_blank">http://www.lotp.fr</a><br>
                &gt;<br>
                &gt; 2015-09-03 13:05 GMT+02:00 Merlin Morgenstern &lt;<a
                  moz-do-not-send="true"
                  href="mailto:merlin.morgenstern@gmail.com"
                  target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:merlin.morgenstern@gmail.com">merlin.morgenstern@gmail.com</a></a>&gt;:<br>
                &gt;&gt;<br>
                &gt;&gt; I have about 1M files in a GlusterFS with rep 2
                on 3 nodes runnnig gluster 3.7.3.<br>
                &gt;&gt;<br>
                &gt;&gt; What would be a recommended automated backup
                strategy for this setup?<br>
                &gt;&gt;<br>
                &gt;&gt; I already considered the following:</span></p>
            <p dir="ltr">Have you considered glusterfs geo-rep? It's
              actually for disaster recovery. But might suit your backup
              use case as well.</p>
            <p dir="ltr">My two cents</p>
            <span class="HOEnZb"><font color="#888888">
                <p dir="ltr">//MS</p>
              </font></span>
            <div class="HOEnZb">
              <div class="h5">
                <p dir="ltr">&gt;&gt;<br>
                  &gt;&gt; 1) glusterfs snapshots in combination with
                  dd. This unfortunatelly was not possible so far as I
                  could not find any info on how to make a image file
                  out of the snapshots and how to automate the snapshot
                  procedure.<br>
                  &gt;&gt;<br>
                  &gt;&gt; 2) rsync the mounted file share to a second
                  directory and do a tar on the entire directory after
                  rsync completed<br>
                  &gt;&gt;<br>
                  &gt;&gt; 3) combination of 1 and 2. Doing a snapshot
                  that gets mounted automaticaly and then rsync from
                  there. Problem: How to automate snapshots and how to
                  know the mount path<br>
                  &gt;&gt;<br>
                  &gt;&gt; Currently I am only able to do the second
                  option, but the fist option seems to be the most
                  atractive.<br>
                  &gt;&gt;<br>
                  &gt;&gt; Thank you for any help on this.<br>
                  &gt;&gt;<br>
                  &gt;&gt;
                  _______________________________________________<br>
                  &gt;&gt; Gluster-users mailing list<br>
                  &gt;&gt; <a moz-do-not-send="true"
                    href="mailto:Gluster-users@gluster.org"
                    target="_blank">Gluster-users@gluster.org</a><br>
                  &gt;&gt; <a moz-do-not-send="true"
                    href="http://www.gluster.org/mailman/listinfo/gluster-users"
                    target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
                  &gt;<br>
                  &gt;<br>
                  &gt;<br>
                  &gt; _______________________________________________<br>
                  &gt; Gluster-users mailing list<br>
                  &gt; <a moz-do-not-send="true"
                    href="mailto:Gluster-users@gluster.org"
                    target="_blank">Gluster-users@gluster.org</a><br>
                  &gt; <a moz-do-not-send="true"
                    href="http://www.gluster.org/mailman/listinfo/gluster-users"
                    target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
                </p>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
    </blockquote>
    <br>
  </body>
</html>