is it possible to copy a brick from the disk to a new node for recovery?

[skvarovski]

Hello, I am studying this system and I have a question, I understand that this is not production use, but more of an amateur interest, if my disk from the host system breaks, can I copy all the contents of the brick for further use to a new disk of a new node, is this possible?

And if I have a week-old copy of /etc/gluster, is there a chance?

So far I see this solution for myself: connect the disk where the brick was located and copy its data through the client to the cluster

[skvarovski]

I am conducting a study in this case and this is what I have achieved:
if you have a copy of the brick and configuration files, then you can transfer it by creating a new instance of the node (in my case, it was an expandable disk space). Then, using the gluster volume status command, see that the node is offline, then give the gluster volume stop + gluster volume start command and make sure that this node has become online in the status. After that, the files will be available.

I continue to experiment with manual copying of configurations, the next step is to raise the node with a long interval of its absence.

[skvarovski]

Now I managed to create a situation when there is a node clone that contains a copy of the system with a small difference in time and files. This peer is considered online, volume status shows it in the list, volume info also displays it. But due to the lack of new files - it does not show its files in the volume distribution. How can I reindex this metadata so that they match the records of the other nodes?

[skvarovski]

If I restart the volume, my clone node will go online and work correctly.