Gluster users - Sep 2017 - Backup and Restore strategy in Gluster FS 3.8.4

> First, please note that gluster 3.8 is EOL and that 3.8.4 is rather old in
> the 3.8 release, 3.8.15 is the current (and probably final) release of 3.8.
>
> "With the release of GlusterFS-3.12, GlusterFS-3.8 (LTM) and
GlusterFS-
> 3.11 (STM) have reached EOL. Except for serious security issues no
> further updates to these versions are forthcoming. If you find a bug please
> see if you can reproduce it with 3.10 or 3.12 and
> file a BZ if appropriate."
> http://lists.gluster.org/pipermail/packaging/2017-August/000363.html
>
> Gluster 3.12 includes '#1428061
<https://bugzilla.redhat.com/1428061>:
> Halo Replication feature for AFR translator' which was introduced in
3.11.
> See Halo Replication feature in AFR has been introduced
> <https://gluster.readthedocs.io/en/latest/release-notes/3.11.0/> for
a
> summary. 3.11 is EOL, best to use 3.12 (long term release) if this is of
> interest to you.
>
> On Thu, Aug 24, 2017 at 4:18 AM, Sunil Aggarwal <sunchill.06 at
gmail.com>
> wrote:
>
>> Hi,
>>
>> What is the preferred way of taking glusterfs backup?
>>
>> I am using Glusterfs 3.8.4.
>>
>> We've configured gluster on thick provisioned LV in which 50% of
the VG
>> is kept free for the LVM snapshot.
>>
>
> Gluster Volume Snapshots require each brick to have it's own thin LV.
Only
> thin LVs are supported with volume snapshots.
>
> Gluster snapshots do not provide a recovery path in the event of
> catastrophic loss of a Gluster volume.
>
>  -  Gluster Volume Snapshots provide point-in-time recovery for a healthy
> Gluster Volume. A restore will reset the entire volume to a previous
> point-in-time recovery point. Granular recovery may be performed with admin
> intervention.
>  - User Serviceable Snapshots exposes Gluster Volume Snapshots via the
> .snaps directory in every directory of the mounted volume. Please review
> documentation for requirements specific to each protocol used to access the
> gluster volume.
>
>
>> is it any different then taking snapshot on a thin provisioned LV?
>>
>
> If you don't want Gluster Volume Snapshots, and are just looking to
backup
> the current state of a volume, Gluster offers a number of features to
> recover from catastrophic loss of a Gluster volume.
>
>  - Simple method: mount the gluster volume and run your backup utility of
> choice
>  - glusterfind generates a file list (full and incremental) for passing to
> another utility to generate a backup. See:
>   http://docs.gluster.org/en/latest/GlusterFS%20Tools/glusterfind/
>   https://milindchangireblog.wordpress.com/2016/10/28/why-glusterfind/
>   http://lists.gluster.org/pipermail/gluster-users/2017-August/032219.html
>  - Geo-replication provides a distributed, continuous, asynchronous, and
> incremental replication service from one site to another over Local Area
> Networks (LANs), Wide Area Networks (WANs), and the Internet. (taken from
> RedHat doc)
>
>
> Please see docs for additional info about each of the above:
> https://access.redhat.com/documentation/en-us/red_hat_
> gluster_storage/3.2/pdf/administration_guide/Red_Hat_Gluster_Storage-3.2-
> Administration_Guide-en-US.pdf
>
>
>>
>> --
>> Thanks,
>> Sunil Aggarwal
>> 844-734-5346 <%28844%29%20734-5346>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170920/ab6ac9d1/attachment.html>

Thanks a lot Ben for your suggestions. I will consider them and see how it
goes.

Regards,
Sunil

