I have been working on this for two weeks and have it down pretty well. I started this as a test before migrating to a new server and found it didn't work well. After much practice it does work with some additional steps. I followed the wiki for Disaster recovery.
A couple of things:
when moving to a new server simple add a hostfile entry on the new server for the new IP. The install will bark that the MX is wrong, but it will still work. This way you can actually test while your existing server is up and not deal with any DNS changes. It works.
Also, the wiki mentioned turing off auto start and backups. If you do that, some of the zimlets (for backup and restore) won't initialize.
Also, you will notice many mentions by people that the logging doesnt work during the zmrestoreoffline. If, during the initial install you DO start and then stop the server, it does fix this problem and the mailbox.log will be created properly. What you will do is install a fresh ZCS. Then start it with zmcontrol start. Then zmcontrol stop. After that continue with the install and remove the database contents with rm -rf /opt/zimbra/db/data/* then reinitialize with /opt/zimbra/libexec/zmmyinit. and continue.
Before executing the procedure, you can get your ldap passwords with the zmlocalconfig -s. Then you can place those in during the initial config. Dont change all the passwords, just the ones listed for ldap. Later in the procedure you are asked for zimbra_ldap_password. You'll need to init it also.
Lastly, after you have restored, you may log in and see your mail. If you try to send it will issue an MTA error. You can continue to utilize the new IP by adding it to the trusted networks of the new server. zmprov getServer <servername> | grep zimbaMtaMyNetworks to get the exsiting and zmprov modifyServer <server> zimbraMtaMyNetworks "ip addreses"
I have not documented any of this. I've just done it like 60 times in the last two weeks and have this procedure memorized now.
Last edited by tecnalb; 10-08-2008 at 08:01 AM..
|