Why the whole forum database should be parsed to begin with? If backup is setup incremental style, only these changes to the DB after recent forum soft update need parsing. The parsing process is not error proof either, so incremental backup seems to be a preferred solution.
...or maybe use differencing .vhd's....
You are missing what the actual issue is about. (Because there are several different ones).
The one I was talking about is the one that you were hit by recently
The "old" database, created by the "old" version of the Board software was saved with a given, compatible with the "old" board software format.
Then upon install of the "stupid new" board software
- the pre-existing database records are NOT parsed correctly by the "stupid new" board software
- the "old" database contents were imported by the "stupid new" board software using it's own "stupid new" importing feature into a "stupid new" database with it's own "stupid new" format
In both cases there is nothing connected with differential vs. full backup methods.
The "stupid new" board software cannot read properly the converted or imported pre-existing data.
This happens a lot of times in the actual "real world" of business when a program is changed, I have several experiences (nightmare ones) with re-importing COBOL originated "fixed size" and "delimited" data from old programs to new ones (by ANOTHER software house, using a totally different data format), this is "normal" what is Abby Normal:http://www.imdb.com/...uotes?qt0504329
in this case is that we are talking of a new version of the SAME software, written by the SAME Software House