Under the guidance of Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki I attempted to move from 32bit to 64bit FOSS version 7 on Ubuntu.
This will be good for all I think. Doing it, albeit 1 pass closer to success brought up quite a few process and clarity question. My hope is that I can get this sorted out, go at it again next Sunday and post something very streamlined and precise without vagueness and appealing to the true newbie.
First of, I suppose I goofed by trying to go from FOSS version 7 32 bit Ubuntu 8 LTS to FOSS version 7 Ubuntu 10 LTS. Is the process so strict that I can only go from Ubuntu 8 LTS 32-bit to Ubuntu 8 LTS 64-bit ?
The guide did say "The ZCS installation on the new server must be configured exactly as the ZCS configuration on the original server. You go through the complete menu driven installation process, making changes to the configuration setting to match the settings on the original server."
Here's goes the list of questions that pertains to exactly. How exact are we talking.
1. must it be same Ubuntu 8 LTS 32-bit to Ubuntu 8 LTS 64-bit
I'm assuming I couldn't go to 10 LTS because I failed.
2. can you use a different local ip ? 32-bit was setup on 10.168.8.1 and because I wanted to be fast and not switch IPs, I just went with 64-bit on 10.168.8.8. Does that matter ?
3. in 32bit FOSS 7 I had a wiki account. In 64bit setup there was no wiki account via the install for me to overwrite the way I did the ham and spam accounts. I dunno how to make system accounts. Was this why things failed ?
Another question about accounts and being exact. On the new 64bit install, was I to create the 27 accounts that were present in my 32bit FOSS 7 ? I figured during the process somewhere accounts and such would be copied over. So, am I to create all the accounts as well ?
4. When doing the new 64-bit server the guide says " making changes to the configuration setting to match the settings on the original server "
When I do my install, I then login and set the default COS to my liking, deploy zimlets, do a bunch of other stuff so Zimbra will relay outgoing mail via my ISP, adjust some global settings, and then I create all accounts.
Is this the type of configuration that's meant to be done on the new server ? Heck was so long ago when I did 32bit settings I forgot by now. Please say it ain't so. Let me know what's meant by that ?
5. what does this mean ?
Zimbra LDAP Server - For Domain to create - identify the same default domain as on the original server
Is this just saying use the same domain name ?
6. What does this mean ?
Global Document Account - This account name is automatically generated. Change the Global Document Account name to be the same account name as on the original server.
I assumed that to be the wiki account.
Hell, I never had one in my 10 LTS install
One was present on FOSS 7 LTS 8
What's the right thing to do ? Create it like I did in 10 LTS ?
Leave it out ?
7. Ahh, I love this one.
Change any other settings on the new server to match the configuration on the original server.
For newbies, what or where is that referring to "
Seems vague to me.
8. This whole section of the guide as shown below doesn't tell us to make a /backup folder until we encounter a copy from that location. Also here's where I ran into problems getting info off the old server to the new.
I tell you, getting the files off the 32bit machine over to the 64bit machine is cumbersome. I used scp as root to an equivalent directory with all permissions like /temp. So I copy first from 32bit to 64bit as root using scp to a temp area. Real cumbersome.
Is it okay to tar up the entire /opt directory and move it over to the 64 bit server and work with it there ? Is so that would make it easier to get to the files you need and less problems.
6.0.x and later LDAP setup:
1. Restore the LDAP data to the 64-bit server. As zimbra, type
a. rm -rf /opt/zimbra/data/ldap/hdb/*
b. If this is an ldap master with replicas: rm -rf /opt/zimbra/data/ldap/accesslog/*
c. mkdir -p /opt/zimbra/data/ldap/hdb/db /opt/zimbra/data/ldap/hdb/logs
d. If this is an ldap master with replicas: mkdir -p /opt/zimbra/data/ldap/accesslog/db /opt/zimbra/data/accesslog/logs
e. Copy the file /opt/zimbra/data/ldap/hdb/db/DB_CONFIG from the 32-bit server to /opt/zimbra/data/ldap/hdb/db on the 64-bit server. Note: If this file does not exist, or is empty, creating it may improve ldap performance; see the Performance Tuning Guide for more information.
f. Type chown -R zimbra:zimbra /opt/zimbra/data/ldap
g. Copy from the 32-bit server to the 64-bit server the /backup/ldap.bak file.
h. Type /opt/zimbra/openldap/sbin/slapadd -q -b "" -F /opt/zimbra/data/ldap/config -cv -l /backup/ldap.bak.
9. The localconfig.xml file
Under my situation zimbra_logger_mysql_password entry was never there.
Neither was mailboxd_keystore_base_password
Is this okay ? Is this a flag that I have bigger problems ?
Should this not be anything to worry about ?
10. The guide says :
Copy the following files from the 32-bit server to the 64-bit server
* Any other volumes that were set up on the 32-bit server such as HSM.
What's mean by Any other volumes that were setup ?
What is HSM ?
I can relate to a directory path with files.
When you get vague and say any other volumes, now you're asking me to know what's up and what's meant by that. What am I to have or look for ?
I don't know, at least not this first time.
11. How about some advise on what to check.
When my system failed due to mailbox notable to start, as I saw from zmcontrol status I abandoned ship. Knowing what log files to get an idea would be nice. I might have been doomed because of any number of the previous items, but it's nice to have something definitive to check.
So, who can set me straight, so I can get at this again next Sunday and be successful ? If I hit I know I can writeup a good enough detailed guide so real newbies can be successful.
Please help and thanks in advance.