On Wed, Sep 20, 2017 at 11:15 PM, Ben Werthmann <ben at apcera.com> wrote:
>
> First, please note that gluster 3.8 is EOL and that 3.8.4 is rather old in
>> the 3.8 release, 3.8.15 is the current (and probably final) release of
3.8.
>>
>> "With the release of GlusterFS-3.12, GlusterFS-3.8 (LTM) and
GlusterFS-
>> 3.11 (STM) have reached EOL. Except for serious security issues no
>> further updates to these versions are forthcoming. If you find a bug
please
>> see if you can reproduce it with 3.10 or 3.12 and
>> file a BZ if appropriate."
>> http://lists.gluster.org/pipermail/packaging/2017-August/000363.html
>>
>> Gluster 3.12 includes '#1428061
<https://bugzilla.redhat.com/1428061>:
>> Halo Replication feature for AFR translator' which was introduced
in 3.11.
>> See Halo Replication feature in AFR has been introduced
>> <https://gluster.readthedocs.io/en/latest/release-notes/3.11.0/>
for a
>> summary. 3.11 is EOL, best to use 3.12 (long term release) if this is
of
>> interest to you.
>>
>> On Thu, Aug 24, 2017 at 4:18 AM, Sunil Aggarwal <sunchill.06 at
gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> What is the preferred way of taking glusterfs backup?
>>>
>>> I am using Glusterfs 3.8.4.
>>>
>>> We've configured gluster on thick provisioned LV in which 50%
of the VG
>>> is kept free for the LVM snapshot.
>>>
>>
>> Gluster Volume Snapshots require each brick to have it's own thin
LV.
>> Only thin LVs are supported with volume snapshots.
>>
>> Gluster snapshots do not provide a recovery path in the event of
>> catastrophic loss of a Gluster volume.
>>
>>  -  Gluster Volume Snapshots provide point-in-time recovery for a
healthy
>> Gluster Volume. A restore will reset the entire volume to a previous
>> point-in-time recovery point. Granular recovery may be performed with
admin
>> intervention.
>>  - User Serviceable Snapshots exposes Gluster Volume Snapshots via the
>> .snaps directory in every directory of the mounted volume. Please
review
>> documentation for requirements specific to each protocol used to access
the
>> gluster volume.
>>
>>
>>> is it any different then taking snapshot on a thin provisioned LV?
>>>
>>
>> If you don't want Gluster Volume Snapshots, and are just looking to
>> backup the current state of a volume, Gluster offers a number of
features
>> to recover from catastrophic loss of a Gluster volume.
>>
>>  - Simple method: mount the gluster volume and run your backup utility
of
>> choice
>>  - glusterfind generates a file list (full and incremental) for passing
>> to another utility to generate a backup. See:
>>   http://docs.gluster.org/en/latest/GlusterFS%20Tools/glusterfind/
>>   https://milindchangireblog.wordpress.com/2016/10/28/why-glusterfind/
>>   http://lists.gluster.org/pipermail/gluster-users/2017-August
>> /032219.html
>>  - Geo-replication provides a distributed, continuous, asynchronous,
and
>> incremental replication service from one site to another over Local
Area
>> Networks (LANs), Wide Area Networks (WANs), and the Internet. (taken
from
>> RedHat doc)
>>
>>
>> Please see docs for additional info about each of the above:
>> https://access.redhat.com/documentation/en-us/red_hat_gluste
>> r_storage/3.2/pdf/administration_guide/Red_Hat_Gluster_
>> Storage-3.2-Administration_Guide-en-US.pdf
>>
>>
>>>
>>> --
>>> Thanks,
>>> Sunil Aggarwal
>>> 844-734-5346 <%28844%29%20734-5346>
>>>
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org
>>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>>
>>
>>
>

-- 
Thanks,
Sunil Aggarwal
844-734-5346
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170921/d041441c/attachment.html>

Not so fast, 3.8.4 is the latest if you are using official RHEL rpms
from Red Hat Gluster Storage, so support for that should go through
your Red Hat subscription. If you are using the community packages,
then yes, you want to update to a more current version.

Seems like the latest is: 3.8.4-44.el7

Diego

