Mathieu Chateau
2015-Sep-04 19:27 UTC
[Gluster-users] What is the recommended backup strategy for GlusterFS?
Hello, so far I use rsnapshot <https://github.com/rsnapshot/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. 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. Cordialement, Mathieu CHATEAU http://www.lotp.fr 2015-09-03 13:05 GMT+02:00 Merlin Morgenstern <merlin.morgenstern at gmail.com> :> I have about 1M files in a GlusterFS with rep 2 on 3 nodes runnnig gluster > 3.7.3. > > What would be a recommended automated backup strategy for this setup? > > I already considered the following: > > 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. > > 2) rsync the mounted file share to a second directory and do a tar on the > entire directory after rsync completed > > 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 > > Currently I am only able to do the second option, but the fist option > seems to be the most atractive. > > Thank you for any help on this. > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150904/167bb369/attachment.html>
M S Vishwanath Bhat
2015-Sep-05 19:03 UTC
[Gluster-users] What is the recommended backup strategy for GlusterFS?
MS On 5 Sep 2015 12:57 am, "Mathieu Chateau" <mathieu.chateau at lotp.fr> wrote:> > Hello, > > so far I use rsnapshot. This script do rsync with rotation, and mostimportant 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.> > I am also interested in solution 1), but need to be stored on distinctdrives/servers. We can't afford to loose data and snapshot in case of human error or disaster.> > > > Cordialement, > Mathieu CHATEAU > http://www.lotp.fr > > 2015-09-03 13:05 GMT+02:00 Merlin Morgenstern <merlin.morgenstern at gmail.com>:>> >> I have about 1M files in a GlusterFS with rep 2 on 3 nodes runnniggluster 3.7.3.>> >> What would be a recommended automated backup strategy for this setup? >> >> I already considered the following:Have you considered glusterfs geo-rep? It's actually for disaster recovery. But might suit your backup use case as well. My two cents //MS>> >> 1) glusterfs snapshots in combination with dd. This unfortunatelly wasnot 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.>> >> 2) rsync the mounted file share to a second directory and do a tar onthe entire directory after rsync completed>> >> 3) combination of 1 and 2. Doing a snapshot that gets mountedautomaticaly and then rsync from there. Problem: How to automate snapshots and how to know the mount path>> >> Currently I am only able to do the second option, but the fist optionseems to be the most atractive.>> >> Thank you for any help on this. >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150906/50cbb591/attachment.html>