Openbravo Issue Tracking System - Openbravo Deployment Options
View Issue Details
0004318Openbravo Deployment OptionsAppliance rPathpublic2008-07-04 10:312015-02-13 20:13
pjuvara 
gorka_gil 
normalminorhave not tried
closedout of date 
5
 
2.40 
0004318: Validate consistency of configuration before backup recovery
Once users have updated Openbravo to a new revision, they should not be able to recover the database from an earlier version.

The system should check that the backup was done from the same version as the current system.
Sprint-1
Issue History
2008-07-04 10:31pjuvaraNew Issue
2008-07-04 10:46pjuvaraStatusnew => scheduled
2008-07-04 10:46pjuvarafix_in_branch => trunk
2008-07-04 10:52pjuvaraTarget Version => 2.40
2008-08-29 09:29pjuvaraAssigned To => jpabloae
2008-08-29 13:44pjuvaraTag Attached: Sprint-1
2008-09-11 16:40psarobeNote Added: 0009004
2008-10-22 11:06jaimetorreStatusscheduled => resolved
2008-10-22 11:06jaimetorreResolutionopen => fixed
2008-10-30 19:56jpabloaeCategory => SMB Network One
2008-11-13 13:40jpabloaeFixed in Version => 2.40
2008-12-22 19:13pjuvaraStatusresolved => closed
2009-01-23 18:27pjuvaraStatusclosed => new
2009-01-23 18:27pjuvaraResolutionfixed => open
2009-01-23 18:27pjuvaraFixed in Version2.40 =>
2009-01-23 18:27pjuvaraStatusnew => acknowledged
2011-08-24 12:58jpabloaeAssigned Tojpabloae => gorka_gil
2012-07-19 13:11gorka_gilCategoryAppliance stack => Appliance rPath
2015-02-13 20:13shuehnerStatusacknowledged => scheduled
2015-02-13 20:13shuehnerNote Added: 0074471
2015-02-13 20:13shuehnerStatusscheduled => closed
2015-02-13 20:13shuehnerResolutionopen => out of date

Notes
(0009004)
psarobe   
2008-09-11 16:40   
Additionally the name of the backup should be more intuitive otherwise you don't know from which patch that backup was made from

Currently the name is for example like this backup-20080911-1607-CEST.tar
(0074471)
shuehner   
2015-02-13 20:13   
This issue only applies to the old rPath Appliance which is not longer supported for a long time already.