On Wed, Sep 20, 2017 at 1:45 PM, Ben Werthmann <ben at apcera.com>
wrote:
>
>> First, please note that gluster 3.8 is EOL and that 3.8.4 is rather old
in
>> the 3.8 release, 3.8.15 is the current (and probably final) release of
3.8.
>>
>> "With the release of GlusterFS-3.12, GlusterFS-3.8 (LTM) and
>> GlusterFS-3.11 (STM) have reached EOL. Except for serious security
issues no
>> further updates to these versions are forthcoming. If you find a bug
please
>> see if you can reproduce it with 3.10 or 3.12 and
>> file a BZ if appropriate."
>> http://lists.gluster.org/pipermail/packaging/2017-August/000363.html
>>
>> Gluster 3.12 includes '#1428061: Halo Replication feature for AFR
>> translator' which was introduced in 3.11. See Halo Replication
feature in
>> AFR has been introduced for a summary. 3.11 is EOL, best to use 3.12
(long
>> term release) if this is of interest to you.
>>
>> On Thu, Aug 24, 2017 at 4:18 AM, Sunil Aggarwal <sunchill.06 at
gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> What is the preferred way of taking glusterfs backup?
>>>
>>> I am using Glusterfs 3.8.4.
>>>
>>> We've configured gluster on thick provisioned LV in which 50%
of the VG
>>> is kept free for the LVM snapshot.
>>
>>
>> Gluster Volume Snapshots require each brick to have it's own thin
LV. Only
>> thin LVs are supported with volume snapshots.
>>
>> Gluster snapshots do not provide a recovery path in the event of
>> catastrophic loss of a Gluster volume.
>>
>>  -  Gluster Volume Snapshots provide point-in-time recovery for a
healthy
>> Gluster Volume. A restore will reset the entire volume to a previous
>> point-in-time recovery point. Granular recovery may be performed with
admin
>> intervention.
>>  - User Serviceable Snapshots exposes Gluster Volume Snapshots via the
>> .snaps directory in every directory of the mounted volume. Please
review
>> documentation for requirements specific to each protocol used to access
the
>> gluster volume.
>>
>>>
>>> is it any different then taking snapshot on a thin provisioned LV?
>>
>>
>> If you don't want Gluster Volume Snapshots, and are just looking to
backup
>> the current state of a volume, Gluster offers a number of features to
>> recover from catastrophic loss of a Gluster volume.
>>
>>  - Simple method: mount the gluster volume and run your backup utility
of
>> choice
>>  - glusterfind generates a file list (full and incremental) for passing
to
>> another utility to generate a backup. See:
>>   http://docs.gluster.org/en/latest/GlusterFS%20Tools/glusterfind/
>>   https://milindchangireblog.wordpress.com/2016/10/28/why-glusterfind/
>>  
http://lists.gluster.org/pipermail/gluster-users/2017-August/032219.html
>>  - Geo-replication provides a distributed, continuous, asynchronous,
and
>> incremental replication service from one site to another over Local
Area
>> Networks (LANs), Wide Area Networks (WANs), and the Internet. (taken
from
>> RedHat doc)
>>
>>
>> Please see docs for additional info about each of the above:
>>
>>
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/pdf/administration_guide/Red_Hat_Gluster_Storage-3.2-Administration_Guide-en-US.pdf
>>
>>>
>>>
>>> --
>>> Thanks,
>>> Sunil Aggarwal
>>> 844-734-5346
>>>
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org
>>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users

Good point Diego. Thanks!

