Hi, I'm making tests to migrate our actual 4.4.5 to a latest versions and add a second dc. I have added a second dc with 4.10.7 and seems to work fine, now I have 4.4.5 with fsmo roles and a second dn with 4.10.7, but reading wiki https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC seems that since latest days some changes about steps to upgrade, now seems that is recommended to us in-place for 4.4.5 ---- Update one Samba AD DC that does not hold any flexible single master operations (FSMO) role, or else the DC with the least roles. For upgrading to a new release, most users should simply follow the 'in-place upgrade' steps above. Advanced users upgrading to a new major release may want to consider using the 'DC rejoin' steps below. Joining a DC to domain can be a troublesome process for some users, and it can be difficult to recover your DC if something goes wrong. Only consider using this approach if you are an advanced Samba user, and are running a modern Samba installation (i.e. v4.7 release or later, with a minimum 2008R2 base schema). Only use this approach for major Samba version upgrades (e.g. v4.10 to v4.11). --- But also appears that is best to use join: Rejoining the upgraded DC has some benefits for your AD database over in-place upgrades. --> What are these benefit? Anybody can give detail about advantages and disadvantages about two methods? what is the recommended in my case, 4.4.5, 1 dc and I need to migrate to 2 dc, both with 4.10.7 Also I like to have an alternatives option/backup in caise of failure, can I do a snapshot of 4.4.5 samba server with samba stopped, before migrate and join new servers,... and in caise of any error revert to this snapshot? All machines and users will work If I have to revert to this previious state? I understand that new users/machines added after machine will be lost Thanks!
On 12/09/2019 10:13, Trenta sis via samba wrote:> Hi, > > I'm making tests to migrate our actual 4.4.5 to a latest versions and > add a second dc. > > I have added a second dc with 4.10.7 and seems to work fine, now I > have 4.4.5 with fsmo roles and a second dn with 4.10.7, but reading > wiki https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC seems > that since latest days some changes about steps to upgrade, now seems > that is recommended to us in-place for 4.4.5 > > ---- > Update one Samba AD DC that does not hold any flexible single master > operations (FSMO) role, or else the DC with the least roles. > > For upgrading to a new release, most users should simply follow the > 'in-place upgrade' steps above. > Advanced users upgrading to a new major release may want to consider > using the 'DC rejoin' steps below. > > > Joining a DC to domain can be a troublesome process for some users, > and it can be difficult to recover your DC if something goes wrong. > Only consider using this approach if you are an advanced Samba user, > and are running a modern Samba installation (i.e. v4.7 release or > later, with a minimum 2008R2 base schema). Only use this approach for > major Samba version upgrades (e.g. v4.10 to v4.11). > --- > > But also appears that is best to use join: > Rejoining the upgraded DC has some benefits for your AD database over > in-place upgrades. --> What are these benefit? > > Anybody can give detail about advantages and disadvantages about two methods? > what is the recommended in my case, 4.4.5, 1 dc and I need to migrate > to 2 dc, both with 4.10.7 > > > Also I like to have an alternatives option/backup in caise of failure, > can I do a snapshot of 4.4.5 samba server with samba stopped, before > migrate and join new servers,... and in caise of any error revert to > this snapshot? All machines and users will work If I have to revert to > this previious state? I understand that new users/machines added after > machine will be lost > > Thanks! >Hi, you seem to have wandered into a discussion that the Samba team members have been having about which is the best way to upgrade Samba ;-) Whilst I understand that re-joining has it benefits, I have never updated this way, I just use apt-get and have never had any problems. From the problems posted on this list, I think a lot of them have been caused by jumping multiple versions at once i.e. trying to go from 4.5.x to 4.9.x I think the best way is to 'walk' up the versions, 4.5.x -> 4.7.x -> 4.8.x -> 4.9.x The only probable way to do this is by the re-join method. The main cause of having to jump multiple versions of Samba is that the distro's only seem to change the Samba version when they change the distro version and even then, they don't seem to use the latest Samba version. I would suggest getting to the latest version of Samba and then upgrade on a regular basis. This will probably mean finding and using an external repo for Samba e.g. Louis's for Debian/Ubuntu 18.04 Rowland
Hi Rowland, Recently I have upgraded a single server 4.4.5 to 4.10.7 with in-place method and all seems to works fine. Can you give detail what are this advantages to upgrade with rejoins about database, performance (index recreated?), stability, dbcheck... what are the realadvantages and disadvantages to evaluate in our case what is the best method To rejoin I think with this steps: - fsmo transfer - demote dc1 - delete old folder samba on dc1 - join dc1 with smae parameters used to join dc2 to 4.4.5 Correct? Thanks for all you help! Missatge de Trenta sis <trenta.sis at gmail.com> del dia dj., 12 de set. 2019 a les 11:13:> > Hi, > > I'm making tests to migrate our actual 4.4.5 to a latest versions and > add a second dc. > > I have added a second dc with 4.10.7 and seems to work fine, now I > have 4.4.5 with fsmo roles and a second dn with 4.10.7, but reading > wiki https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC seems > that since latest days some changes about steps to upgrade, now seems > that is recommended to us in-place for 4.4.5 > > ---- > Update one Samba AD DC that does not hold any flexible single master > operations (FSMO) role, or else the DC with the least roles. > > For upgrading to a new release, most users should simply follow the > 'in-place upgrade' steps above. > Advanced users upgrading to a new major release may want to consider > using the 'DC rejoin' steps below. > > > Joining a DC to domain can be a troublesome process for some users, > and it can be difficult to recover your DC if something goes wrong. > Only consider using this approach if you are an advanced Samba user, > and are running a modern Samba installation (i.e. v4.7 release or > later, with a minimum 2008R2 base schema). Only use this approach for > major Samba version upgrades (e.g. v4.10 to v4.11). > --- > > But also appears that is best to use join: > Rejoining the upgraded DC has some benefits for your AD database over > in-place upgrades. --> What are these benefit? > > Anybody can give detail about advantages and disadvantages about two methods? > what is the recommended in my case, 4.4.5, 1 dc and I need to migrate > to 2 dc, both with 4.10.7 > > > Also I like to have an alternatives option/backup in caise of failure, > can I do a snapshot of 4.4.5 samba server with samba stopped, before > migrate and join new servers,... and in caise of any error revert to > this snapshot? All machines and users will work If I have to revert to > this previious state? I understand that new users/machines added after > machine will be lost > > Thanks!
On 12/09/2019 11:56, Trenta sis via samba wrote:> Hi Rowland, > > Recently I have upgraded a single server 4.4.5 to 4.10.7 with in-place > method and all seems to works fine. > > Can you give detail what are this advantages to upgrade with rejoins > about database, performance (index recreated?), stability, dbcheck... > what are the realadvantages and disadvantages to evaluate in our case > what is the best methodIn your instance, as you now have a fairly recent version of Samba on your second DC, you will already have all the benefits of the latest index and database improvements.> > To rejoin I think with this steps: > - fsmo transfer > - demote dc1 > - delete old folder samba on dc1 > - join dc1 with smae parameters used to join dc2 to 4.4.5 > > Correct? >I would transfer the FSMO roles to the second DC, then demote DC1, remove the existing Samba packages and clean up anything 'Samba' left. Install the new Samba packages (this should recreate the Samba directories) and then join to the domain as a DC, as you did for DC2. The other way to do this would be to transfer the FSMO roles to the second DC, then demote DC1 and then re-install the OS, this would also allow you to upgrade the distro. Rowland
On 12/09/19 9:13 PM, Trenta sis via samba wrote:> But also appears that is best to use join: > Rejoining the upgraded DC has some benefits for your AD database over > in-place upgrades. --> What are these benefit? > > Anybody can give detail about advantages and disadvantages about two methods? > what is the recommended in my case, 4.4.5, 1 dc and I need to migrate > to 2 dc, both with 4.10.7Sorry, I only updated that page yesterday and left off a link. This explains more about the differences between in-place upgrades and rejoins: https://wiki.samba.org/index.php/Downgrading_an_Active_Directory_DC#In-place_upgrades_vs_DC_rejoins
Great, thanks! Missatge de Tim Beale <timbeale at catalyst.net.nz> del dia dj., 12 de set. 2019 a les 23:04:> > On 12/09/19 9:13 PM, Trenta sis via samba wrote: > > But also appears that is best to use join: > > Rejoining the upgraded DC has some benefits for your AD database over > > in-place upgrades. --> What are these benefit? > > > > Anybody can give detail about advantages and disadvantages about two methods? > > what is the recommended in my case, 4.4.5, 1 dc and I need to migrate > > to 2 dc, both with 4.10.7 > > Sorry, I only updated that page yesterday and left off a link. > > This explains more about the differences between in-place upgrades and > rejoins: > > https://wiki.samba.org/index.php/Downgrading_an_Active_Directory_DC#In-place_upgrades_vs_DC_rejoins > >