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

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 07-19-2007, 09:31 PM
Intermediate Member
 
Posts: 19
Default Zimbra Version 4.0.4 to Zimbra 4.5.6_GA Migration

Hey Guys,

I have an older server running Version 4.0.4_GA_457.RHEL4 Nov 15, 2006.

I have a new fresh just built server running Version 4.5.6_GA_1044.RHEL4 Jul 6, 2007.

What is the best way to go about moving all settings - server configuration (theme graphics, settings, etc) and also moving all users to the new box.

Unfortunately due to running out of hard drive space on the old server it wasn't possible to 'upgrade' it.

Basically I want to get everyone to the new server and do away with the old - without losing anything.

...Skeeve
Reply With Quote
  #2 (permalink)  
Old 07-19-2007, 09:45 PM
Former Zimbran
 
Posts: 5,606
Default

Do you have custom skins? You'll need to back those up.

Also, what OS are you migrating from/to?

generally, you can just zip up /opt/zimbra and move it over following the wiki instructions.
Reply With Quote
  #3 (permalink)  
Old 07-19-2007, 09:54 PM
Intermediate Member
 
Posts: 19
Default

Quote:
Originally Posted by jholder View Post
Do you have custom skins? You'll need to back those up.

Also, what OS are you migrating from/to?

generally, you can just zip up /opt/zimbra and move it over following the wiki instructions.
Are you serious? I am migrating between different versions, surely I cant just grab /opt/zimbra and move it.

I am going from a CentOS4.5 physical box to a CentOS5 VM Server on very big hardware.

...Skeeve

Last edited by skeeve; 07-19-2007 at 09:56 PM..
Reply With Quote
  #4 (permalink)  
Old 07-19-2007, 10:28 PM
Former Zimbran
 
Posts: 5,606
Default

Yup. Serious.

You'll need to install your old version of zimbra on the new server 1st, then rm it, and move your new one in.

It's very easy. It doesn't come without hiccups tho, but we'll get to those when we get there

more here
Open Source Edition Backup Procedure - ZimbraWiki
Reply With Quote
  #5 (permalink)  
Old 07-19-2007, 10:31 PM
Intermediate Member
 
Posts: 19
Default

Quote:
Originally Posted by jholder View Post
Yup. Serious.

You'll need to install your old version of zimbra on the new server 1st, then rm it, and move your new one in.

It's very easy. It doesn't come without hiccups tho, but we'll get to those when we get there

more here
Open Source Edition Backup Procedure - ZimbraWiki
OK, you missed what I said. I have a new server WITH 456 already installed. And this isnt the open-source version, it's the licensed version.

...Skeeve
Reply With Quote
  #6 (permalink)  
Old 07-19-2007, 10:37 PM
Former Zimbran
 
Posts: 5,606
Default

What did I miss? Do you have people on the new box already?
Reply With Quote
  #7 (permalink)  
Old 07-19-2007, 10:42 PM
Intermediate Member
 
Posts: 19
Default

Quote:
Originally Posted by jholder View Post
What did I miss? Do you have people on the new box already?
You referred me to the Open Source version documents. Unless they are basically the same.

OK. Maybe it isn't clear to me.

But, even though I have built the 4.5.6 server, your suggestion I just delete it - to rebuild the box again? Then just copy across the /opt/zimbra directory. As far as I can see there is mySQL databases as well - unless Zimbra doesn't use them? Then just copying files could be very messy.

Surely there is an easier (less dangerous) migration path/tool to do this.

...Skeeve
Reply With Quote
  #8 (permalink)  
Old 07-19-2007, 10:45 PM
Loyal Member
 
Posts: 94
Default No, thats right

You want to migrate first, then upgrade.
  • Install the exact same 4.0.4 on the new server
  • Rsync the /opt/zimbra over from the old
  • Re-run the 4.0.4 install script on the new server
  • Start up the 4.0.4 on the new server and make sure it's running properly (LDAP, MySql, message store, etc) Really make sure - you don't want to try to upgrade a broken system
  • Shut Zimbra down and then -
  • Then run the install script for 4.5.6
__________________
Brian Harden
www.chromedcomputing.com
Reply With Quote
  #9 (permalink)  
Old 07-19-2007, 10:45 PM
Former Zimbran
 
Posts: 5,606
Default

Ah, I see
So on the network edition, you can backup all the mailboxes.

I did miss the first time that you are on the network edition.

General info is here: Network Edition Backup Procedure - ZimbraWiki

Some considerations should be
1) DNS-make sure that mx records get transferred to the new box.
2) Move over (once you've backed up) the entire /opt/zimbra/backups, if that's where you backed up. If not, move your other location
3) make sure the files are Zimbra user accessable.

and if something goes wrong, let us know

john
Reply With Quote
  #10 (permalink)  
Old 07-19-2007, 10:47 PM
Former Zimbran
 
Posts: 5,606
Default

Quote:
Originally Posted by brained View Post
You want to migrate first, then upgrade.
  • Install the exact same 4.0.4 on the new server
  • Rsync the /opt/zimbra over from the old
  • Re-run the 4.0.4 install script on the new server
  • Start up the 4.0.4 on the new server and make sure it's running properly (LDAP, MySql, message store, etc) Really make sure - you don't want to try to upgrade a broken system
  • Shut Zimbra down and then -
  • Then run the install script for 4.5.6
Brained is 100% correct on the Open Source edition

Some of us (brained included) have assisted in many open source migrations. Forgive us for thinking that's what you have

john
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.