Hi,
I've setup two server A + B (debian etch) with drbd + heartbeat in
active/passive mode. If the primary server A fails, the shared
storage is mounted on B, the virtual ip A-vip moves to the new primary
B and samba is started by heartbeat. This works well, but I'm not sure
which samba files should be identical on both server. Both have a
dedicated machine account at the moment.
primary: A, 192.168.0.50 (active)
secondary: B, 192.168.0.60 (passive)
cluster/failover: A-vip, 192.168.0.70 (dns name and ip that the
client use to access the
shares)
Should I just kick all samba files on B and sync them with the files
of the primary server A (maybe rsync or inotify, I don't use
drbdlinks....)?
I *think* this would be the necessary directories:
/etc/samba
/var/cache/samba
/var/lib/samba
/var/log/samba
/var/run/samba
/var/spool/samba
I've not set any host specific paramters in smb.conf, I use the
dns alias A-vip and the virtal-ip for the netbios alias and interface
settings.
BTW: the machine account was created for the hostname of the primary
server A, not the DNS alias A-vip, will this lead to a problem?
Ralf
Ralf Gross schrieb:> > I've setup two server A + B (debian etch) with drbd + heartbeat in > active/passive mode. If the primary server A fails, the shared > storage is mounted on B, the virtual ip A-vip moves to the new primary > B and samba is started by heartbeat. This works well, but I'm not sure > which samba files should be identical on both server. Both have a > dedicated machine account at the moment. > > primary: A, 192.168.0.50 (active) > secondary: B, 192.168.0.60 (passive) > cluster/failover: A-vip, 192.168.0.70 (dns name and ip that the > client use to access the > shares) > > Should I just kick all samba files on B and sync them with the files > of the primary server A (maybe rsync or inotify, I don't use > drbdlinks....)? > > I *think* this would be the necessary directories: > > /etc/samba > /var/cache/samba > /var/lib/samba > /var/log/samba > /var/run/samba > /var/spool/sambaOk, nobody is complaining, so guess it's the right way ;) Ralf
1. Use LDAP Backend
2. Follow this Guide
http://wiki.samba.org/index.php/Replicated_Failover_Domain_Controller_and_file_server_using_LDAP
The link may be broken, you may have to copy and paste.
:)
Adrian Sender.
-----------------------------------------------------------------------------
From: Ralf Gross <Ralf-Lists@ralfgross.de>
To: samba@lists.samba.org
Subject: [Samba] samba and failover (drbd + heartbeat)
Sent: Tuesday, 15 May 2007 10:20:50 PM
Hi,
I've setup two server A + B (debian etch) with drbd + heartbeat in
active/passive mode. If the primary server A fails, the shared
storage is mounted on B, the virtual ip A-vip moves to the new primary
B and samba is started by heartbeat. This works well, but I'm not sure
which samba files should be identical on both server. Both have a
dedicated machine account at the moment.
primary: A, 192.168.0.50 (active)
secondary: B, 192.168.0.60 (passive)
cluster/failover: A-vip, 192.168.0.70 (dns name and ip that the
client use to access the
shares)
Should I just kick all samba files on B and sync them with the files
of the primary server A (maybe rsync or inotify, I don't use
drbdlinks....)?
I *think* this would be the necessary directories:
/etc/samba
/var/cache/samba
/var/lib/samba
/var/log/samba
/var/run/samba
/var/spool/samba
I've not set any host specific paramters in smb.conf, I use the
dns alias A-vip and the virtal-ip for the netbios alias and interface
settings.
BTW: the machine account was created for the hostname of the primary
server A, not the DNS alias A-vip, will this lead to a problem?
Ralf
_________________________________________________________________
Advertisement: Meet Sexy Singles today at Lavalife - Click here
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D27783&_t=762255081&_r=lavalife_may07_meetsexysingles&_m=EXT