Thanks William.
Just wanted to make an update to report that recovery via ldif2db was successful last night.
Thanks,
Trev
On 2020-09-17, 7:37 PM, "William Brown" <wbrown@suse.de> wrote:
> I don't want to do an db2ldif during production time since it will put the db into read-only mode.
> The primary provider will do a backup at 01:00 (with -r) so I'll grab that and try to ldif2db the secondary provider with it.
>
Yep, that seems like your best course of action at this point. :)
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs
_______________________________________________
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
_______________________________________________
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
No comments:
Post a Comment