>>> Quanah Gibson-Mount <[email protected]> schrieb am 29.03.2019 um 20:51 in Nachricht <A26081897ABCFAFC0B8B8F1A@[192.168.1.39]>: > ‑‑On Friday, March 29, 2019 8:40 PM +0000 Howard Chu <[email protected]> wrote: > >> Maxime Besson wrote: >>> Hi! >>> > >>> How would you handle live backups of a database with lots of write > activity? > > > Sadly Howard did not answer the above question you had, so I'll give you > the best solution I can think of based on what's currently available: > > Have a secondary server (a replica) of the first. Using cn=config, delete > the syncrepl statement from the replica, run slapcat, then re‑add the > syncrepl statement when you're done. As long as the server is under heavy > write traffic and backups take signficant time, you will unfortunately > heavily fragment the DB.
Hi! I wonder: Is there a more elegant solution that lets one "pause" a replication? Such a feature sounds useful for various reasons. Regards, Ulrich Windl > > ‑‑Quanah > > > ‑‑ > > Quanah Gibson‑Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com>
