#49550 do not write changelog RUV in online backup
Opened a year ago by lkrispen. Modified a year ago

The replication code has a mechanism to write the changelog RUV to the changelog database file when on online backup is done.
Before the backup it is written and after the backup it is removed again.
But if there are any mods while the backup proceeds (this is the feature of online, the txn logs will be in the backup and at restore all mods during backup will be recovered).

But in this scenario the changelog RUV and the database RUV will not match and at restore the changelog will be recreated and lost.
The correct method would be NOT to write the changelog RUV, at restore it will be recalculated from the changelog an set


Metadata Update from @lkrispen:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

a year ago

I'm not sure if this is ready for review, but it looks good to me, ack

I'm not sure if this is ready for review, but it looks good to me, ack

no, wanted to add a test case, but didn't want to loose the patch

Like @mreynolds the patch looks good to me and I am happy to remove no longer used code.
SLAPI_PLUGIN_BE_PRE_BACKUP_FN and SLAPI_PLUGIN_BE_POST_BACKUP_FN are not documented but are in slapi-plugin.h. Is ok to remove them.

Like @mreynolds the patch looks good to me and I am happy to remove no longer used code.

It is used, but I think it should not be used.

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.0

a year ago

Login to comment on this ticket.

Metadata