[Samba] steady increase of objects reported by dbcheck in my test samdom
Rowland penny
rpenny at samba.org
Tue Jun 1 09:54:41 UTC 2021
On 01/06/2021 10:22, mj via samba wrote:
> Hi,
>
> I left out --cross-ncs to create the LDIF, as the increase of objects
> is also reported without --cross-ncs. (trying keep it simple)
>
> Here is a diff of 2843 -> 2844 objects:
>
>>> > dn: CN=SAMDOM-WIN2012-,CN=Topology,CN=Domain System Volume,CN
>>> > objectClass: top
>>> > objectClass: msDFSR-Member
>>> > cn: SAMDOM-WIN2012-
>>> > instanceType: 4
>>> > whenCreated: 20210601175003.0Z
>>> > uSNCreated: 13556
>>> > showInAdvancedViewOnly: TRUE
>>> > name: SAMDOM-WIN2012-
>>> > objectGUID:
>>> 38fc7430-1e69-415e-aa8b-0d31ac581165
>>> > objectCategory:
>>> CN=ms-DFSR-Member,CN=Schema,CN=Configuration,
>>> > serverReference: CN=NTDS
>>> Settings,CN=SAMDOM-WIN2012-,CN=Serve
>>> > whenChanged: 20210601085134.0Z
>>> > msDFSR-ComputerReference:
>>> CN=SAMDOM-WIN2012-,OU=Domain Contro
>>> > uSNChanged: 13558
>>> > distinguishedName:
>>> CN=SAMDOM-WIN2012-,CN=Topology,CN=Domain S
>>> >
>>> > # record 363
>>> highest_usn : 0x000000000000
>>> | highest_usn : 0x000000000000
>>> highest_usn : 0x000000000000
>>> | highest_usn : 0x000000000000
>>> last_success : Tue Jun 1 10:41:35 20
>>> | last_success : Tue Jun 1 10:51:34 20
>>> last_attempt : Tue Jun 1 10:41:35 20
>>> | last_attempt : Tue Jun 1 10:51:34 20
>>> tmp_highest_usn : 0x000000000000fdfc
>>> | tmp_highest_usn : 0x000000000000fe21
>>> highest_usn : 0x000000000000fdfc
>>> | highest_usn : 0x000000000000fe21
>>> last_success : Tue Jun 1 10:41:35 20
>>> | last_success : Tue Jun 1 10:51:34 20
>>> last_attempt : Tue Jun 1 10:41:35 20
>>> | last_attempt : Tue Jun 1 10:51:34 20
>>> tmp_highest_usn : 0x000000000000c213
>>> | tmp_highest_usn : 0x000000000000c28a
>>> highest_usn : 0x000000000000c213
>>> | highest_usn : 0x000000000000c28a
>>> last_success : Tue Jun 1 10:41:39 20
>>> | last_success : Tue Jun 1 10:51:35 20
>>> last_attempt : Tue Jun 1 10:41:39 20
>>> | last_attempt : Tue Jun 1 10:51:35 20
>>> <
>>> # record 1771 <
>>> dn: CN=SAMDOM-WIN2012-,CN=Topology,CN=Domain System Volume,CN <
>>> objectClass: top <
>>> objectClass: msDFSR-Member <
>>> cn: SAMDOM-WIN2012- <
>>> instanceType: 4 <
>>> whenCreated: 20210601174011.0Z <
>>> uSNCreated: 13548 <
>>> showInAdvancedViewOnly: TRUE <
>>> name: SAMDOM-WIN2012- <
>>> objectGUID: 5e76b78a-48a1-42a9-824b-e22c35e8bac9 <
>>> objectCategory: CN=ms-DFSR-Member,CN=Schema,CN=Configuration, <
>>> serverReference: CN=NTDS Settings,CN=SAMDOM-WIN2012-,CN=Serve <
>>> whenChanged: 20210601084135.0Z <
>>> msDFSR-ComputerReference: CN=SAMDOM-WIN2012-,OU=Domain Contro <
>>> uSNChanged: 13550 <
>>> distinguishedName: CN=SAMDOM-WIN2012-,CN=Topology,CN=Domain S <
>
> It seems to be about the same server SAMDOM-WIN2012-, that is getting
> a new objectGUID in the in CN=Topology.
>
> Can anyone explain what we are seeing? And why is it causing dbcheck
> objects to increase? It seems more like an update..? (the objectGUID
> is replaced, and the old objectGUID is gone in the newer dump)
>
> I hope formatting above will survive...
>
> MJ
>
I wonder if your Windows DC's are trying to replicate Sysvol to the
Samba DC and failing ???
'Topology' seems to have something to do with DFSR (Distributed File
System Replication), something that Samba doesn't have yet.
Rowland
More information about the samba
mailing list