#51152 add changelog conf to backup
Closed: wontfix 3 years ago by spichugi. Opened 3 years ago by elkris.

In a backup we store information about backend and index configuration in the files: dse_index.ldif dse_instance.ldif

The intention is to ensure that a backup is only restored to an instance thah has the same configuration. In fact, these files are read during a restore and if a mismatch is detected a warning is logged, but restore tries to procede.

There could also be a mismatch in changelog configuration, eg changelog dir path, encryption. But there is no way to detect it.

If we would store changelog information like backend and index info this could be done if requested.

BUT the main benefit of having this info available would be if a backup from a version with traditional changelog is restored to a instance with the integrated changelog. It could be used to temporarily create the changelog dir


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4

3 years ago

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/4205

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

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)

3 years ago

Login to comment on this ticket.

Metadata