[SOLVED] Zimbra 6.0.7 to 7.1.0 - I Cant Upgrade version

[Som30ne]

Hi.

I have just (well, for the last 6 hours) tried to upgrade my ZCS from V6.0.7 to 7.1.0.
At first - it failed because I didnt downgrade my dpkg.
After I did downgrade my dpkg and installed ZCS, mysql.server did not start (something to do with plugins),
so I searched the net and foud that I had to add a few lines to my.cnf.

Now I get the following:

2011-05-07 15:49:31,316 INFO  [main] [] system - Setting mysql connector property: maxActive=100
2011-05-07 15:49:31,339 INFO  [main] [] system - Setting mysql connector property: maxActive=100
2011-05-07 15:49:33,814 ERROR [main] [] Versions - DB Version Mismatch: ours="65" from DB="64"
2011-05-07 15:49:33,814 FATAL [main] [] system - Data version mismatch.  Reinitialize or upgrade the backend data store.

I tried re-installing ZCS 7.1.0 - and got:

Starting MySql... Done
I Can't upgrade version

No version was specified.

I tried downgrading back to 6.0.7 - but got a message that a downgrade is not possible,

--- I dont want to uninstall ZCS, since I dont have a backup, and I dont remember exactly what I changed (I enabeld POP before SMTP, and userd pasword for ISPs mail relay,
and probably some other settings)

How can I do the DB upgrade ?

Thanks

[Som30ne]

Originally Posted by Som30ne

Hi.

I have just (well, for the last 6 hours) tried to upgrade my ZCS from V6.0.7 to 7.1.0.
At first - it failed because I didnt downgrade my dpkg.
After I did downgrade my dpkg and installed ZCS, mysql.server did not start (something to do with plugins),
so I searched the net and foud that I had to add a few lines to my.cnf.

Now I get the following:

2011-05-07 15:49:31,316 INFO  [main] [] system - Setting mysql connector property: maxActive=100
2011-05-07 15:49:31,339 INFO  [main] [] system - Setting mysql connector property: maxActive=100
2011-05-07 15:49:33,814 ERROR [main] [] Versions - DB Version Mismatch: ours="65" from DB="64"
2011-05-07 15:49:33,814 FATAL [main] [] system - Data version mismatch.  Reinitialize or upgrade the backend data store.

I tried re-installing ZCS 7.1.0 - and got:

Starting MySql... Done
I Can't upgrade version

No version was specified.

I tried downgrading back to 6.0.7 - but got a message that a downgrade is not possible,

--- I dont want to uninstall ZCS, since I dont have a backup, and I dont remember exactly what I changed (I enabeld POP before SMTP, and userd pasword for ISPs mail relay,
and probably some other settings)

How can I do the DB upgrade ?

Thanks

Oh, well, I looked a bit more and saw that there are zmsetup.pl, and zmupgrade.pl
I investigared these files, and did a bit messing here and there.

Finally made them to hard-coded identify prevVersion to be 6.0.7_GA.
It upgraded and started working,
but of-course I lost some/most/all (I dont know yet) of my configuration settings.
(didnt seem to lose any mail though - which is a bit of a comfort . . .)

I re-set the pop-before-smtp, and the password protected mail-relay.

Hope that this will end this saga.
(Dont mark it as "solved" just yet)

[phoenix]

Originally Posted by Som30ne

....but of-course I lost some/most/all (I dont know yet) of my configuration settings.

Configuration changes you make are not preserved across upgrades.

Originally Posted by Som30ne

(didnt seem to lose any mail though - which is a bit of a comfort . . .)

There's no reason why you should but at this stage you should have taken a backup of the /opt/zimbra directory structure before continuing the upgrade.

Originally Posted by Som30ne

(Dont mark it as "solved" just yet)

It's you that marks the thread as Solved.

[Som30ne]

Originally Posted by phoenix

Configuration changes you make are not preserved across upgrades.

Really ?
That's very annoying.
(And if I recall correctly, when I upgraded from 6.0.6 to 6.0.7 it saved my settings . . . but maybe Im mistaken)

Originally Posted by phoenix

There's no reason why you should but at this stage you should have taken a backup of the /opt/zimbra directory structure before continuing the upgrade.

