samba - Dec 2001 - Upgrade Samba PDC from 2.2.0 -> 2.2.2

Hi!

I already posted this question to the samba-ntdom list
a few days ago, but haven't got a single answer so far :-(
Learning that the ntdom list will be shut down shortly, I 
figured that this list is a more appropriate place to 
ask. Isn't it?

So, this is the challenge:

We have samba 2.2.0 running as PDC for a domain with about
30 NT workstations (up to SP6). We are using server-based 
profiles, and also some printer drivers are stored on the server.
There are about 40 disk shares and 10 printer shares defined.
The server stores about 60GB of data and is heavily in use
during working hours.
I would say it's a typical fileserver in a typical office
environment, and it's working really fine!

We now want to upgrade this server to samba-2.2.2, because
of new W2KSP2 workstations which should join the domain in the
near future. The upgrade is scheduled for next week, because
between Christmas and New Year the office is almost empty,
and other services are shut down due to Euro conversion... :-)

My question is: now that samba uses a lot of database files
which are not easily human-readable ("/var/lock/samba/*.tdb"
with samba-2.2.0, "/var/cache/samba/*.tdb" with samba-2.2.2),
and also some files in /etc/samba/ ("secrets.tdb",
"MACHINE.SID"),
what are the files to save during the update? What files can
be deleted, what files must not be deleted?
Can I just copy all the files from "/var/lock/samba/" to
"/var/cache/samba/"?

It is absolutely essential that after the update all people
on all workstations can work in the domain just as before!
A complete (or even partial) re-install of the NT workstations 
is not an option!

Is there a "samba-upgrade-HOWTO" somewhere? Does anyone
out there have any experience with such an update on a
samba PDC server in production use? Any tips & tricks?

Any help would be appreciated!

If I survive this challenge I'm quite willing to report all
experiences to the list... :-)

Thanks in advance! 

- andreas

-- 
Andreas Haumer                     | mailto:andreas@xss.co.at
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71

On Sat, 22 Dec 2001, Andreas Haumer wrote:
> My question is: now that samba uses a lot of database files
> which are not easily human-readable ("/var/lock/samba/*.tdb"
> with samba-2.2.0, "/var/cache/samba/*.tdb" with samba-2.2.2),
> and also some files in /etc/samba/ ("secrets.tdb",
"MACHINE.SID"),
> what are the files to save during the update? What files can
> be deleted, what files must not be deleted?
> Can I just copy all the files from "/var/lock/samba/" to
> "/var/cache/samba/"?
For smbd (as a PDC) you need to save

	nt*.tdb
	share_info.tdb (if you have changed and default share ACLs)
	secrets.tdb (contains domain SID)
	smb.conf (include smbpasswd and any username map file)

Winbind did not exist in 2.2.0 but for future reference,
you should also save all of winbind's idmap.tdb files.


I would recommend tarring up the entire /usr/local/samba/
directory prior to the upgrade (good practice IMO).
> Is there a "samba-upgrade-HOWTO" somewhere? Does anyone
> out there have any experience with such an update on a
> samba PDC server in production use? Any tips & tricks?
I should go smoothly I would expect.  If something fails, you
be able to back out the upgrade as well.









chau, jerry
 ---------------------------------------------------------------------
 Hewlett-Packard                                     http://www.hp.com
 SAMBA Team                                       http://www.samba.org
 --                                            http://www.plainjoe.org
 "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN
0-672-32269-2
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--