I currently plan to move my storage to Gluster. One of the anticipated advantages is to have Gluster replicate data among physical nodes, i.e. if one node dies the file service can live on. AD for authentication also replicates nice on distinct physical nodes. So the remaining single point of failure is the samba file service. Is there something more intelligent than: if not \\severA\share -> try: \\serverB\share? Regards, -lars.
On 2015-02-02 12:56, Lars Hanke wrote:> I currently plan to move my storage to Gluster. One of the anticipated > advantages is to have Gluster replicate data among physical nodes, i.e. > if one node dies the file service can live on. > > AD for authentication also replicates nice on distinct physical nodes. > > So the remaining single point of failure is the samba file service. Is > there something more intelligent than: > > if not \\severA\share -> try: \\serverB\share?Use a common domain name for both servers (what AD does internally for authentication), or use IP-based failover via Samba's CTDB. -- Mit freundlichen Gr??en, / Best Regards, Sven Schwedas Systemadministrator TAO Beratungs- und Management GmbH | Lendplatz 45 | A - 8020 Graz Mail/XMPP: sven.schwedas at tao.at | +43 (0)680 301 7167 http://software.tao.at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 648 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20150202/59c60a14/attachment.pgp>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 02.02.2015 um 13:30 schrieb Sven Schwedas:> On 2015-02-02 12:56, Lars Hanke wrote: >> I currently plan to move my storage to Gluster. One of the >> anticipated advantages is to have Gluster replicate data among >> physical nodes, i.e. if one node dies the file service can live >> on. >> >> AD for authentication also replicates nice on distinct physical >> nodes. >> >> So the remaining single point of failure is the samba file >> service. Is there something more intelligent than: >> >> if not \\severA\share -> try: \\serverB\share? > > Use a common domain name for both servers (what AD does internally > for authentication), or use IP-based failover via Samba's CTDB.For Member Servers, you can use a clustred Samba installation with CTDB. But you can't on Samba AD DCs, because it's not compatible with CTDB. Regards, Marc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUz6OlAAoJEFNERvHO3m51hPMH/iCuKsSyJrIqEJV9F+jBBPEe 3kqRmYPEbO/wpMF2T3B3fps7OiQOElasudHLxj6Af83/RtcxUyv7J7uX2BBheY1g Bjh+dD68nhN/na04E2cm98+JPND7a2ZhE1JkL7Bj8PRow3hTfrR6ponNI3Hnbk+i mCQxYoUASPbZjdzFCqW4gJ21zFMVhy/5trUkqYLv8koXvDdDiHDhmZ/Ly2U+p2qe Y2nxeNlgg4Vrod+GfByczXnGenH3OaXAYxaZDCwHoO5UuAZsIVzzgUXi7ccOhjQn MnZoBF/BF7/Hfmlif3OKQw8sFP8xHoOPvO0HQj0vifzbN83suw4vUdZpWV7TBLA=qAUS -----END PGP SIGNATURE-----