[Gluster-users] Replacing brick in replicated volume without reducing redundancy?

[Stefan]

Hi, 

I am looking to replace a brick in a replicated volume with arbiter (2+1 bricks). 
Judging from this page: [ https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-brick | https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-brick ] 
it seems that the procedure is: simulate a brick failure, then add a replacement brick. 

Is that the only way to do it? Isn't there a way to migrate the data on the fly without running on reduced redundancy during the migration, like pvmove exists for LVM? 

Thanks, 

Stefan 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200107/11dd5f8b/attachment.html>