blob: a4d5097cd940f64a0f8d7e00d9347999efc7b8a0 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
|
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
<chapter id="upgrades">
<title>Updating Samba-3</title>
<para>
It was a little difficult to select an appropriate title for this chapter.
From email messages on the Samba mailing lists it is clear that many people
consider the updating and upgrading of Samba to be a migration matter. Others
talk about migrating Samba servers when in fact the issue at hand is one of
installing a new Samba server to replace an older existing Samba server.
</para>
<para>
There has also been much talk about migration of Samba-3 from an smbpasswd
passdb backend to the use of the tdbsam or ldapsam facilities that are new
to Samba-3.
</para>
<para>
Clearly, there is not a great deal of clarity in the terminology that various
people apply to these modes by which Samba servers are updated. This is further
highlighted by an email posting that included the following neat remark:
</para>
<blockquote><para>
I like the <quote>net rpc vampire</quote> on NT4, but that to my surpirse does
not seem to work against a Samba PDC and, if addressed in the Samba to Samba
context in either book, I could not find it.
</para></blockquote>
<para>
So in response to the significant request for these situations to be better
documented this chapter has now been added. Your contributions and documentation
of real-world experiences will be a most welcome addition to this chapter.
</para>
<sect1>
<title>Introduction</title>
<para>
A Windows network administrator explained in an email what changes he was
planning to make and and followed with the question: <quote>Anyone done this before?</quote>.
Many of us have upgraded and updated Samba without incident. Others have
experienced much pain and user frustration. So it is to be hoped that the
notes in this chapter will make a positive difference by assuring that
someone will be saved a lot of discomfort.
</para>
<para>
Before anyone commences an upgrade or an update of Samba the one cardinal
rule that must be observed is: Backup all Samba configuration files in
case it is necessary to revert to the old version. Even if you do not like
this precautionary step, users will punish an administrator who
fails to take adequate steps to avoid situations that may inflict lost
productivity on a user.
</para>
<para>
It is prudent also to backup all data files on the server before attempting
to perform a major upgrade. Many administrators have experienced the consequences
of failure to take adequate precautions. So what is adequate? That is simple!
If data is lost during an upgrade or and update and it can not be restored
the precautions take were inadequate. If a backup was not needed, but was available,
precaution was on the side of the victor.
</para>
</sect1>
<sect1>
<title>Upgrading from Samba-2 to Samba-3</title>
<para>
Sites that are being upgraded from Samba-2 (or earlier versions) to Samba-3
may experience little difficulty or may require a lot of effort, depending
on the complexity of the configuration. Samba-1.9.x upgrades to Samba-3 will
generally be simple and straight forward, although no upgrade should be
attempted without proper planning and preparation.
</para>
<para>
There are two basic modes of use of Samba versions prior to Samba-3. The first
does not use LDAP, the other does. Samba-1.9.x did not provide LDAP support.
Samba-2.x could be compiled with LDAP support.
</para>
<sect2>
<title>Samba 1.9.x and 2.x Versions Without LDAP</title>
<para>
JJJ Pick up from here JJJ.
</para>
</sect2>
<sect2>
<title>Samba-2.x with LDAP support</title>
<para>
</para>
</sect2>
</sect1>
<sect1>
<title>Updating a Samba-3 Installation</title>
<para>
</para>
<sect2>
<title>Updating from Versions Earlier than 3.0.6</title>
<para>
</para>
</sect2>
<sect2>
<title>Updating from Versions between 3.0.7 and 3.0.10</title>
<para>
</para>
</sect2>
<sect2>
<title>Migrating Samba-3 to a New Server</title>
<para>
</para>
</sect2>
<sect2>
<title>Cautions and Notes</title>
<sect3>
<title>Change of hostname</title>
<para>
</para>
</sect3>
<sect3>
<title>Change of workgroup (domain) name</title>
<para>
</para>
</sect3>
<sect3>
<title>Location of config files</title>
<para>
The Samba 1.9.x &smb.conf; file may be found either in the <filename>/etc</filename>
directory or in <filename>/usr/local/samba/lib</filename>.
</para>
<para>
During the life of the Samba 2.x release the &smb.conf; file was relocated
on Linux systems to the <filename>/etc/samba</filename> directory where it
remains located also for Samba 3.0.x installations.
</para>
<para>
Samba 2.x introduced the secrets.tdb file that is also stored in the
<filename>/etc/samba</filename> directory, or in the <filename>/usr/local/samba/lib</filename>
directory sub-system.
</para>
<para>
It is important that both the &smb.conf; file and the <filename>secrets.tdb</filename> should
be backed up before attempting any upgrade. The <filename>secrets.tdb</filename> file is version
encoded and therefore a newer version may not work with an older version of Samba. A backup
means that it is always possible to revert a failed or problematic upgrade.
</para>
</sect3>
</sect2>
</sect1>
</chapter>
|
