Koozali.org: home of the SME Server
Contribs.org Forums => Koozali SME Server 10.x => Topic started by: yythoss on July 07, 2022, 04:31:18 PM
-
Is there a howto to migrate a samba domain controller from a SME 9.2 to a SME10. It would be important that the Windows clients do not have to be join to the domain again. With Affa from SME9 to SME9 it works wonderfully.
But unfortunately that doesn't work from SME 9.2 to SME 10.
THX
-
Standard upgrade path is as per the wiki.
https://wiki.koozali.org/SME_Server:10.0
I suggest you do some serious testing first, and read about SMB1/SMB2/SMB3 as well. There is lots here.
Affa is not recommended for upgrades. Some have used it, but there are no guarantees.
-
THX for this link, but I know that.
I want to move the SME9 to a new Hardware with SME10 is installed.
-
I want to move the SME9 to a new Hardware with SME10 is installed.
Sorry - please explain a little more clearly exactly what you trying to do as it is not clear to me.
You have an SME v10 that is already installed. Are you using it?
Are you planning to delete all the data and start again, or are you wanting to merge it with an existing SME v9?
-
There is a SME9 as a productive server and is used as a domain controller for the Windows 10 Clients.
There is now a new hardware with a freshly installed SME10. I would now like to move the domain controller from the SME9 to the SME10 and then switch off the SME9.
However, it should be the case that the Windows clients can continue to logon to the SME10 without having to add all Windows clients to the domain again. The rest of the data is no problem to move to the SME10.
-
My Idea was:
1.) Create all Users on the SME10 with the same UserID from SME9
2.) Copy /etc/samba/secrets.tdb and /etc/samba/smbpasswd form SME9 to SME10
3.) Restart Samba on SME10
-
aren’t they part of core backup?
-
No
-
well, code says : yes
my @backup = (
'home/e-smith',
'etc/e-smith/templates-custom',
'etc/e-smith/templates-user-custom',
'etc/ssh',
'root',
'etc/sudoers',
'etc/passwd',
'etc/shadow',
'etc/group',
'etc/gshadow',
'etc/samba/secrets.tdb',
'etc/samba/smbpasswd',
'etc/backup-data.d',
);
-
https://wiki.koozali.org/Migratehelper out of the box, no domain memberships or passwords lost, working in production :)
/etc/samba/secrets.tdb
/etc/samba/smbpasswd
/etc/samba/schannel_store.tdb
/var/lib/samba/group_mapping.tdb
/var/lib/samba/account_policy.tdb
-
That's what I was looking for, thank you!
-
both migratehelper and core console usb backup will backup those samba files per default.
be carrefull for migratehelper it is more versatil, helps backuping sme9 contribs and also allow not to backup the huge folders of data, so you can restore the configuration, and latter sync the users and ibays data.
-
Yes, but files that are not compatible with SME10 are also backed up. That's why I don't want to use that.
Files from ibay are easy to back up with tar. My problem was only Samba Domain Controller.
-
Is there a howto to migrate a samba domain controller from a SME 9.2 to a SME10. It would be important that the Windows clients do not have to be join to the domain again. With Affa from SME9 to SME9 it works wonderfully.
But unfortunately that doesn't work from SME 9.2 to SME 10.
THX
This is typically not even recommended for Windows Server. Most Windows Server admins will tell you to do a fresh install and avoid an in-place upgrade. With a Windows Domain Controller, you can copy the active directory to another Domain Controller, do the upgrade on the main box, then copy the active directory back over to the main server. This isn't an option with SME 10.
As painful as it is, you really are much better off re-joining the workstations to SME 10 if you are moving to SME 10. Their are some tricks you can do with Samba to copy over machine accounts to a new SME install, but I wouldn't recommend most people try it. It's far too easy to make a hell of a mess.
-
Yes, but files that are not compatible with SME10 are also backed up.
can you elaborate this statement ?
-
I think:
/home/e-smith/
so you include /home/e-smith/db
There are files that make problems.
/home/e-smith/db/mysql
/home/e-smith/db/ldap
/home/e-smith/db/yum_repositories
-
I think:
/home/e-smith/
so you include /home/e-smith/db
There are files that make problems.
/home/e-smith/db/mysql
/home/e-smith/db/ldap
/home/e-smith/db/yum_repositories
those files are your db settings and the core of SME, they are of course backuped and restored.
There are process of migration for all of them when needed and tests about that.
if you have a specific problem related with one of those files then you need to document it with expected behaviour, result observed, installed packages and logs and fill a bug.
also need to be more specific than « problems »
it is like saying my car does not work.