On Thu, 2008-10-30 at 17:12 -0400, Damian Krzeminski wrote: > Martin Steinmann wrote: > > We currently do not allow a backup taken with a specific release to be > > restored with a later release of the sipXecs software. What would it > > mean if we required this to be possible? > > > > [...] > > This is what I was thinking: sipXconfig is set up to upgrade its database > every times it starts (only if necessary of course). This is different from > all the other components that only upgrade their data when new version is > installed (that why upgrade works and restore from the older backup does not.) > > So if everything was in sipXconfig database (and only there) we could > restore it and sipXconfig would upgrade everything. In 3.11 we already > moved quite a bit of information into sipXconfig database and before 4.0 > release we will move even more. > > Once it completed we can spend some time tracking down the things that > cannot be in the sipXconfig database and make sure that they are > upgradeable...
All of which means that post-4.0 there is some hope of supporting restore from any 4.0 or later release (some work required, but probably reasonable). Supporting restore from any backup made by a version less than 4.0 is much much harder because "the configuration" is not all in the database. This is just one of the motivations for the big effort we've made for 4.0 to centralize the configuration into the database. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
