I had a well-running open-source 5.0.18 installation. I went to another spare machine intending to create a mirror. I installed full new 5.0.18 on the spare machine.
Not quite sure what happened next. I stopped the "new" machine and the original seemed fine. However, overnight the backup script stopped zimbra, copied it to the backup folder then tried to restart. It failed because ldap was looking for the "new" server.
Unfortunately, even starting the new server didn't help and one thing and another I give up.
I have all the original mail store and mysql database etc. How can I re-install 5.0.18 and rebuild the local configuration? It no longer asks me for installation details because it reads and save the old configuration - which I screwed up in the first place!
Alternatively, how can I replace the message store of a brand-new installation with the original - how do I connect the recreated users with their original mail etc.?
What more information must I give?
Very red-faced, should have known better, Derek
O.K. Did the twenty-step re-install from [SOLVED] Same error when recovering, this time on machine with same IP address - in fact needed a few admin steps en route; step 16 needed doing at each re-install and I had to re-build a corrupt logger database (as zimbra user, logmysql zimbra_logger and then in mysql REPAIR TABLE raw_logs; where ";" is part of the command). So far so good but about to do a complete machine reboot to check - the zmcontrol start/stop/start series seems OK but I need to be sure before I mark this as solved.