Agreed. I found myself on the end of that once when a 3.10 patch was posted that didn't support FC6 but it applied anyway. In my case the DB had updated, so I did the backup and wiped the system, and was able to restore.
Should there be a mechanism in the restore to determine the DB schema version and then process it to the current version supported by the platform the restore is being applied to? >>> "Martin Steinmann" <[EMAIL PROTECTED]> 10/30/08 4:47 PM >>>We currently do >>> not allow a backup taken with a specificrelease to be restored with a later >>> release of the sipXecs software. What wouldit mean if we required this to >>> be possible?<o:p></o:p> <o:p> </o:p> This would give us a much smoother upgrade strategy,especially in cases where the OS needs to be upgraded as well (i.e. CentOS 4 toCentOS 5).<o:p></o:p> <o:p> </o:p> Could someone please explain what the obstacles are?<o:p></o:p> --martin<o:p></o:p> <o:p> </o:p> </[EMAIL PROTECTED]>
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
