Restore: Problem of Zimbra Version

[victorLeong]

hi everyone,

I have two servers. One is testing server, another is production server. I do a backup on production server. The production server of zimbra version is 3.1.2. Now, I go to the testing server. Then I installed a clean zimbra that the version is 3.1.2. After the installation completed, I stopped zimbra and kill all processes. Copy the backup of production server to testing server and restore on testing server ( two machines have the same setting ). The error appears.

Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.log.9734
Setting defaults...Setting defaults from existing config...Done
Upgrading from 3.1.3_GA_474 to 3.1.2_GA_445
Fri Jul 28 10:04:05 2006: Stopping zimbra services
Fri Jul 28 10:04:09 2006: Checking mysql status
Fri Jul 28 10:04:11 2006: Starting mysql
Fri Jul 28 10:04:12 2006: SELECT value FROM config WHERE name = 'db.version'
Fri Jul 28 10:04:13 2006: Checking logger mysql status
Fri Jul 28 10:04:14 2006: Starting logger mysql
Fri Jul 28 10:04:16 2006: SELECT value FROM config WHERE name = 'db.version'
I can't upgrade version 3.1.3_GA

However, I used 3.1.3 install package to do the restore on testing server, it did not have any errors.

What's the problem?

[jholder]

Upgrading from 3.1.3_GA_474 to 3.1.2_GA_445

From the log (I often don't read all the way), but it looks like the DB is 3.1.3.

It is STRONGLY not advised you downgrade. It's entirely possible you could break everything.

Rather than using the 3.1.2 package, just use the 3.1.3 or higher.

I would reccomend you upgrade your production server to 3.1.4. Here's a summary of the fix levels:
3.1.4 Major bugfixes 27-Jun-2006 23:55
3.1.3 Minor bugfixes 13-Jun-2006 13:43
3.1.2 Major bugfixes 31-May-2006 17:12
3.1.1 Major bugfixes 11-May-2006 21:36

[victorLeong]

Upgrading from 3.1.3_GA_474 to 3.1.2_GA_445

From the log (I often don't read all the way), but it looks like the DB is 3.1.3.

It is STRONGLY not advised you downgrade. It's entirely possible you could break everything.

Rather than using the 3.1.2 package, just use the 3.1.3 or higher.

I would reccomend you upgrade your production server to 3.1.4. Here's a summary of the fix levels:
3.1.4 Major bugfixes 27-Jun-2006 23:55
3.1.3 Minor bugfixes 13-Jun-2006 13:43
3.1.2 Major bugfixes 31-May-2006 17:12
3.1.1 Major bugfixes 11-May-2006 21:36

Thanks you

Why the db version change to 3.1.3?

[jholder]

Not quite sure. There is nothing in bugzilla either opened or closed.

The most likely cause would be a failed/aborted install

Your best bet is to simply install 3.1.3_GA_474

jh