File: upgrading-samba4.txt

package info (click to toggle)
samba 2:4.1.11+dfsg-1~bpo70+1
  • links: PTS, VCS
  • area: main
  • in suites: wheezy-backports
  • size: 102,616 kB
  • sloc: ansic: 1,163,067; xml: 114,289; python: 103,162; perl: 28,109; sh: 12,165; asm: 3,281; cpp: 2,281; yacc: 1,949; ada: 1,681; exp: 1,582; makefile: 1,181; pascal: 1,089; cs: 879; lex: 566; awk: 140; csh: 58; sed: 45
file content (28 lines) | stat: -rw-r--r-- 1,172 bytes parent folder | download | duplicates (5)
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
Upgrading from an older samba4 installation.

* Compile the new version of samba4 by following the HOWTO, but do
  not install it yet, and do not run provision.
* Stop any samba process
* Backup your samba4 provision:
  go into the directory where your samba4 provision is stored (/usr/local/samba by default)
  do tar cf $HOME/backup.tar private etc var sysvol
* do make install
* run 'samba-tool dbcheck'

This will do a consistency check of the data, and is all most existing
installations will require.

If you are upgrading from a quite old provision (Samba 4.0 alpha 13 or
earlier) then running upgradeprovision will do an upgrade of security
descriptors, and upgradeprovision --full will perform a more
comprehensive upgrade of the data (including schema and display
specifiers).  This attempts to do a new provision, and to then copy
existing data into that database.

If you are upgrading from a more recent version, particularly alpha16
or later, then it is better *NOT* to run upgradeprovision as the
database format has not changed.

To upgrade from BIND9 flat files to the internal database store for
Bind 9 DLZ, use ./source4/scripting/bin/samba_upgradedns