samba - Jan 2007 - concerns with moving from samba2 to samba3

Hi!

I am planning on moving a samba server from RedHat 8.0 to RedHat AS4(U4)

What I intend to do is put RHAS on a new machine and bring it up as if
it

were the old machine, after copying over the databases from the original


machine. I will keep the same IP address and hostname.

Note I do not use LDAP.

 

My only slight concern is that I am moving from samba version 2 to samba


version 3 so I am mailing this list in case some knows something that I

don't know and can warn me in advance. Here's some more details:

 

My current server runs samba-2.2.7-5.8.0 and the new server will run

3.0.10-1.4E.9.

On the new server I have run testparm on the smb.conf file I want to use

and it only gives a warning:

Unknown parameter encountered: "domain admin group"

Ignoring unknown parameter "domain admin group"

..so I reckon it's ok to use the current file.

 

I intend to .....

Stop the original service and copy over /etc/samba/ to the new server.

(This includes secrets.tdb. smb.conf and smbpasswd)

Shut down the original machine.

Bring up the new server with same hostname and IPaddress as original
server,

effectively the same machine but runningnew version of samba.

 

So my question is will this work? Or have I missed something?

Do I need to copy over the stuff in /var/cache/samba/? - some advice I
got

indicated that these would not matter as they would get created anyway, 

but it wouldn't do any harm if these could be understood by samba3
surely?

 

(Is there a command to interrogate these files so I could check in
advance

if samba3 could understand them?)

 

 

The other thing I would like to ask is does samba support a BDC? Can I
run

a PDC and if it goes down the BDC will take its place and have an

up-to-date copy of the databases?

 

Thanks in advance,

any help appreciated,

 

Ross

 

Ross Macintyre
School of Mathematical and Computer Sciences, Heriot-Watt University

Tel: 0131 451 3417
R.A.Macintyre@hw.ac.uk (raz@macs.hw.ac.uk)

Paintings at http://www.macs.hw.ac.uk/~raz/paintings/

Ross,

As I have executed this before, here's my story:

Create a complete and exact copy of what you HAVE on the new machine...
This includes /etc/samba/* /var/lib/samba/* etc...

Verify that the NEW machine does the same job as the OLD one...
Eg logon clients, shares etc...
Also check if the SIDS are still the same...
Oh and plz don't run these two server TOGETHER at the SAME TIME... ;)
Just a minor note *harharhar*

After you verified that the new server has properly replaced the old,
it's time to update the software...

We have simply used "rpm -Uvh *.rpm" in a directory with all the
updated rpm's together...
So, stop the services... execute the upgrade, and restart your services...

At my customer this went without a glitch (in the end)...
If anything failes, just try again...

OH... if you are running a domain controller with logon scripts...
things tend to get ugly if you don't follow procedures :D


So in your case, you are stuck with one minor detail... the new server
will not have the OLD samba installed...
This was not a problem in my case because I install Samba after installation...
Again... if it failes... try and try again :)

I hope this helps...
Cheers,
-- 
Rory Slegtenhorst
rory dot slegtenhorst at gmail dot com