<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Yes for long term backups LVM snapshots
might not be the solution. There is no side effect in backing up
the bricks. The data would indeed be readable. And if you back up
"/var/lib/glusterd/vols/<volname>" on each volume as well,
you can effectively recreate the volume from the bricks at a later
stage.<br>
<br>
Regards,<br>
Avra<br>
<br>
On 08/17/2015 04:11 PM, Thibault Godouet wrote:<br>
</div>
<blockquote
cite="mid:CA+K9O9_WaW7isUfcfY1EZcESjeNDNBfsJLX=fqVwC1J7UrXS9Q@mail.gmail.com"
type="cite">
<p dir="ltr">Thanks Avra.</p>
<p dir="ltr">I am aware of the Gluster snapshots, but didn't think
about using them on the offsite replica. That could indeed
cover the short term backups, and be used to do longer term
backups from.</p>
<p dir="ltr">What I perhaps wasn't clear about is that we'll need
longer term backups to tape (e.g. to keep multiple years). I
don't think keeping LVM snapshots for that long would really
work.<br>
So basically my initial question was on whether backing up the
brick instead of the volume, which would be significantly
faster, would be a good idea: would the data be readable ok? Any
known side effect that could cause issues?</p>
<div class="gmail_quote">On 17 Aug 2015 10:12 am, "Avra Sengupta"
<<a moz-do-not-send="true" href="mailto:asengupt@redhat.com">asengupt@redhat.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi Thibault,<br>
<br>
Instead of backing up, individual bricks or the entire
thin logical volume, you can take a gluster volume
snapshot, and you will have a point in time backup of the
volume. <br>
<br>
gluster snapshots internally use thin lv snapshots, so you
can't move the backup out of the system. Also having the
backup on the same filesystem as the data doesn't protect
you from device failure scenarios. However in events of
any other data loss or corruption, you can restore the
volume from the snapshot, mount the read-only snapshot and
copy the necessary files. <br>
<br>
In order to take backup at a remore site, using geo-rep is
recommended.<br>
<br>
Regards,<br>
Avra<br>
<br>
On 08/17/2015 02:27 PM, Thibault Godouet wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">I have a 1 x 2 = 2 volume geo-replicated to a
single-brick volume in another physical site, where I
would like to set up a backup.</p>
<p dir="ltr">I could setup a backup on a mount of
the volume, but a quick test shows it is slow in this
setup (presumably because there are loads of small files
on there).</p>
<p dir="ltr">Instead I thought I could maybe backup the
filesystem where the brick is (or rather a snapshot of
the thin logical volume). My understanding is that all
the files will be in there, and readable, so it seems to
me it would be fine to back things up from there.</p>
<p dir="ltr">Is that right, or am I missing something
here?</p>
<p dir="ltr">Note the .glusterfs directory would also be
backed up too, although I'm not sure whether that would
be of any use in a backup.</p>
<p dir="ltr">More generally is there a recommended way to
setup backups?</p>
<p dir="ltr">Thanks,<br>
Thibault.</p>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Gluster-users mailing list
<a moz-do-not-send="true" href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<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></pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>