Tim,

If I try to restore a backup that has a different table or catalog version number from the
current version then I receive a "Version mismatch" error.

The way I have been dealing with this is to drop the database, answer NO to the question
"Do you want to keep the contents of the database?"   Then create a new database with the
same name and restore the database.

Is this the right way to handle this situation?  Am I missing something?

(Installed v1.07b2 - it fixed my AV when using an index with a computed field - thank you)

Richard Harding

Richard,

<< If I try to restore a backup that has a different table or catalog
version number from the current version then I receive a "Version mismatch"
error. >>

Are you talking about restoring an older version of the backup/catalog with
a newer version of EDB, or the other way around ?  It makes a difference,
because older to newer should work, while newer to older will not work.

--
Tim Young
Elevate Software
www.elevatesoft.com

>>Are you talking about restoring an older version of the backup/catalog with
a newer version of EDB, or the other way around ?  It makes a difference,
because older to newer should work, while newer to older will not work.

===================
Tim,

I have created a DB with 1 table.  Backed it up and called it "backup v1".
Added a column to the table.  Backed it up and called it "backup v2".
Tried to restore "backup 1" with the restore catalog option checked.  This gave a version
mismatch which is to be expected because it is going back to an older version of the table.

Deleted the database, removing the tables.
Created a new database.
Restored "backup 1".
Tried to restore "backup 2" with the restore catalog option checked.  This too gave a
version mismatch.


Is the version of EDB (for example, v1.07) relevant to restoring?

Richard Harding

Richard,

Thanks for the specifics.  It's a bug - the restore is running into an issue
where it's trying to open the old version of the table using the
newly-restored catalog, hence the error.  A fix will be available today or
tomorrow that will correct this, and it won't involve any changes to any
existing backups.  The fix is simply for ElevateDB to backup the existing
table files to .old versions and creating a new version of the table that
matches the older catalog.

--
Tim Young
Elevate Software
www.elevatesoft.com