restore uses BDB's fatal recovery feature which reads ALL transaction logs, not only past the last 2 checkpoints as with normal recovery.
to make this work in all cases we would have to enforce the log rollover during upgrad so that later backup/restore do not see references to old cl files in the txn logs.
In the lates patch I added a call and a stub for "bdb_force_logrenewal()" and added comments to what should be done
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1843525
Issue linked to Bugzilla: Bug 1843525
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue priority set to: major - Issue set to the milestone: 1.4.4 - Issue tagged with: Replication, lmdb
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/4177
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.