Go to file
Andreas Schneider b22041fdd7 Package /var/lib/samba/ldb in the common-libs package
Since gensec also parses secrets.ldb all our tools like 'net' are
looking for this directory and print a warning if it doesn't exist.
2016-08-17 08:35:51 +02:00
.gitignore Update to Samba 4.5.0rc1 2016-07-28 15:42:11 +02:00
filter-requires-samba.sh
pam_winbind.conf
README.dc
README.downgrade
samba.log
samba.pamd
samba.spec Package /var/lib/samba/ldb in the common-libs package 2016-08-17 08:35:51 +02:00
samba.xinetd
smb.conf.example Small fix to the example smb.conf file 2016-06-20 09:41:05 +02:00
smb.conf.vendor
sources Update to Samba 4.5.0rc1 2016-07-28 15:42:11 +02:00

Downgrading Samba
=================

Short version: data-preserving downgrades between Samba versions are not supported

Long version:
With Samba development there are cases when on-disk database format evolves.
In general, Samba Team attempts to maintain forward compatibility and
automatically upgrade databases during runtime when requires.
However, when downgrade is required Samba will not perform downgrade to
existing databases. It may be impossible if new features that caused database
upgrade are in use. Thus, one needs to consider a downgrade procedure before
actually downgrading Samba setup.

Please always perform back up prior both upgrading and downgrading across major
version changes. Restoring database files is easiest and simplest way to get to
previously working setup.

Easiest way to downgrade is to remove all created databases and start from scratch.
This means losing all authentication and domain relationship data, as well as
user databases (in case of tdb storage), printers, registry settings, and winbindd
caches.

Remove databases in following locations:
/var/lib/samba/*.tdb
/var/lib/samba/private/*.tdb

In particular, registry settings are known to prevent running downgraded versions
(Samba 4 to Samba 3) as registry format has changed between Samba 3 and Samba 4.