Hello to all, I currently have a samba server with the following specs : - Samba 4.1.7 , compiled install from source code (samba wiki guided) - CentOS 6.5 x86_64 (VM) - AD DC + print server / CUPS - Internal DNS server I'm considering an upgrade to the last stable release 4.4.2. Since this server is in production with 400 users , 500 computers (XP, 7 Pro, OSX) , NAS members (Synology) , and 15 printers, I can't take any risks about this upgrade. - Is there any point I have to take care about before this upgrade ? I read some problems about RDP authentication in previous releases , is it solved in 4.4 ? Performance issues ? - Is the process : ./configure ; make ; samba stop ; make install ; samba start , the way to proceed ? - Is there any data to backup before ? (I plan to backup the entire VM anyway) - From the client point of view, in case of 4.4 dysfunction is it possible to go back to 4.1.7 seamlessly by restarting the 4.1.7 VM (I'd like to avoid to rejoin 500 PCs ...) ? Any advise welcome . Thanks in advance Henri
Hi, Isn't it possible to add another DC to your environment? Doing that you get another instance of your database then you could upgrade your DC with very less risk... 2016-04-19 10:40 GMT+02:00 henri transfert <hb.transfert at gmail.com>:> Hello to all, > > I currently have a samba server with the following specs : > > - Samba 4.1.7 , compiled install from source code (samba wiki guided) > - CentOS 6.5 x86_64 (VM) > - AD DC + print server / CUPS > - Internal DNS server > > I'm considering an upgrade to the last stable release 4.4.2. > > Since this server is in production with 400 users , 500 computers (XP, 7 > Pro, OSX) , NAS members (Synology) , and 15 printers, I can't take any > risks about this upgrade. > > - Is there any point I have to take care about before this upgrade ? I read > some problems about RDP authentication in previous releases , is it solved > in 4.4 ? Performance issues ? > > - Is the process : ./configure ; make ; samba stop ; make install ; samba > start , the way to proceed ? > > - Is there any data to backup before ? (I plan to backup the entire VM > anyway) > > - From the client point of view, in case of 4.4 dysfunction is it possible > to go back to 4.1.7 seamlessly by restarting the 4.1.7 VM (I'd like to > avoid to rejoin 500 PCs ...) ? > > Any advise welcome . > > Thanks in advance > > Henri > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
Am 19.04.2016 um 10:40 schrieb henri transfert:> I'm considering an upgrade to the last stable release 4.4.2. > > Since this server is in production with 400 users , 500 computers (XP, 7 > Pro, OSX) , NAS members (Synology) , and 15 printers, I can't take any > risks about this upgrade.> - Is there any data to backup before ? (I plan to backup the entire VM > anyway) > > - From the client point of view, in case of 4.4 dysfunction is it possible > to go back to 4.1.7 seamlessly by restarting the 4.1.7 VM (I'd like to > avoid to rejoin 500 PCs ...) ?Read on if you have one single DC, otherwise read only the last line. I always compile Samba on a separate machine, erasing /usr/local/samba before 'make install'. Then I tar that directory, and copy the tgz-file to the real machine. There /usr/local/samba is a link to the real samba directory, which contains the version number, for example 'samba-4.3.6'. I stop samba, then "cp -a samba-$old samba-$new; cd samba-$new; tar xf ../samba-$new-compiled.tgz" Now I can "ln -fs samba-$new samba" and start the new one. If anything goes wrong, simply stop samba, "ln -fs samba-$old samba", and restart the old one. However my samba is not AD yet, it is running as classic PDC. I do not know where AD stores all its data. If it is also all inside /usr/local/samba, then this should work there as well. EXCEPT IF THERE IS ALSO ANOTHER AD-DC. THEN YOU MUST NEVER EVER DO THIS!
Hi, maybe this thread should ask an even more general question: How are AD-DC admins supposed to test upgrades? If there is more than one AD-DC, an upgraded DC which causes problems cannot (must not) be restored from backup. This is one of the reasons why I do not want to switch to AD. A PDC *can* simply be restored from backup. It is even enough to switch back to the previous contents of /usr/local/samba, a matter of seconds. Should we force all clients to use/test the upgraded DC by switching the other DCs off, and in case of problems turn the new DC off, the others back on, and then wipe the upgraded DC? Is it enough to wipe /usr/local/bin, make install, rejoin, copy sysvol? regards, Klaus