I'm testing disaster recovery for a set of 389 servers in multi-master replication. These are AWS instances with attached EBS volumes, so it amounts to restoring the EBS from backup and starting a new EC2.
My preferred scenario would be to recover just one of the instances, attempting to avoid any out-of-sync replication issues with the others, and then create new replicas from the one recovered instance. When I do this, however, the recovered instance wants to rebuild the replication changelog and this can take up to an hour. My questions are:
1. Is there any way to start an instance like this with replication completely disabled?
2. Is there a better way to do this recovery?
Tim
--
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
No comments:
Post a Comment