s4-provision: set 'dcerpc endpoint servers' but not 'vfs objects'

[nivanova/samba-autobuild/.git] / upgrading-samba4.txt

diff --git a/upgrading-samba4.txt b/upgrading-samba4.txt
index 9dc4636296138754cf0cb78147a5fdaa38f6941f..8c74f5aae5840b34526214ef4d1b5306fc3a52c6 100644 (file)
--- a/upgrading-samba4.txt
+++ b/upgrading-samba4.txt
@@ -6,13 +6,23 @@ Upgrading from an older samba4 installation.
 * 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
-* Go into the source4 dir
-* run ./scripting/bin/upgradeprovision -s <path to smb.conf in samba4 install>
 * do make install
+* run 'samba-tool dbcheck'
 
-This will do the minimum (safest) upgrade of the data.  
+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
 
-Runing upgradeprovision with --full will do 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.