Use checkpoint feature along with Snapshots at slave side to make sure
each days snapshot contains all the changes from that day.
When you set checkpoint, you can watch the status of checkpoint
completion using geo-rep status. Once checkpoint complete, it is
guaranteed that everything created before Checkpoint Time is synced to
slave.(Note: It only ensures that all the creates/updates done before
checkpoint time but Geo-rep may sync the files which are
created/modified after Checkpoint time)
Read more about Checkpoint here
http://gluster.readthedocs.io/en/latest/Administrator%20Guide/Geo%20Replication/#checkpoint
regards
Aravinda
On Monday 21 November 2016 01:36 PM, Gandalf Corvotempesta
wrote:>
> anyone?
>
>
> Il 19 nov 2016 10:36, "Gandalf Corvotempesta"
> <gandalf.corvotempesta at gmail.com
> <mailto:gandalf.corvotempesta at gmail.com>> ha scritto:
>
> Would be possible to setup a geo-replicated cluster to be used as
> backup?
> Obviously deleted files on master would be also deleted on the
> replicated, so this won't be feasable to be used as backup, BUT if
I
> schedule a snapshot every night (on the replicated node), I can use
> the snapshot as backup.
>
> I case of restore, I have to mount the snapshot e restore from there.
>
> Something like this, on the geo-replicated node:
>
> # gluster snapshot create backup_$(date +%Y%m%d_%H%M) gv0
>
> in a cronjob
>
> Any drawbacks ?
> Backing up a multi-terabyte or multi-petabyte would be impossible with
> standard rsnyc or any other backup tools.
>
>
>
> _______________________________________________
> 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/20161121/e58be61a/attachment.html>