On Thu, Sep 21, 2017 at 9:49 AM, Diego Remolina <dijuremo at gmail.com>
wrote:
> Not so fast, 3.8.4 is the latest if you are using official RHEL rpms
> from Red Hat Gluster Storage, so support for that should go through
> your Red Hat subscription. If you are using the community packages,
> then yes, you want to update to a more current version.
>
> Seems like the latest is: 3.8.4-44.el7
>
> Diego
>
> On Wed, Sep 20, 2017 at 1:45 PM, Ben Werthmann <ben at apcera.com>
wrote:
> >
> >> First, please note that gluster 3.8 is EOL and that 3.8.4 is
rather old
> in
> >> the 3.8 release, 3.8.15 is the current (and probably final)
release of
> 3.8.
> >>
> >> "With the release of GlusterFS-3.12, GlusterFS-3.8 (LTM) and
> >> GlusterFS-3.11 (STM) have reached EOL. Except for serious security
> issues no
> >> further updates to these versions are forthcoming. If you find a
bug
> please
> >> see if you can reproduce it with 3.10 or 3.12 and
> >> file a BZ if appropriate."
> >>
http://lists.gluster.org/pipermail/packaging/2017-August/000363.html
> >>
> >> Gluster 3.12 includes '#1428061: Halo Replication feature for
AFR
> >> translator' which was introduced in 3.11. See Halo Replication
feature
> in
> >> AFR has been introduced for a summary. 3.11 is EOL, best to use
3.12
> (long
> >> term release) if this is of interest to you.
> >>
> >> On Thu, Aug 24, 2017 at 4:18 AM, Sunil Aggarwal <sunchill.06 at
gmail.com>
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> What is the preferred way of taking glusterfs backup?
> >>>
> >>> I am using Glusterfs 3.8.4.
> >>>
> >>> We've configured gluster on thick provisioned LV in which
50% of the VG
> >>> is kept free for the LVM snapshot.
> >>
> >>
> >> Gluster Volume Snapshots require each brick to have it's own
thin LV.
> Only
> >> thin LVs are supported with volume snapshots.
> >>
> >> Gluster snapshots do not provide a recovery path in the event of
> >> catastrophic loss of a Gluster volume.
> >>
> >>  -  Gluster Volume Snapshots provide point-in-time recovery for a
> healthy
> >> Gluster Volume. A restore will reset the entire volume to a
previous
> >> point-in-time recovery point. Granular recovery may be performed
with
> admin
> >> intervention.
> >>  - User Serviceable Snapshots exposes Gluster Volume Snapshots via
the
> >> .snaps directory in every directory of the mounted volume. Please
review
> >> documentation for requirements specific to each protocol used to
access
> the
> >> gluster volume.
> >>
> >>>
> >>> is it any different then taking snapshot on a thin provisioned
LV?
> >>
> >>
> >> If you don't want Gluster Volume Snapshots, and are just
looking to
> backup
> >> the current state of a volume, Gluster offers a number of features
to
> >> recover from catastrophic loss of a Gluster volume.
> >>
> >>  - Simple method: mount the gluster volume and run your backup
utility
> of
> >> choice
> >>  - glusterfind generates a file list (full and incremental) for
passing
> to
> >> another utility to generate a backup. See:
> >>   http://docs.gluster.org/en/latest/GlusterFS%20Tools/glusterfind/
> >>  
https://milindchangireblog.wordpress.com/2016/10/28/why-glusterfind/
> >>   http://lists.gluster.org/pipermail/gluster-users/2017-
> August/032219.html
> >>  - Geo-replication provides a distributed, continuous,
asynchronous, and
> >> incremental replication service from one site to another over
Local Area
> >> Networks (LANs), Wide Area Networks (WANs), and the Internet.
(taken
> from
> >> RedHat doc)
> >>
> >>
> >> Please see docs for additional info about each of the above:
> >>
> >> https://access.redhat.com/documentation/en-us/red_hat_
> gluster_storage/3.2/pdf/administration_guide/Red_Hat_Gluster_Storage-3.2-
> Administration_Guide-en-US.pdf
> >>
> >>>
> >>>
> >>> --
> >>> Thanks,
> >>> Sunil Aggarwal
> >>> 844-734-5346
> >>>
> >>> _______________________________________________
> >>> Gluster-users mailing list
> >>> Gluster-users at gluster.org
> >>> http://lists.gluster.org/mailman/listinfo/gluster-users
> >>
> >>
> >
> >
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170921/d679542e/attachment.html>