|
 |
f6791b2 |
Downgrading Samba
|
|
|
f6791b2 |
=================
|
|
|
f6791b2 |
|
|
|
f6791b2 |
Short version: data-preserving downgrades between Samba versions are not supported
|
|
|
f6791b2 |
|
|
|
f6791b2 |
Long version:
|
|
|
f6791b2 |
With Samba development there are cases when on-disk database format evolves.
|
|
|
f6791b2 |
In general, Samba Team attempts to maintain forward compatibility and
|
|
|
f6791b2 |
automatically upgrade databases during runtime when requires.
|
|
|
f6791b2 |
However, when downgrade is required Samba will not perform downgrade to
|
|
|
f6791b2 |
existing databases. It may be impossible if new features that caused database
|
|
|
f6791b2 |
upgrade are in use. Thus, one needs to consider a downgrade procedure before
|
|
|
f6791b2 |
actually downgrading Samba setup.
|
|
|
f6791b2 |
|
|
|
f6791b2 |
Please always perform back up prior both upgrading and downgrading across major
|
|
|
f6791b2 |
version changes. Restoring database files is easiest and simplest way to get to
|
|
|
f6791b2 |
previously working setup.
|
|
|
f6791b2 |
|
|
|
f6791b2 |
Easiest way to downgrade is to remove all created databases and start from scratch.
|
|
|
f6791b2 |
This means losing all authentication and domain relationship data, as well as
|
|
|
f6791b2 |
user databases (in case of tdb storage), printers, registry settings, and winbindd
|
|
|
f6791b2 |
caches.
|
|
|
f6791b2 |
|
|
|
f6791b2 |
Remove databases in following locations:
|
|
|
f6791b2 |
/var/lib/samba/*.tdb
|
|
|
f6791b2 |
/var/lib/samba/private/*.tdb
|
|
|
f6791b2 |
|
|
|
f6791b2 |
In particular, registry settings are known to prevent running downgraded versions
|
|
|
f6791b2 |
(Samba 4 to Samba 3) as registry format has changed between Samba 3 and Samba 4.
|