<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 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"><<a href="mailto:msvbhat@gmail.com" target="_blank">msvbhat@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr"></p>
<p dir="ltr">MS<span class=""><br>
On 5 Sep 2015 12:57 am, "Mathieu Chateau" <<a href="mailto:mathieu.chateau@lotp.fr" target="_blank">mathieu.chateau@lotp.fr</a>> wrote:<br>
><br>
> Hello,<br>
><br>
> 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>
><br>
> 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>
><br>
><br>
><br>
> Cordialement,<br>
> Mathieu CHATEAU<br>
> <a href="http://www.lotp.fr" target="_blank">http://www.lotp.fr</a><br>
><br>
> 2015-09-03 13:05 GMT+02:00 Merlin Morgenstern <<a href="mailto:merlin.morgenstern@gmail.com" target="_blank">merlin.morgenstern@gmail.com</a>>:<br>
>><br>
>> I have about 1M files in a GlusterFS with rep 2 on 3 nodes runnnig gluster 3.7.3.<br>
>><br>
>> What would be a recommended automated backup strategy for this setup?<br>
>><br>
>> 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">>><br>
>> 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>
>><br>
>> 2) rsync the mounted file share to a second directory and do a tar on the entire directory after rsync completed<br>
>><br>
>> 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>
>><br>
>> Currently I am only able to do the second option, but the fist option seems to be the most atractive.<br>
>><br>
>> Thank you for any help on this.<br>
>><br>
>> _______________________________________________<br>
>> Gluster-users mailing list<br>
>> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
>> <a href="http://www.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
> <a 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>