[Samba] about samba failover
mueller at tropenklinik.de
Mon Jun 30 02:51:08 MDT 2014
Quick and dirty
Setup up your 2 fileservers join them to samba. set up a floating ip running
Host the file shares on mount point with glusterfs replications.
EDV Daniel Müller
Tel.: 07071/206-463, Fax: 07071/206-499
eMail: mueller at tropenklinik.de
Von: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] Im
Auftrag von Davor Vusir
Gesendet: Sonntag, 29. Juni 2014 06:50
Cc: samba at lists.samba.org
Betreff: Re: [Samba] about samba failover
Den 28 jun 2014 23:42 skrev "steve" <steve at steve-ss.com>:
> On Sat, 2014-06-28 at 21:50 +0200, Davor Vusir wrote:
> > 2014-06-28 20:16 GMT+02:00 steve <steve at steve-ss.com>:
> > > On Sat, 2014-06-28 at 20:02 +0200, Davor Vusir wrote:
> > >
> > >>
> > >> Never the less, domain based DFS works. Thanks to Garming, if I
> > >> correctly.
> > >
> > > Hi
> > > That's exactly what we want. Two domain file servers carry the
> > > same share. One goes down, there's still another left with the same
> > >
> > > Can you point us at a howto?
> > > Thanks,
> > > Steve
> > >
> > >
> > Hi!
> > I haven't found a howto. If you can't Explore to
> > \\example.org\netlogon, I suggest you revert to Ubuntu 12.04 for
> > starters. :)
> Yes, but that's as far as it goes. We can only see the shares on the
> DC, but only netlogon and sysvol. If we create our own share, it does
> not show. Neither do any other shares on the dfs root we have set on
> our file server. We _always_ have to specify the file server, so
> domain dfs does not work.
Oh! Sorry, I didn't get that. I regard you as a seasoned sysadmin and you
would never make such a mistake. It has to be a typo in smb.conf after long
days trying to get DFS to work.
> > According to the documentation
> > (https://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/msdfs.h
> > tml
> > it is not possible in my opinion. At least not with automatic
> > failover. Because there is not enough information embedded in Sambas
> > implementation that informs the (Windows) client which server is to
> > prioritize and which is secondary and for how long this information
> > is valid. You can create links to several shares but you can't
> > determine which server the client will connect to (if it does not
> > connect alphabetacally(?)). If client A connects to server A the
> > first time, and client B connects to server B, you have to implement
> > two-way synchronization. There is no way to determine if the
> > opposite occurs at the next logon. The documentation fails to tell.
> > The only thing you know is that domainbased DFS is possible. The
> > availability solution is for you to decide.
> > I think it boils down to a solution with one (1) link to either a
> > cold stand-by server or a hot stand-by server(cluster) of some sort.
> > If you choose the cold stand-by solution, you'll have to 'relink' to
> > the stand-by server manually in case of server crash. Does rsync
> > copy open files? How often is enough? Every five minutes? Or is
> > inotify (
> > good enough?
> > If you choose the hot stand-by solution, I think DRBD will be
> > With the first solution you will loose data/information. The second
> > guaranties consistency.
> > The trick is one link to one server. High avaliability not included.
> > Regards
> > Davor
To unsubscribe from this list go to the following URL and read the
More information about the samba