> On 16 Jan 2026, at 04:52, tdarby--- via 389-users > <[email protected]> wrote: > > 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?
What is the process you are using on the "recovered" instance? The changelog shouldn't need rebuilding if you are just starting up from an existing DB. Are you restoring a backup perhaps? > 2. Is there a better way to do this recovery? I think you pretty much have it right, it's just different gradients. * If you lose one server, you just rebuild it and re-init from replication. * If you lose many servers (but at least one survives), you can rebuild them and re-init from replication. * If you lose all servers, then you have to restore one instance from a backup, and then proceed to rebuild/reinit from there. -- Sincerely, William Brown Senior Software Engineer, Identity and Access Management SUSE Labs, Australia
-- _______________________________________________ 389-users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
