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