<HTML><HEAD>
<STYLE id=eMClientCss>blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
.plain pre, .plain tt { font-family: monospace; font-size: 100%; font-weight: normal; font-style: normal; white-space: pre-wrap; }
a img { border: 0px; }body {font-family: Times New Roman;font-size: 12pt;}
.plain pre, .plain tt {font-family: Times New Roman;font-size: 12pt;}
</STYLE>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff scroll=auto class>
<DIV>Aravinda, </DIV>
<DIV> </DIV>
<DIV>I was testing glusterfind and wondering if you could provide some feedback.</DIV>
<DIV> </DIV>
<DIV>My system is RH7.1 and I am using gluster 3.7.5. My setup for testing is a single brick with the parameters shown below... </DIV>
<DIV>I was testing glusterfind by copying over my source code and then running 'glusterfind pre' (code is ~140,000 files). The results of the test is that "glusterfind pre" took over an hour to process these 140,000 files and sat at 100% cpu-utilization for the extent of the run. Is this expected and is this the expected rate for "glusterfind pre" to process files? </DIV>
<DIV> </DIV>
<DIV>The reason I am asking is because my production gluster system sees approximately 2-million files changes per day. At this pace, glusterfind cannot process the requests fast enough to keep up.</DIV>
<DIV> </DIV>
<DIV>I also went back and tested file deletion through a removal of this directory. Looking at the /usr/var/lib/misc/glusterfsd/glusterfind/backup/gfs<BR>/tmp_output_0 file, it looks like it is only processing 1000-files per hour for file deletions.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>[root@ff01bkp gfs]# gluster volume info<BR>Volume Name: gfs<BR>Type: Distribute<BR>Volume ID: 7bbdfcf8-1801-4a2a-9233-0a3261cbcba7<BR>Status: Started<BR>Number of Bricks: 1<BR>Transport-type: tcp<BR>Bricks:<BR>Brick1: ffib01bkp:/data/brick01/gfs<BR>Options Reconfigured:<BR>diagnostics.client-log-level: WARNING<BR>diagnostics.brick-log-level: WARNING<BR>server.allow-insecure: on<BR>performance.readdir-ahead: on<BR>storage.build-pgfid: on<BR>changelog.changelog: on<BR>changelog.capture-del-path: on<BR>changelog.rollover-time: 90<BR>changelog.fsync-interval: 30<BR>client.event-threads: 8<BR>server.event-threads: 8<BR></DIV>
<DIV> </DIV>
<DIV>------ Original Message ------</DIV>
<DIV>From: "Aravinda" <<A href="mailto:avishwan@redhat.com">avishwan@redhat.com</A>></DIV>
<DIV>To: "Mathieu Chateau" <<A href="mailto:mathieu.chateau@lotp.fr">mathieu.chateau@lotp.fr</A>>; "M S Vishwanath Bhat" <<A href="mailto:msvbhat@gmail.com">msvbhat@gmail.com</A>></DIV>
<DIV>Cc: "gluster-users" <<A href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</A>></DIV>
<DIV>Sent: 9/7/2015 2:02:09 AM</DIV>
<DIV>Subject: Re: [Gluster-users] What is the recommended backup strategy for GlusterFS?</DIV>
<DIV> </DIV>
<DIV id=x2ce5a446c90d4f479f3764797b0e39f9 style="COLOR: #000000">
<BLOCKQUOTE class=cite2 cite=55ED2861.7000109@redhat.com type="cite">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 <SESSION_NAME> <VOLUME_NAME><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 class=cite 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 href="http://www.lotp.fr/" moz-do-not-send="true">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" moz-do-not-send="true">msvbhat@gmail.com</A>></SPAN>:<BR>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex">
<P dir=ltr>MS<SPAN><BR>On 5 Sep 2015 12:57 am, "Mathieu Chateau" <<A href="mailto:mathieu.chateau@lotp.fr" moz-do-not-send="true"><A class=moz-txt-link-abbreviated href="mailto:mathieu.chateau@lotp.fr">mathieu.chateau@lotp.fr</A></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/" moz-do-not-send="true">http://www.lotp.fr</A><BR>><BR>> 2015-09-03 13:05 GMT+02:00 Merlin Morgenstern <<A href="mailto:merlin.morgenstern@gmail.com" moz-do-not-send="true"><A class=moz-txt-link-abbreviated href="mailto:merlin.morgenstern@gmail.com">merlin.morgenstern@gmail.com</A></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" moz-do-not-send="true">Gluster-users@gluster.org</A><BR>>> <A href="http://www.gluster.org/mailman/listinfo/gluster-users" moz-do-not-send="true">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" moz-do-not-send="true">Gluster-users@gluster.org</A><BR>> <A href="http://www.gluster.org/mailman/listinfo/gluster-users" moz-do-not-send="true">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></BLOCKQUOTE></DIV></BODY></HTML>