Directory Server Directory Service exportieren

[shb256]

Hallo an Alle,

mit dem Windows Update aus dem Juli 2023 gibt es leider mal wieder Problem zwischen Windows und Samba.
Grundsätzlich wurde in Samba diese Problem auch zeitnah gefixt siehe hier.
Leider gibt es für Synology noch kein Update und ich erwarte es auch nicht wirklich zeitnah.
Nun würde ich gerne die bestehende Domain in eine eigene VM ziehen, ohne die Domain neu aufzusetzten.
In der Therorie geht das eigentlich recht einfach

samba-tool domain backup offline --targetdir /path/to/backup

in echt geht das auch
hier das Problem aus Sicht der Synology NAS

ash-4.4# samba-tool domain backup offline --targetdir /root/dom
running backup on dirs: /var/packages/DirectoryServerForWindowsDomain/var/private /var/lib/samba /etc/samba
Starting transaction on /var/packages/DirectoryServerForWindowsDomain/var/private/secrets
Starting transaction on /var/packages/DirectoryServerForWindowsDomain/var/private/sam.ldb
backing up /var/packages/DirectoryServerForWindowsDomain/var/private/sam.ldb
backing up locked/related file /var/packages/DirectoryServerForWindowsDomain/var/private/sam.ldb.d/CN%3DCONFIGURATION,DC%3DAD,DC%3DDOMAINNAME,DC%3DDE.ldb
backing up locked/related file /var/packages/DirectoryServerForWindowsDomain/var/private/sam.ldb.d/CN%3DSCHEMA,CN%3DCONFIGURATION,DC%3DAD,DC%3DDOMAINNAME,DC%3DDE.ldb
backing up locked/related file /var/packages/DirectoryServerForWindowsDomain/var/private/sam.ldb.d/DC%3DAD,DC%3DDOMAINNAME,DC%3DDE.ldb
backing up locked/related file /var/packages/DirectoryServerForWindowsDomain/var/private/sam.ldb.d/DC%3DDOMAINDNSZONES,DC%3DAD,DC%3DDOMAINNAME,DC%3DDE.ldb
backing up locked/related file /var/packages/DirectoryServerForWindowsDomain/var/private/sam.ldb.d/DC%3DFORESTDNSZONES,DC%3DAD,DC%3DDOMAINNAME,DC%3DDE.ldb
tdbbackup of locked/related file /var/packages/DirectoryServerForWindowsDomain/var/private/sam.ldb.d/metadata.tdb
Starting transaction on solo db: /var/packages/DirectoryServerForWindowsDomain/var/private/hklm.ldb
running tdbbackup on the same file
Starting transaction on solo db: /var/packages/DirectoryServerForWindowsDomain/var/private/idmap.ldb
running tdbbackup on the same file
Starting transaction on solo db: /var/packages/DirectoryServerForWindowsDomain/var/private/privilege.ldb
running tdbbackup on the same file
running tdbbackup on lone tdb file /var/packages/DirectoryServerForWindowsDomain/var/private/schannel_store.tdb
Starting transaction on solo db: /var/packages/DirectoryServerForWindowsDomain/var/private/share.ldb
running tdbbackup on the same file
running tdbbackup on lone tdb file /var/packages/DirectoryServerForWindowsDomain/var/private/netlogon_creds_cli.tdb
tdb_mutex_open_ok[/var/packages/DirectoryServerForWindowsDomain/var/private/netlogon_creds_cli.tdb]: Can use mutexes only with MUTEX_LOCKING or NOLOCK
Failed to open /var/packages/DirectoryServerForWindowsDomain/var/private/netlogon_creds_cli.tdb
running tdbbackup on lone tdb file /var/lib/samba/winbindd_idmap.tdb
running tdbbackup on lone tdb file /var/lib/samba/winbindd_cache.tdb
running tdbbackup on lone tdb file /var/lib/samba/account_policy.tdb
running tdbbackup on lone tdb file /var/lib/samba/share_info.tdb
running tdbbackup on lone tdb file /var/lib/samba/registry.tdb
running tdbbackup on lone tdb file /etc/samba/private/secrets.tdb
running offline ntacl backup of sysvol
INFO 2023-08-11 18:13:04,150 pid:4143 /var/packages/SMBService/target/usr/lib/python3/site-packages/samba/ntacls.py #621: use /tmp/tmpfv_cyi6d as tempdir
use /tmp/tmpfv_cyi6d as tempdir
We support connectpath is /volulmeX/share, but we get /
We support connectpath is /volulmeX/share, but we get /
Bad talloc magic value - unknown value
===============================================================
INTERNAL ERROR: Signal 6: Aborted in pid 4143 (4.15.13)
If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
===============================================================
PANIC (pid 4143): Signal 6: Aborted in 4.15.13
BACKTRACE:
#0 log_stack_trace + 0x3d [ip=0x7f1aea9ad1ed] [sp=0x7fff35b84340]
#1 smb_panic + 0xd [ip=0x7f1aea9ad55d] [sp=0x7fff35b84c80]
#2 smb_panic + 0xa8 [ip=0x7f1aea9ad5f8] [sp=0x7fff35b84c90]
#3 __sigaction + 0x40 [ip=0x7f1aecacf650] [sp=0x7fff35b84d40]
#4 pthread_key_delete + 0x12c [ip=0x7f1aecb1c3ac] [sp=0x7fff35b852f0]
#5 gsignal + 0x12 [ip=0x7f1aecacf5b2] [sp=0x7fff35b85330]
#6 abort + 0xc5 [ip=0x7f1aecaba464] [sp=0x7fff35b85340]
#7 <unknown symbol> [ip=0x7f1aeaa6f7c2] [sp=0x7fff35b85400]
#8 pytalloc_GetBaseObjectType + 0x14a [ip=0x7f1aeaa4b46a] [sp=0x7fff35b85440]
#9 py_return_ndr_struct + 0x4a [ip=0x7f1ae9d2e0fa] [sp=0x7fff35b85490]
#10 <unknown symbol> [ip=0x7f1ae7043fb2] [sp=0x7fff35b854c0]
#11 _Py_CheckFunctionResult + 0x1e9 [ip=0x7f1aece1d259] [sp=0x7fff35b85550]
#12 _PyObject_MakeTpCall + 0xa1 [ip=0x7f1aece1d861] [sp=0x7fff35b85590]
#13 _PyEval_EvalFrameDefault + 0x5d7f [ip=0x7f1aecdfb7ff] [sp=0x7fff35b855e0]
#14 _PyEval_EvalCodeWithName + 0x91f [ip=0x7f1aeceded1f] [sp=0x7fff35b85720]
#15 _PyFunction_Vectorcall + 0x98 [ip=0x7f1aece1d678] [sp=0x7fff35b857c0]
#16 _PyEval_EvalFrameDefault + 0x5b22 [ip=0x7f1aecdfb5a2] [sp=0x7fff35b85840]
#17 _PyEval_EvalCodeWithName + 0x91f [ip=0x7f1aeceded1f] [sp=0x7fff35b85980]
#18 _PyFunction_Vectorcall + 0x98 [ip=0x7f1aece1d678] [sp=0x7fff35b85a20]
#19 PyCell_Set + 0x87a [ip=0x7f1aece20d5a] [sp=0x7fff35b85aa0]
#20 _PyEval_EvalFrameDefault + 0x5b22 [ip=0x7f1aecdfb5a2] [sp=0x7fff35b85b30]
#21 <unknown symbol> [ip=0x7f1aecdf486b] [sp=0x7fff35b85c70]
#22 _PyEval_EvalFrameDefault + 0x5c3c [ip=0x7f1aecdfb6bc] [sp=0x7fff35b85cb0]
#23 _PyEval_EvalCodeWithName + 0x91f [ip=0x7f1aeceded1f] [sp=0x7fff35b85df0]
#24 _PyFunction_Vectorcall + 0x98 [ip=0x7f1aece1d678] [sp=0x7fff35b85e90]
#25 PyCell_Set + 0x7e5 [ip=0x7f1aece20cc5] [sp=0x7fff35b85f10]
#26 PyVectorcall_Call + 0x73 [ip=0x7f1aece1f483] [sp=0x7fff35b85fa0]
#27 _PyEval_EvalFrameDefault + 0x1dc6 [ip=0x7f1aecdf7846] [sp=0x7fff35b85ff0]
#28 _PyEval_EvalCodeWithName + 0x91f [ip=0x7f1aeceded1f] [sp=0x7fff35b86130]
#29 _PyFunction_Vectorcall + 0x98 [ip=0x7f1aece1d678] [sp=0x7fff35b861d0]
#30 PyCell_Set + 0x7e5 [ip=0x7f1aece20cc5] [sp=0x7fff35b86250]
#31 PyVectorcall_Call + 0x73 [ip=0x7f1aece1f483] [sp=0x7fff35b862e0]
#32 _PyEval_EvalFrameDefault + 0x1dc6 [ip=0x7f1aecdf7846] [sp=0x7fff35b86330]
#33 _PyEval_EvalCodeWithName + 0x91f [ip=0x7f1aeceded1f] [sp=0x7fff35b86470]
#34 _PyFunction_Vectorcall + 0x98 [ip=0x7f1aece1d678] [sp=0x7fff35b86510]
#35 PyCell_Set + 0x7e5 [ip=0x7f1aece20cc5] [sp=0x7fff35b86590]
#36 PyVectorcall_Call + 0x73 [ip=0x7f1aece1f483] [sp=0x7fff35b86620]
#37 _PyEval_EvalFrameDefault + 0x1dc6 [ip=0x7f1aecdf7846] [sp=0x7fff35b86670]
#38 _PyEval_EvalCodeWithName + 0x91f [ip=0x7f1aeceded1f] [sp=0x7fff35b867b0]
#39 _PyFunction_Vectorcall + 0x98 [ip=0x7f1aece1d678] [sp=0x7fff35b86850]
#40 PyCell_Set + 0x7e5 [ip=0x7f1aece20cc5] [sp=0x7fff35b868d0]
#41 PyVectorcall_Call + 0x73 [ip=0x7f1aece1f483] [sp=0x7fff35b86960]
#42 _PyEval_EvalFrameDefault + 0x1dc6 [ip=0x7f1aecdf7846] [sp=0x7fff35b869b0]
#43 _PyEval_EvalCodeWithName + 0x91f [ip=0x7f1aeceded1f] [sp=0x7fff35b86af0]
#44 _PyFunction_Vectorcall + 0x98 [ip=0x7f1aece1d678] [sp=0x7fff35b86b90]
#45 PyCell_Set + 0x7e5 [ip=0x7f1aece20cc5] [sp=0x7fff35b86c10]
#46 PyVectorcall_Call + 0x73 [ip=0x7f1aece1f483] [sp=0x7fff35b86ca0]
#47 _PyEval_EvalFrameDefault + 0x1dc6 [ip=0x7f1aecdf7846] [sp=0x7fff35b86cf0]
#48 _PyEval_EvalCodeWithName + 0x91f [ip=0x7f1aeceded1f] [sp=0x7fff35b86e30]
#49 PyEval_EvalCodeEx + 0x3f [ip=0x7f1aecedefef] [sp=0x7fff35b86ed0]
#50 PyEval_EvalCode + 0x1f [ip=0x7f1aecedf01f] [sp=0x7fff35b86f30]
#51 _PyObject_CheckCrossInterpreterData + 0xea [ip=0x7f1aecf152ca] [sp=0x7fff35b86f70]
#52 _PyObject_CheckCrossInterpreterData + 0x1a0 [ip=0x7f1aecf15380] [sp=0x7fff35b86fa0]
#53 PyRun_InteractiveOneFlags + 0xf0 [ip=0x7f1aecf17e30] [sp=0x7fff35b86fd0]
#54 PyRun_SimpleFileExFlags + 0x131 [ip=0x7f1aecf17fa1] [sp=0x7fff35b87020]
#55 Py_RunMain + 0x748 [ip=0x7f1aecf33298] [sp=0x7fff35b870a0]
#56 Py_BytesMain + 0x5e [ip=0x7f1aecf337ee] [sp=0x7fff35b871a0]
#57 __libc_init_first + 0x77 [ip=0x7f1aecabb177] [sp=0x7fff35b87230]
#58 __libc_start_main + 0x85 [ip=0x7f1aecabb235] [sp=0x7fff35b872d0]
#59 _start + 0x21 [ip=0x55fbb8a44081] [sp=0x7fff35b87320]
Can not dump core: corepath not set up
ash-4.4#

ash-4.4#

Das Backup stribt mit einem Internal error.
Gibt es dafür eine Lösung oder ein Workaround?

Danke

 

[Adama]

Moin @shb256

Schau mal hier: https://community.synology.com/enu/forum/1/post/161649?page=1

Das müsste das eigentlich lösen...

Dass das Backup nicht läuft, liegt vermutlich an den Manipulationen von Synology. Das ist leider kein natives Samba mehr, die flanschen da noch eigene Logik an.

 

[maxblank]

In welches Betriebssystem in der VM willst du das umziehen?

 

[shb256]

@Adama danke! Genau das habe ich gesucht.
wie findet man sowas? Ich habe zwar die Probleme gefunden aber nicht die Lösung
@maxblank auf eine Debian VM

 

[Adama]

Bin mir gar nicht mehr sicher, wo ich das gefunden hab. War - glaube ich - bei einer Suche hochgepoppt.

Der beste Weg, um eine Domain umziehen, ist übrigens einfach einen neuen DC zu joinen, ev. die FSMO zu verschieben (wenn der alte diese hält) und dann den alten DC zu demoten.

Naja, normalerweise sollte man natürlich auch mehr als einen DC haben.