Zimbra Migration Strategy

[Sir Bob]

Hello,

This probably should have been in the Migration section of the forums. My apologies. As I'm fairly new to Zimbra and am unable to find a thread that defines my problem, I'm creating my own.

My Problem:
We currently have a server running Zimbra 5.0.4 (opensource) on Suse 10.2. Our goal is to upgrade the server to 5.0.14 then migrate the server onto a new O/S (CentOS 5.3). Currently, I am experimenting in our lab with the migration and have run into a problem.

The initial server has hostname of mail1.geekdept.com. Following a document on migration from one server to another, this is what I have done:
1. built the original server (suse10.2) and installed zimbra (5.0.14), created a few accounts and sent a few emails (just for data)
2. built the new server to migrate to (CentOS 5.3). This server has the same hostname and network settings as the original one. After shutting Zimbra down on the original server, I have changed the hostname to mail.geekdept.com as well as the IP.
3. on the new server, installed zimbra with the -s option, removed the /opt/zimbra directory then rsynced the original /opt/zimbra directory into place
4. ran the zmfixperms command for permissions
5. re-ran the zimbra install (without the -s option)

All DNS settings are correct.

On the new server, I can get all the services running and it appears to be functional, but when I try to open the log in screen, I get an error as follows:

HTTP Error 404
Not_Found
RequestURl=/

When I go back to the original server and change the hostname and IP back to its original settings, the login page displays no problem.

I guess the problem is that the web page can connect to mail1.geekdept.com, but is unable to find the correct file for the web page.

Any ideas on where to look?

Thanks
Sir Bob

[phoenix]

You should change the server name with the command: zmsetservername

[Sir Bob]

Hello and thank you for the quick response.

I don't quite see how using the zmsetservname command will solve my problem though. The original server was given the name mail1. The new server to be migrated to was also given the same hostname. The only time that the hostname was changed was on the original server after Zimbra was installed and configured and even then, it was only changed after Zimbra was stopped (just to get it out of the way so to speak). The new server that things were migrated to has not had its hostname changed and wears the hostname of the original server.

Moving the /opt/zimbra directory on to the new server, setting permissions and reinstalling Zimbra should have worked, should it not? All DNS is working correctly in that if you dig mail1.geekdept.com, it directs me to the new server.

Sir Bob

[phoenix]

Sorry, I must have misunderstood your first post (I assume you installed the same version of Zimbra on the new server and they're both 32bit systems?). On the new server run the following command and post the output:

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname`  <--thype that command exactly and use backticks not single quotes

[Sir Bob]

Hello,

Yes, I have installed the same version of Zimbra and they are both on 32 bit systems. The original server was mail1 with an IP of 10.2.46.154, but after changed to mail and 10.2.46.156 (and hosts DNS). The new server has mail1 and 10.2.46.154. The info you requested is as below:

cat /etc/resolve.conf

search geekdept.com
nameserver 10.2.46.156

cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
10.2.46.154 mail1.geekdept.com mail1

dig geekdept.com mx
; <<>> DiG 9.3.4-P1 <<>> geekdept.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64674
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; QUESTION SECTION:
;geekdept.com. IN MX

;; ANSWER SECTION:
geekdept.com. 172800 IN MX 10 mail1.geekdept.com.

;; AUTHORITY SECTION:
geekdept.com. 172800 IN NS mail.geekdept.com.

;; ADDITIONAL SECTION:
mail1.geekdept.com. 172800 IN A 10.2.46.154
mail.geekdept.com. 172800 IN A 10.2.46.156

;; Query time: 1 msec
;; SERVER: 10.2.46.156#53(10.2.46.156)
;; WHEN: Wed Jun 17 10:03:34 2009
;; MSG SIZE rcvd: 103

dig geekdept.com any
; <<>> DiG 9.3.4-P1 <<>> geekdept.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5515
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;geekdept.com. IN ANY

;; ANSWER SECTION:
geekdept.com. 172800 IN SOA mail.geekdept.com. root.mail.geekdept.com. 2009061100 10800 3600 604800 86400
geekdept.com. 172800 IN NS mail.geekdept.com.
geekdept.com. 172800 IN MX 10 mail1.geekdept.com.

;; ADDITIONAL SECTION:
mail.geekdept.com. 172800 IN A 10.2.46.156
mail1.geekdept.com. 172800 IN A 10.2.46.154

;; Query time: 1 msec
;; SERVER: 10.2.46.156#53(10.2.46.156)
;; WHEN: Wed Jun 17 10:03:40 2009
;; MSG SIZE rcvd: 144

host `hostname`
mail1.geekdept.com has address 10.2.46.154