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