[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gluster-users
Subject:    Re: [Gluster-users] change OS on one node
From:       Strahil Nikolov <hunter86_bg () yahoo ! com>
Date:       2023-01-30 11:26:55
Message-ID: 1988146407.741329.1675078015896 () mail ! yahoo ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I've done something similar when upgrading from EL7 to EL8.Backup /var/lib/glusterd/ \
& /etc/glusterfs/ (if needed upgrade to a gluster version that exists in both OSes) \
and once you install the system, install the same gluster package version and restore \
the 2 dirs from backup. Of course , a proper backup is always a good idea.
Best Regards,Strahil Nikolov  
 
 
  On Mon, Jan 30, 2023 at 11:33, Stefan Kania<stefan@kania-online.de> wrote:   Hi to \
all,


I would like to replace the operating system on one gluster brick. Is it 
possible to hold the data on the brick? If yes, how can I connect the 
data partition back to the new brick.

I will remove the brick from the volume and remove the peer from the 
pool first. Then setup the new OS then I would like to configure the new 
brick and bind the exixting partion to the new brick.

Or is it better to format the brick and rereplicat the data? We only 
have 500GB of data.


________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
  


[Attachment #5 (text/html)]

I've done something similar when upgrading from EL7 to EL8.<div>Backup \
/var/lib/glusterd/ &amp; /etc/glusterfs/ (if needed upgrade to a gluster version that \
exists in both OSes) and once you install the system, install the same gluster \
package version and restore the 2 dirs from backup.<div><div><br></div><div>Of course \
, a proper backup is always a good idea.</div><div><br></div><div>Best \
Regards,</div><div>Strahil Nikolov&nbsp;<br><div> <br> <blockquote style="margin: 0 0 \
20px 0;"> <div style="font-family:Roboto, sans-serif; color:#6D00F6;"> <div>On Mon, \
Jan 30, 2023 at 11:33, Stefan Kania</div><div>&lt;stefan@kania-online.de&gt; \
wrote:</div> </div> <div style="padding: 10px 0 0 20px; margin: 10px 0 0 0; \
border-left: 1px solid #6D00F6;"> <div dir="ltr">Hi to all,<br></div><div \
dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">I would like to replace \
the operating system on one gluster brick. Is it <br></div><div dir="ltr">possible to \
hold the data on the brick? If yes, how can I connect the <br></div><div \
dir="ltr">data partition back to the new brick.<br></div><div \
dir="ltr"><br></div><div dir="ltr">I will remove the brick from the volume and remove \
the peer from the <br></div><div dir="ltr">pool first. Then setup the new OS then I \
would like to configure the new <br></div><div dir="ltr">brick and bind the exixting \
partion to the new brick.<br></div><div dir="ltr"><br></div><div dir="ltr">Or is it \
better to format the brick and rereplicat the data? We only <br></div><div \
dir="ltr">have 500GB of data.<br></div><div dir="ltr"><br></div><div \
dir="ltr"><br></div>________<br><br><br><br>Community Meeting \
Calendar:<br><br>Schedule -<br>Every 2nd and 4th Tuesday at 14:30 IST / 09:00 \
UTC<br>Bridge: <a href="https://meet.google.com/cpu-eiue-hvk" \
target="_blank">https://meet.google.com/cpu-eiue-hvk</a><br>Gluster-users mailing \
list<br><a ymailto="mailto:Gluster-users@gluster.org" \
href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br><a \
href="https://lists.gluster.org/mailman/listinfo/gluster-users" \
target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br> \
</div> </blockquote></div></div></div></div>



________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users


[prev in list] [next in list] [prev in thread] [next in thread]