Restore specifying a backend fails if the target_server has extra backends. bak2db arcivedir -Z target_server -n backend
origin_server has NetscapeRoot and userRoot. target_server has userRoot and testRoot.
If the backup from origin_server is restored onto target_server with "-n userRoot", it fails.
DBVERSION entryrdn.db id2entry.db
Error log on the target server: [] - Copying /var/lib/dirsrv/slapd-origin/bak/origin-2016_03_22_10_41_57/NetscapeRoot/parentid.db to /var/lib/dirsrv/slapd-target/db/../fribak/NetscapeRoot/parentid.db [] - Removing file /var/lib/dirsrv/slapd-target/db/../fribak/DBVERSION from staging area [] - Removing file /var/lib/dirsrv/slapd-target/db/../fribak/log.0000000001 from staging area [] - Removing file /var/lib/dirsrv/slapd-target/db/../fribak/.repl_changelog_backup from staging area [] - Removing file /var/lib/dirsrv/slapd-target/db/../fribak/testRoot from staging area [] - Removing file /var/lib/dirsrv/slapd-target/db/../fribak/NetscapeRoot from staging area [] - resizing db cache size: 20000000 -> 10000000 [] - Instance Config Entry cn=userRoot,cn=ldbm database,cn=plugins,cn=config [] - Add Attribute nsslapd-directory Value /var/lib/dirsrv/slapd-origin/db/userRoot [] - Del Attribute nsslapd-directory Value /var/lib/dirsrv/slapd-target/db/userRoot [] - nsslapd-directory can't be modified while the server is running. [] - WARNING!!: current Instance Config is different from backed up configuration; The backup is restored.
Discussion in the weekly meeting:
This functionality (mrclone) has a design bug. By "copying" one supplier's backend to the corresponding consumer's, there could be mismatches between the copied db files and the bdb transaction logs.
We should not work on this bug but should deprecate this feature.
Closing this ticket.
Reopening this ticket for the code cleanup.
We should disable bak2db -n backend. If it is issued, print "not supported" and suggest online init or db2ldif -r + ldif2db in the output from the script.
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.6.0
Metadata Update from @mreynolds: - Issue close_status updated to: None - Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1834
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.