james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Charles <e...@apache.org>
Subject Re: James upgrade database issues
Date Mon, 25 Jul 2011 13:35:02 GMT

The web site we have to deploy documents this.
You can read in preview the proposed procedure on 

The idea is to copy the old database to maildir, and then recopy back 
the maildir to the new database.

Hope you can find your way.

On 25/07/11 14:49, Saibabu Vallurupalli wrote:
> Hi Team, Good morning.
> I have completed upgrade successfully using new James database from
> 3.0-M3-SNAPSHOT to 3.0-beta2 release. During this upgrade process I tried to
> use existing database and I wasn't successful then I have take backup of
> existing database and create a new James database.
> Now, I wanted to restore the MySQL database which I have taken backup and
> trying to figure out what the differences are going to be.
> Is there any better way I can handle this upgrade without having much impact
> on database? How do I know the changes to Database from 3.0-M3-SNAPSHOT and
> 3.0-beta2?
> Please advise.
> Thanks,
> Sai

Eric Charles

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message