[Gluster-devel] Decomission a brick

[Anand Avati]

2007/12/10, Steffen Grunewald <steffen.grunewald at aei.mpg.de>:
>
> On Sat, Dec 08, 2007 at 02:12:50AM +0000, DeeDee Park wrote:
> >
> > What is the procedure for removing a brick from operation without
> loosing any of the data while still
> > providing an operational file system for the other users?
>
> And just to jump in with a similar issue:
> What's the preferred way to backup a glusterfs brick, and even more
> important:
> how to restore it?
> My prospective use of glusterfs will be quasi-static storage of data which
> are hard to reproduce from other sources (mostly because of bandwidth
> reasons)
> so there's a need to keep a local backup (and since several n-TB volumes
> are
> involved, having only one overall backup might become tricky). OTOH there
> may be ways to fill a volume without glusterfs being aware of it - is
> there
> a way yet to tell glusterfs not to write to an individual volume?



Is snapshotting what you are looking for? it is possible to make unify not
to schedule files to a subvolume be marking them with 'option
read-only-subvolumes vol1 vol2' etc.

avati

-- 
If I traveled to the end of the rainbow
As Dame Fortune did intend,
Murphy would be there to tell me
The pot's at the other end.