Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-07-2008, 08:08 AM
Moderator
 
Posts: 1,209
Default Problem With Moving ZCS to New Server

We are trying to move Zimbra from one server running 4.5.11NE on SLES9 to another server running 4.5.11NE on 64-bit SLES10.

We followed the instructions in John Holder's blog, and also did the LDAP export/import procedure.

The import of the ldif file on the new server generated the error:
Warning - No DB_CONFIG file found in directory /opt/zimbra/openldap-data: (2)
Expect poor performance for suffix .

This error repeated when we ran the ZCS installer after the ldif import.

The ZCS installer then failed at the end with:
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...Restoring backup schedule...done
Can't load '/opt/zimbra/zimbramon/lib/i586-linux-thread-multi/auto/DBI/DBI.so' for module DBI: /opt/zimbra/zimbramon/lib/i586-linux-thread-multi/auto/DBI/DBI.so: wrong ELF class: ELFCLASS32 at /usr/lib/perl5/5.8.8/x86_64-linux-thread-multi/DynaLoader.pm line 230, line 228.
at /opt/zimbra/zimbramon/lib/i586-linux-thread-multi/DBI.pm line 266
BEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/i586-linux-thread-multi/DBI.pm line 266, line 228.
Compilation failed in require at /opt/zimbra/libexec/scripts/Migrate.pm line 18, line 228.
BEGIN failed--compilation aborted at /opt/zimbra/libexec/scripts/Migrate.pm line 18, line 228.
Compilation failed in require at /opt/zimbra/libexec/zmupgrade.pm line 21, line 228.
BEGIN failed--compilation aborted at /opt/zimbra/libexec/zmupgrade.pm line 21, line 228.
Compilation failed in require at /opt/zimbra/libexec/zmsetup.pl line 59, line 228.
BEGIN failed--compilation aborted at /opt/zimbra/libexec/zmsetup.pl line 59, line 228.


Any ideas?

Thanks!
Mark
__________________
___________________________________
L. Mark Stone, CIO


"Uptime. All the time."

477 Congress Street | Portland, ME 04101-3431 | (207) 772-5678

proactive maintenance and monitoring | technology consulting
Zimbra groupware | EMR implementations | private cloud hosting
Reply With Quote
  #2 (permalink)  
Old 03-10-2008, 09:00 PM
Former Zimbran
 
Posts: 5,606
Default

John Holder? You followed that quack's instructions?

So moving to 64 bit is a bit tougher. You must dump ldap before moving.
Then import it into your dummy install.
Then move /opt/zimbra/openldap-data from the dummy install to somewhere safe
Then copy your backup over the /opt/zimbra
Then copy your "new" openldap-data into /opt/zimbra
Then run ./install.sh

(Sorry it took so long to reply, PM me if you need more help)
Reply With Quote
  #3 (permalink)  
Old 03-11-2008, 06:08 AM
Moderator
 
Posts: 1,209
Default

Quote:
Originally Posted by jholder View Post
John Holder? You followed that quack's instructions?

So moving to 64 bit is a bit tougher. You must dump ldap before moving.
Then import it into your dummy install.
Then move /opt/zimbra/openldap-data from the dummy install to somewhere safe
Then copy your backup over the /opt/zimbra
Then copy your "new" openldap-data into /opt/zimbra
Then run ./install.sh

(Sorry it took so long to reply, PM me if you need more help)
Ah! The wiki article on exporting/importing ldap data I understood to say to delete on the new machine the contents of /opt/zimbra/openldap-data before doing the import.

So, you are saying I think that we should:
  1. Run install.sh -s on new machine
  2. Import the ldif file into this dummy install
  3. Copy on the new machine /opt/zimbra/openldap-data someplace safe
  4. Replace the entire /opt/zimbra tree on the new server with the /opt/zimbra tree from the old 32-bit server
  5. On the new server, now replace the contents of the /opt/zimbra/openldap-data directory (which now has data from the 32-bit server) with the new server contents we previously copied to a safe place in step 3 above
  6. Run ./install.sh with no options to perform an "upgrade".

We'll try that and see how it goes!

Thanks John!

All the best,
Mark

P.S. We have a ticket open with A. Cody on this one. I'll update the ticket once I try the above steps towards the end of the day.
__________________
___________________________________
L. Mark Stone, CIO


"Uptime. All the time."

