|
Hi, http://track.sipfoundry.org/browse/XX-7870 (Config UI should not allow to restore when voicemail & configuration files are interchanged) says that if wrong archives are uploaded the application is rendered into a wrong state, unrecoverable. After some discussions we came up with the idea of making some checks on the archives. One of the checks could be to verify the presence of the database archive: we can safely assume that the configuration archive has the database archive, and the voicemail does not. (Basically we *should not* proceed with configuration restore if the configuration archive is not valid, since this would imply dropping the DB and rendering the application useless.) There is already a --verify option on the restore script. We can add the sanity check to the current verification that is already done: - script running from sipXconfig: -e and --verify options are passed automatically and the application will exit with an error code if version is wrong or archive is wrong; script will exit with code 0 if verification succeeds - sipXconfig proceeds then with the restore - script running from command line without the -e or --verify options: script will exit with error code 7 if archives are wrong; script will continue with restore if everything is ok A further improvement (most probably we'll open an improvement issue for this) would be to check the validity of the files paths. Thoughts, comments? Regards, Cristi S. |
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
