Wow, this is definitely a strike against the Chuck-beloved FrontBase!
In MySQL, the dump is a text SQL file with table create statements, data insert statements etc ..... it even puts conditional comments around features that MySQL version specific so that those are ignored by old versions that cannot handle those features. So essentially a typical (there are multiple ways to dump/backup btw) MySQL dump is platform, Operating System, CPU brand/arch and MySQL version agnostic ..... kind of important when dealing with BACKUPS I think ;-) ...... or even moving your database to another server with different OS and hardware.
Regards, Kieran
On Sep 28, 2010, at 10:39 AM, John Huss wrote: You have to restore it on exactly the same version of FrontBase that was used to back it up AND it must be the same architexture - if the backup was from 32-bit frontbase you cannot restore it with the 64-bit executable.
John On Tue, Sep 28, 2010 at 9:13 AM, David Avendasora <email@hidden> wrote:
Things just get stranger and strangerer, apparently the backup was pulled from an Intel server, and the only thing that Google comes back with when searching on Frontbase and the "Wrong magic number - not a backup file" message is Flor's post I linked to below.
Dave
|