> Message: 8 > Date: Mon, 11 Feb 2013 17:42:53 -0500 > From: Phil Stracchino <ala...@metrocast.net> > Subject: Re: [Bacula-users] Corrupted catalog on bad drive - please > help!
<snip> > > MyISAM-table 'File.MYI' is not fixed because of errors > > > > Try fixing it by using the --safe-recover (-o), the --force (-f) option > > or by not using the --quick (-q) flag" > > Without belaboring the point too much, MyISAM is an obsolete, legacy > storage engine that does not scale to modern systems or database sizes, > is not robust, cannot be backed up without locking tables, has no crash > recovery to speak of, and should not be in use in production databases. > Pretty much the only reason it has not been deprecated is because > Oracle has not yet been able to remove all of the dependencies in MySQL > upon MyISAM for the grant tables. The odds are as soon as MySQL can use > InnoDB to store its grant tables (probably in 6.0), MyISAM will be > deprecated. > > > If you suspect hard (as in unrecoverable) disk errors, my advice would > be to replace the disk, recreate your DBs using InnoDB tables, properly > retune MySQL for InnoDB, then rebuild your catalog using bscan. > > (You might also update to a current MySQL version while you're at it. > I'm guessing you probably have, at best, MySQL 5.0.95. 5.0 was EOL'd in > 2011, 5.1 will be EOL'd this year, current most recent versions are > 5.5.30 and 5.6.10.) Thanks Phil. Yes, once I get things recovered I'd like to update the whole system. Although it sounds like I could update the bacula server and then rebuild the catalog anyway with bscan - good to know. -M ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
