[Gluster-users] substitution of two faulty servers

[Atin Mukherjee]

On Fri, 9 Jun 2017 at 21:53, Erekle Magradze <erekle.magradze at recogizer.de>
wrote:

> thanks for reply, but the problem is the number of replications, I have
> replication factor 3 so what would be the best way to substitute 2 bricks?
> as I understood properly first I need to add the server to gluster as a
> node, afterwards I need to add bricks to the volume (but if the number of
> bricks is not a factor of 3 it is not possible),
>

Have you referred
http://gluster.readthedocs.io/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-brick
?

First you'd need to add the server and then you can replace one brick at a
time irrespective of the replica count.


> or, if there is other way please drop me a hint or link
> On 06/09/2017 05:44 PM, Atin Mukherjee wrote:
>
> Go for replace brick.
>
> On Fri, 9 Jun 2017 at 19:29, Erekle Magradze <erekle.magradze at recogizer.de>
> wrote:
>
>> Hello,
>>
>> I have glusterfs 3.8.9, integrated with oVirt.
>>
>> glusterfs is running on 6 servers, I have one brick from each server for
>> oVirt virtdata volume (used for VM images)
>>
>> and 2 bricks from each servers (12 bricks in total) for data volume,
>> which is used as a file storage (with different sizes).
>>
>> I would like to substitute 2 servers with new ones, due to the hardware
>> reorganization.
>>
>> So for virtdata volume I need to substitute 2 bricks with the 2 bricks
>> from the new servers and for data volume I need to substitute 4 bricks
>> (2 bricks from each server) with 4 bricks from new servers.
>>
>> In both volumes I have distributed replicated setup.
>>
>> What would be the most recommended strategy for substitution operation?
>>
>> Many thanks in advance.
>>
>> Cheers
>>
>> Erekle
>>
>>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
> --
> - Atin (atinm)
>
>
> --
> Recogizer Group GmbH
>
> Erekle Magradze
> Lead Big Data Engineering & DevOps
> Rheinwerkallee 2, 53227 Bonn
> Tel: +49 228 29974555
>
> E-Mail erekle.magradze at recogizer.de
> Web: www.recogizer.com
>
> Recogizer auf LinkedIn https://www.linkedin.com/company-beta/10039182/
> Folgen Sie uns auf Twitter https://twitter.com/recogizer
>
> -----------------------------------------------------------------
> Recogizer Group GmbH
> Geschäftsführer: Oliver Habisch, Carsten Kreutze
> Handelsregister: Amtsgericht Bonn HRB 20724
> Sitz der Gesellschaft: Bonn; USt-ID-Nr.: DE294195993
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
> informieren Sie bitte sofort den Absender und löschen Sie diese Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail und der darin enthaltenen Informationen ist nicht gestattet.
>
> --
- Atin (atinm)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170610/8d151bd0/attachment.html>