Sven, I wish I could give you better advice than this:
- Do a sogo-backup on each user on each server - Backup both databases - Merge Databases - If users complain restore from sogo-backup on a user by user basis. What database system are you using? Have you considered a N-way multi-master system like Galera with MySQL or MariaDB? In the future you should have at least 3 database nodes to avoid the split brain issue that you now have. Good Luck, Mark -------- Original Message -------- Subject: Re: [SOGo] Merging diverged databases Date: Monday, July 28, 2014 09:11 AM CDT From: Sven Schwedas <sven.schwe...@tao.at> Reply-To: users@sogo.nu Organization: TAO Software To: users@sogo.nu References: <53ce3155.8070...@tao.at> > On 2014-07-22 11:39, Sven Schwedas wrote: > > Hello, > > > > I've noticed that during my vacation our (master-master) database > > replication failed (for unrelated reasons), and now our SOGo databases > > have diverged quite a bit between the servers. > > > > The good news is that each user exclusively wrote to *one* server, and > > both servers have used correct autoincrement values, so there shouldn't > > be any conflicts. > > > > What's the best strategy here to merge the databases? Use sogo-backup > > for each user on the correct server, and then restore on a pristine > > database? Or can I just merge the databases directly? > > *bump* Any opinion on this? I'm inclined to use sogo-backup just to be > on the safe side, could that lead to any problems? > > -- > Mit freundlichen Grüßen, / Best Regards, > Sven Schwedas > Systemadministrator > TAO Beratungs- und Management GmbH | Lendplatz 45 | A - 8020 Graz > Mail/XMPP: sven.schwe...@tao.at | +43 (0)680 301 7167 > http://software.tao.at > -- users@sogo.nu https://inverse.ca/sogo/lists