[Samba] Upgrading from 3.0.37 to 3.5.9
Gaiseric Vandal
gaiseric.vandal at gmail.com
Fri Jul 8 14:20:39 MDT 2011
I upgraded a while ago. I believe with samba 3.0.x from sun that the
executables are in /usr/sfw and that configuration and account info is
in /etc/samba. You will also have database files in /var/samba
You should run "testparm -v " to see the location of configuration files
and directories.
You MUST back these up!
I think 3.5.x will also look for smb.conf in /etc/samba by default.
You can explicitly define paths if need be. Once you upgrade you
should run "testparm -v" before starting samba to which which paths have
changed.
I don't believe you will have any issue with TDB files. I am using an
LDAP backend so the user accounts weren't in TDB anyway. Other
databases (e.g. idmap caches) were, If you do have problems you could
probably use the old pdbedit to export to text, and the new pdbedit to
import back to TDB.
You may need to explicitly define a local unix "nobody" account to map
as the guest account
e.g.
useradd .... smbnobody
vi smb.conf
.....
guest account = smb_nobody
...
There may have been changes on how password policies function (e.g
maximum password age etc.)
On 07/08/2011 03:30 PM, Stringer Kenneth M NGA-PRTN USA CTR wrote:
> I am upgrading from 3.0.37 to 3.5.9 on the same server and need some advice. I am running Solaris 10 on a domain server that services 10 XP and Win 7 clients. The existing Samba directory structure is not standard. I believe the engineer who built the Solaris install transferred all Samba 2.0 directories from the old server to the current server and then created additional directories for the install and symbolically linked some of the old files to the new install. Anyway, Samba is installed in two different structures on the server: Samba and /etc/samba... and /etc/sfw.... We are using the "sfw" directories:
>
>
>
> The smb.conf file in /etc/samba is symbolically linked to the smb.conf file in /etc/sfw. So here are my questions:
>
> 1) How do I migrate the tdbsam database from 3.0.37 to 3.5.9?
>
> 2) Can I use the existing smb.conf file?
>
> 3) Can I just backup smb.conf and tdbsam files and reinstall to all the default directories and then copy the backup files to the appropriate Samba directories?
>
> 4) What else do I need to migrate?
>
>
>
> I'm sure if I just do a ./configure like the Samba web site says, my whole team will be down until I get it fixed. There seems to be nothing in the documentation, which is very old, to help w/ this issue. Any input to point me in the right direction would be greatly appreciated.
>
>
>
> Thanks.
>
>
>
> Ken
>
>
>
More information about the samba
mailing list