Re: Restoring Database from 4.1 DB files
> additionally if i copy all the <tablename>.FRM, <tablename>.MYD, <tablename>.MYI files into the same location
The MYD and MYI files, plus the corresponding FRM files, are MyISAM tables. They will or won't work thus:
* The tables in the directory (database) "mysql" are for the system (GRANTs, etc), and should probably be tossed. It is probably easier to reissue the GRANTs.
* Tables in other directories (databases) will probably work without issue. (OK, there may have been a change over the years; we can look into it if these are in trouble.)
> the -ib_logfile0, ib_logfile1,
These may or may not cause trouble. You should probably not copy them.
If innodb_log_file_size changed between the installations, the ib_logfiles will not work.
> ibdata1
> the only problem is some of the necessary tables that only have a .FRM cannot be queried
ibdata1, plus any loan .FRM files (and, for those listening in, any .ibd files), make up the the InnoDB tables. You need all of them to recover the files. However, there may have been internal changes that complicate massive version upgrade (as Peter points out).
> <compname>.err, <compname>.pid
Probably toss.
> does not keep listings of the old versions.
What is the oldest version you can find?
TO EVERYONE LISTENING IN...
Do not let your software get more than 5 years old. Upgrade, even if there is no pressing need. Otherwise, you could get stuck in Jake's predicament !
This applies to all software!
And this goes for backup media -- papertape, punched cards, magtape, floppies, zipdrives, CDs, DVDs, SDs, USB sticks, etc -- but 10 years might be feasible. How many of you have a floppies, but no longer have a floppy drive?