[one-users] what's the best way to deal with "Database version mismatch" after upgrading

[Héctor Sanjuán]

Hi Shi Jin,

> it there a better way to update the database
> structure so that we don't lose all the data already in it? Thanks.

I'm afraid there is not a straightforward way to do that. It is a
consequence of the heavy development efforts we are carrying towards 3.0
Iris release. The closer we are to the stable release the less this and
other problems will happen.

Also, I'd like to remind that there will be an upgrade tool (onedb)
which will take care of the 2.2 -> 3.0 migration process.

Still, thanks a lot for testing on master and sorry for the annoyances.

Hector

El 12/07/11 19:05, Shi Jin escribió:
> Hi there,
> 
> I am testing the latest git code. Whenever I pull the latest code and
> build a new OpenNebula master code, I am no longer able to run on the
> old database since I get the "Database version mismatch.oned failed to
> start" error.
> Since I am testing, it is not a big deal to cleanup the database to
> start over. However, it there a better way to update the database
> structure so that we don't lose all the data already in it? Thanks.
> 
> Shi
> 
> -- 
> Shi Jin, Ph.D.
> 
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org


-- 
Héctor Sanjuán
OpenNebula Sunstone Developer