[mdlug] Samba and F5 for Failover?

[Robert Adkins]

> -----Original Message-----
> From: mdlug-bounces at mdlug.org 
> [mailto:mdlug-bounces at mdlug.org] On Behalf Of Michael ORourke
> Sent: Thursday, October 08, 2009 1:13 PM
> To: MDLUG's Main discussion list
> Subject: Re: [mdlug] Samba and F5 for Failover?
> 
> ----- Original Message -----
> From: "Robert Adkins" <radkins at impelind.com>
> To: "'MDLUG's Main discussion list'" <mdlug at mdlug.org>
> Sent: Wednesday, October 07, 2009 10:41 AM
> Subject: Re: [mdlug] Samba and F5 for Failover?
> 
> 
> >
> >  This should work perfectly fine, since using the exact 
> same configuration
> > files on both servers will appear to be no different to the 
> workstations, 
> > as
> > the SIDS will be the same. I love this about Samba as it 
> has allowed me to
> > shift the entire domain from one server to another a good 
> half a dozen 
> > times
> > without me having to run around and manually reboot or 
> rejoin workstations
> > to the "new" domain server. (Of course, I don't perform 
> such changeovers
> > during normal business hours, unless I am in a bind.)
> >
> 
> Doh!  I wish I had talked to you about this exact scenario a 
> week ago, as I 
> had run into some problems migrating XP Pro clients from an 
> old Samba server 
> running as a PDC to a new Samba server.  Just out of 
> curiousity, did you 
> setup the new server as a BDC, then promote it to a PDC?  Or 
> just copy the 
> config from the old to the new server, then turn off Samba on 
> the old server 
> and turn in on for the new server?
> 
> -Mike
> 

	I did the latter. (Copy configs over, shutdown old, start up new.)

	Remember, Windows wants to hurt you. Linux wants to help you.

	So, anytime you want to do something like replace a running system,
Windows will work to thwart you, while Linux will work to help you.

	Two days ago, I had to replace the motherboard in our email server.
All I did was shut it down, put the RAM and CPU into the new board and
booted it up. I just had to configure X and the new LAN cards and tell a few
services that they needed to use eth2 now and everything just worked. It
took less than an hour to get the whole job done. With Windows, at a
minimum, I would have had to run a recovery installation and then rerun all
the patches and then double check all the configurations. (It would have
hurt.)

	-Rob