477 Congress Street | Portland, ME 04101-3431 | (207) 772-5678

proactive maintenance and monitoring | technology consulting
Zimbra groupware | EMR implementations | private cloud hosting
Reply With Quote
  #4 (permalink)  
Old 03-11-2008, 09:34 AM
Former Zimbran
 
Posts: 5,606
Default

Yep, that's right.

I like to make things as complicated as possible, adding many many steps.

Good luck,
john
Reply With Quote
  #5 (permalink)  
Old 03-11-2008, 10:46 AM
Active Member
 
Posts: 48
Default 32 bit to 64 bit

Looks like I posted pretty much the same question right after you lol. I was wondering about the import of the ldap. Do I copy over the slapd.conf and the DB_CONFIG files from the old server also. Because doing an ./install.sh -s doesn't install these files and when I run /opt/zimbra/openldap/sbin/slapadd -f /opt/zimbra/conf/slapd.conf -cv < /backup/ldap.bak to restore ldap of course it is missing the slapd.conf. Any help is appreciated.
Reply With Quote
  #6 (permalink)  
Old 03-11-2008, 10:46 AM
Former Zimbran
 
Posts: 5,606
Default

wiki is too complicated. Try this:
http://www.zimbra.com/blog/archives/...ap_data_1.html
Reply With Quote
  #7 (permalink)  
Old 03-11-2008, 10:57 AM
Moderator
 
Posts: 1,209
Default

Quote:
Originally Posted by jholder View Post
But John...

That article says to delete the contents of /opt/zimbra/openldap-data and if I understood you correctly, that's what got me into trouble.

Please clarify!

Thanks oh wise Zimbra sensei... (hey, your avatar looks very pensive so I thought I should sign off with something appropriate...)

Mark
__________________
___________________________________
L. Mark Stone, CIO


"Uptime. All the time."

477 Congress Street | Portland, ME 04101-3431 | (207) 772-5678

proactive maintenance and monitoring | technology consulting
Zimbra groupware | EMR implementations | private cloud hosting
Reply With Quote
  #8 (permalink)  
Old 03-11-2008, 10:59 AM
Former Zimbran
 
Posts: 5,606
Default

haha

Follow the "dumping ldap to disk" part only. You just want to get the ldif file. Then refer to the other instructions.
Reply With Quote
  #9 (permalink)  
Old 03-11-2008, 11:11 AM
Moderator
 
Posts: 1,209
Default

Hi John,

Something is not quite right here...

On the new 64-bit server, if I run ./install.sh -s, there is nothing in the /opt/zimbra/openldap-data directory.

If I then try to import the ldif file created from the 32-bit server, I get the error about the missing CONFIG file (which is accurate), and the subsequent running of ./install.sh as an upgrade fails as described in a previous post.

Now, if after running ./install.sh -s on the new server I instead copy over /opt/zimbra from the 32-bit server to the 64-bit server to populate (among other things) the /opt/zimbra/openldap-data directory, then when I go to import the ldif file created from the 32-bit server, I get lots of errors that all those keys are already in there.

IOW:
1. ./install.sh -s + import ldif = missing ldap CONFIG error.

2. ./install.sh -s + overwrite /opt/zimbra + import ldif = ldap import failures.

Is any of this making sense?

Thanks!
Mark
__________________
___________________________________
L. Mark Stone, CIO


"Uptime. All the time."

477 Congress Street | Portland, ME 04101-3431 | (207) 772-5678

proactive maintenance and monitoring | technology consulting
Zimbra groupware | EMR implementations | private cloud hosting
Reply With Quote
  #10 (permalink)  
Old 03-11-2008, 11:21 AM
Former Zimbran
 
Posts: 5,606
Default

Okay sorry. My fault. Here's a quick once over

1) Backup working zimbra
2) Dump ldap to disk using wiki page (create ldif file)
3) stop running zimbra, shut down machine
4) bring up new machine with same hostname, same IP doesn't matter as long is DNS is redirecting
5) install current version of zimbra with new flavor for OS. Go through entire setup (ie don't use ./install.sh -s, just./install.sh)
6) wipe /opt/zimbra/openldap-data
7) Import ldif file using wiki page
8) Move /opt/zimbra/openldap-data dir to safe local
9) replace /opt/zimbra with backup
10) Move openldap-data dir into place (/opt/zimbra/openldap-data)
11) run ./install.sh -s
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.