S3 to S4 migration (samba-tools) -- Progress!
Adam Tauno Williams
awilliam at whitemice.org
Fri Jan 13 09:27:42 MST 2012
On Wed, 2012-01-11 at 08:04 +1100, Andrew Bartlett wrote:
> On Tue, 2012-01-10 at 14:59 -0600, Ricky Nance wrote:
> > Might help if you could describe more of how you had your S3 server setup.
> > What kind of backend would be the very minimum to mention (more details the
> > better though). The groups didn't transfer from my ldap backend at first,
> > but I am 99% sure Amitay fixed that issue. Please also tell us what samba
> > --version reports.
> We did a lot of work with Ricky on his transition, and the biggest point
> that remained is that we do not warn if we do not find the groups
> locally when we attempt the upgrade.
> That is, groups in Samba3 are defined by posix or the setting
> 'ldapsam:trusted'. If a migration is done by first transferring the
> Samba data between hosts, the groups also need to be transferred such
> that Samba3 would be able to operate.
In working on my S3->S4 migration I did notice that UID seems to have
moved but not GID [I assume that is what we are talking about here??].
barbel:/tmp # wbinfo -i adam
437 is my old S3/LDAPSAM UID [awesome!] but 100 appears to just be a
default GID. My S3/LDAPSAM GID is 230.
In light of the above statement I made use all the POSIX groups from the
S3 domain existed on the new S4 server.
old server: getent group
append those groups to /etc/groups on new server
getent group now lists all the groups on new server
Then I reran the domain migration. But groups [gids] assignments still
did not seem to have been copied.
Otherwise everything seems to have transferred successfully, which is
--- somewhat related ----
System & Network Administrator [ LPI & NCLA ]
OpenGroupware Developer <http://www.opengroupware.us>
Adam Tauno Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part
More information about the samba-technical