Wednesday, September 13, 2023

[389-users] Migration: importing an OU to a new instance

I've read this doc:
https://access.redhat.com/documentation/en-us/red_hat_directory_server/12/html/importing_and_exporting_data/importing-data-to-directory-server_importing-and-exporting-data

The export from server A to an LDIF file works and I've done some testing but it seems like the import feature always deletes existing OUs on server B that aren't in the exported LDIF file. Am I missing something? I'd like to simply get an LDIF of all the entries in Server A and populate only that OU in server B.

Related, this bit is bewildering
Optional: By default, Directory Server sets the entry update sequence numbers (USNs) of all imported entries to 0. To set an alternative initial USN value, set the nsslapd-entryusn-import-initval parameter. For example, to set USN for all imported values to 12345, enter:

I don't understand what this means or the consequences of taking the default or not. Server B is already in multi-supplier replication with other servers, so I worry about screwing that up with any import choices I might make.
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

No comments:

Post a Comment