Well ofcourse I did by then (only of the zimbra/db/ since that was the problematic area),
but - what good would it have done if It is in the "old" format ? I would still not be able to use it without the conversion, that did not work . . . :-)

Originally Posted by phoenix

It's you that marks the thread as Solved.

Ok, I didnt know that . . .

[phoenix]

Originally Posted by Som30ne

Really ?
That's very annoying.
(And if I recall correctly, when I upgraded from 6.0.6 to 6.0.7 it saved my settings . . . but maybe Im mistaken)

That's always been the case but I'm talking about modifications to configuration files here.

Originally Posted by Som30ne

Well ofcourse I did by then (only of the zimbra/db/ since that was the problematic area),
but - what good would it have done if It is in the "old" format ? I would still not be able to use it without the conversion, that did not work . . . :-)

If you backed up the directory structure I suggested and a disaster happened and you lost some or all of your mail you'd have a backup to recover into a new server.

[Som30ne]

Originally Posted by phoenix

That's always been the case but I'm talking about modifications to configuration files here.

If you say so, Id believe you (My memory is a bit problematic ), and it was a long time ago

Originally Posted by phoenix

If you backed up the directory structure I suggested and a disaster happened and you lost some or all of your mail you'd have a backup to recover into a new server.

But to my understanding - At that stage, I had a mismatching versions of ZCS and it's DB,
so a restore would still bring the mismatching with it - and we get nowhere
(Or am I wrong ? and if so - how ?)

PS
Many Thanks for your reply(s)

[phoenix]

Originally Posted by Som30ne

But to my understanding - At that stage, I had a mismatching versions of ZCS and it's DB,
so a restore would still bring the mismatching with it - and we get nowhere
(Or am I wrong ? and if so - how ?)

First, you did find out how to bypass the problem and continue the upgrade. Second, assuming you were stuck at that stage and lost either the email and/or the database your email is still available in your backup and you can inject that into a new version of Zimbra - it' takes some effort but zmlmtpinject will do it. It depends how important your old email is and whether you wan to preserve it.

[Som30ne]

Originally Posted by phoenix

First, you did find out how to bypass the problem and continue the upgrade. Second, assuming you were stuck at that stage and lost either the email and/or the database your email is still available in your backup and you can inject that into a new version of Zimbra - it' takes some effort but zmlmtpinject will do it. It depends how important your old email is and whether you wan to preserve it.

I overcame the problem, by hacking . . . but - well, that's sort of a way too

I did not know there was a way to import old mail to new installation.
Now I know.

Again - many thanks.

[udfc]

I am having the same problem you described. You said you edited zmsetup.pl and zmupgrade.pl.

Could you share what changes you made. I would like to see if your approach fixes my problems.

Thank You
Alan

[Som30ne]

Originally Posted by udfc

I am having the same problem you described. You said you edited zmsetup.pl and zmupgrade.pl.

Could you share what changes you made. I would like to see if your approach fixes my problems.

Thank You
Alan

Im attaching the modified files here, with ".txt" added to the extension -
since .pl and .pm is not accepted by the server here.
(After modifying - I ran zmsetup.pl)

The diff is (.sav is the original file):

 diff zmsetup.pl zmsetup.pl.sav
122c122
< my $prevVersion = "6.0.7_GA";
---
> my $prevVersion = "";
158d157
< $prevVersion = "6.0.7_GA";

diff zmupgrade.pm zmupgrade.pm.sav
217c217
<   "7.1.0_GA" => \&upgrade607GA,
---
>   "7.1.0_GA" => \&upgrade710GA,
340d339
<     main::progress("Testing start is: $startVersion");
343,344d341
<     $startVersion="6.0.7_GA";
< main::progress("Testing2 start is: $startVersion");
355,358c352
<   my $needMysqlUpgrade = 0;
<
< $startVersion="6.0.7_GA";
<
---
>   my $needMysqlUpgrade = 0;
383,384d376
<
<     main::progress("\nfinally start version is: $startVersion\n");

Hope this helps.

** I take no responsibility as for the outcome
The fact that it worked for me, and did not mess up the DB,
is not a guarantee that it will work for you.