Samba in a high availablity enviroment
mathewmckernan at optushome.com.au
Tue Mar 30 14:33:30 GMT 2004
I had to configure a similar thing at my workplace.
I found netbios name was more useful, as we never had samba running on
both servers at once. We stored the private, var and lib directories on
the RAID and made sure samba was compiled with the correct paths
pointing at the RAID mount point. With that done, we had many successful
failovers (nearly all of them forced by me for testing). One day it
swapped over and no one noticed, we only knew as an email was sent by
the linux-ha software to the engineer's email account.
samba-technical-bounces+mathewmckernan=optushome.com.au at lists.samba.org
[mailto:samba-technical-bounces+mathewmckernan=optushome.com.au at lists.sa
mba.org] On Behalf Of daniel.jarboe at custserv.com
Sent: Tuesday, 30 March 2004 23:55
To: Volker.Lendecke at SerNet.DE; per at sgi.com
Cc: samba-technical at lists.samba.org
Subject: RE: Samba in a high availablity enviroment
On Monday, March 29, 2004 10:22 AM, Volker Lendecke wrote:
> On Mon, Mar 29, 2004 at 03:17:24PM +0200, Per Kofod wrote:
> > My guess is that this information is kept in one of the files under
> > $SAMBA/var/locks directory; but which one, and can the other node
> > over this file without any complications?
> It's in secrets.tdb. The easiest way is to have both servers with
> different 'netbios name' entries but with a common 'netbios aliases'.
> determines the workstation account name, and the common 'netbios
> the additional one that is announced to clients. This way no
> domain membership needs to be shared.
I've been having a lot of trouble getting something similar working
correctly. If have two servers always up, each with a single interface
always on, and a third IP address that can be toggled between them on an
additional interface (in dns the third ip is gutenberg). When a client
installs a printer via the gutenberg print$ share, the printer is often
installed as PRINTER-NAME on printserv1, instead of PRINTER-NAME on
I've tried it with and without netbios aliases. Sometimes we will get
the correct behavior if the client deletes the printer, restarts
Windows, and then adds the printer again, but it tends to be wrong more
often than right.
We'd like to be able to switch clients from one server to the other
without having to touch every single client. Am I doing something
wrong, missing some important step?
This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
More information about the samba-technical