Hello,

I am running openldap 2.6.3 configured as provider-consumer and I would like to do backup/restore of the database on the provider.

I create a backup on working sladp using command(ends with success, file created): slapd.exe –T cat –f slapd.conf –l backup.ldif

And then trying to load it using slapd command into a new database(restore): slapd.exe -T add -f slapd.conf -l backup.ldif -d -1

Command ends with: . creatorsName: uid=root,ou=invalid,dc=vmbox,dc=int createTimestamp: 20230410111050Z entryCSN: 20230410111051.368528Z#000000#000#000000 modifiersName: uid=root,ou=invalid,dc=vmbox,dc=int modifyTimestamp: 20230410111050Z contextCSN: 20230410125515.-401856Z#000000#000#000000 "

...

...

dnPrettyNormal: <dc=vmbox,dc=int>

<<< dnPrettyNormal: <dc=vmbox,dc=int>, <dc=vmbox,dc=int>

...

...

dnNormalize: <uid=root,ou=invalid,dc=vmbox,dc=int>

<<< dnNormalize: <uid=root,ou=invalid,dc=vmbox,dc=int>

...

...

dnNormalize: <uid=root,ou=invalid,dc=vmbox,dc=int>

<<< dnNormalize: <uid=root,ou=invalid,dc=vmbox,dc=int> <= str2entry NULL (smr_normalize contextCSN 21) slapadd: could not parse entry (line=1) slapadd shutdown: initiated slapadd destroy: freeing system resources.

When I look into backup.ldif files I see that there is an '-' in contextCSN timestamp which cause this behaviour: entryCSN: 20230410111051.368528Z#000000#000#000000 modifiersName: uid=root,ou=invalid,dc=vmbox,dc=int modifyTimestamp: 20230410111050Z contextCSN: 20230410125515.-401856Z#000000#000#000000 ^^^^^^ contextCSN: 20230412130738.035155Z#000000#002#000000

I also see that entryCSN also can be negative which also causes similar problems when loading files.

I would like to ask if there is any way to restore backup in this scenario in a proper way? for instance removing the "-" sign?

Thank in advance for your response,

Best regards,

Peter