samba - Jan 2015 - recreating domain with existing gid and uid

Okay, I gave up fixing that raspberry and going to use some conventional
legacy PC instead and reinstall it all.

Is there a way I can use the group, user and domain controller IDs from the
backups I created to reinstall a new Samba4 DC without the clients noticing?

I don't like to rejoin everything yet another time.

- Axel

If you did it as the backup and restore wiki says I see no problem as long as it
was the only domain controller (I guess samba4?)

Install your new machine with same IP and hostname, provision your domain with
the same version and restore your backup.
I did it and it worked.

Tim

Am 21. Januar 2015 18:01:20 MEZ, schrieb Axel Kittenberger <axkibe at
gmail.com>:
>Okay, I gave up fixing that raspberry and going to use some
>conventional
>legacy PC instead and reinstall it all.
>
>Is there a way I can use the group, user and domain controller IDs from
>the
>backups I created to reinstall a new Samba4 DC without the clients
>noticing?
>
>I don't like to rejoin everything yet another time.
>
>- Axel
>-- 
>To unsubscribe from this list go to the following URL and read the
>instructions:  https://lists.samba.org/mailman/options/samba

Am 21.01.2015 um 20:16 schrieb Tim:
> Install your new machine with same IP and hostname,
> provision your domain with the same version and restore your backup.

He ment "install Samba using the same version and pathes" and not
"provision your domain with the same version". You don't do a
provision.
You're copying back your old databases.


Regards,
Marc

On of the database files in /private was reported to corrupted by
samba_backup, so I played it safe and spend today to redo the domain from
scratch and rejoined every pc and recreated all user and group accounts.
And yes I did ran that hidden samba_backup thing this time right afterward.
This one is a small domain anyway, thats why I felt it as good testcase to
go for samba4 for a chance too.

One part of the question was tough, if it matters if one changes the cpu
architecture when importing a backup. or if other libs matter. Not that it
matters for my case anymore.

I would do the following (and did it just to know how how it works)

Create your domain and do a backup. 
Possibly you can set up a second network with the same subnet decoupled from
your existing production one. Than restore your DC as described in the wiki and
switch one client in this testing network and do some tests. It should work.

I customized the original script a bit. Have a look here:
https://groups.google.com/forum/m/#!topic/linux.samba/5_18I-9orIY

Regards
Tim

Am 22. Januar 2015 21:23:58 MEZ, schrieb Axel Kittenberger <axkibe at
gmail.com>:
>On of the database files in /private was reported to corrupted by
>samba_backup, so I played it safe and spend today to redo the domain
>from
>scratch and rejoined every pc and recreated all user and group
>accounts.
>And yes I did ran that hidden samba_backup thing this time right
>afterward.
>This one is a small domain anyway, thats why I felt it as good testcase
>to
>go for samba4 for a chance too.
>
>One part of the question was tough, if it matters if one changes the
>cpu
>architecture when importing a backup. or if other libs matter. Not that
>it
>matters for my case anymore.