<div dir="auto">If you are referring single head server as the samba node, then have samba deployed on other server nodes and create a samba cluster using ctdb. <div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Poornima</div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Feb 9, 2019, 8:31 PM Jim Laib <<a href="mailto:jlaib01@gmail.com">jlaib01@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I'm using a single server (gluster client) to mount a gluster replicated gluster cvolume using two servers. so the single server is acting as the head to the gluster volume. My users access the cluster client head using Samba. What I'm wondering is. what's the best way to insure continuity if my single head server takes a nap?</div><div>And yes, I agree 3 is better and I plan to move down that path when I reconfigure my system.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 8, 2019 at 12:51 PM Nico van Royen <<a href="mailto:nico@van-royen.nl" target="_blank" rel="noreferrer">nico@van-royen.nl</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
What do you mean by a gluster 'client server' ?<br>
A node is either a server (running the glusterd and glusterfsd/brick processes), and you'd need at least 2 (3 is better, and the volume to be set as a replica-3) or a gluster client (uses the gluster-client to mount a volume from a gluster-cluster).<br>
You could of-course also run the 'client' on the actual gluster-server to mount to itself (wouldn't recommend that).<br>
<br>
Nico<br>
<br>
----- Oorspronkelijk bericht -----<br>
Van: "Jim Laib" <<a href="mailto:jlaib01@gmail.com" target="_blank" rel="noreferrer">jlaib01@gmail.com</a>><br>
Aan: "gluster-users" <<a href="mailto:gluster-users@gluster.org" target="_blank" rel="noreferrer">gluster-users@gluster.org</a>><br>
Verzonden: Vrijdag 8 februari 2019 17:04:45<br>
Onderwerp: [Gluster-users] Client failover question<br>
<br>
I may have missed this in the documentation, but is there a way to make a Gluster client server redundant? I have several bricks setup being controlled by one cluster client server and if that server blows, there's quite a bit of rebuilding to do. So looking for a way to ovoid that. Any suggestions would be most appreciated. <br>
<br>
Thanks in advance. <br>
<br>
_______________________________________________ <br>
Gluster-users mailing list <br>
<a href="mailto:Gluster-users@gluster.org" target="_blank" rel="noreferrer">Gluster-users@gluster.org</a> <br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a> <br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank" rel="noreferrer">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank" rel="noreferrer">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>