Hi, It is not very surprising that the database cannot recover from a Time Machine backup. This generally applies to any software that is running at the moment the backup is taken. The InnoDB is especially sensitive to taking what is called a 'dirty' backup because it has a cache. You may get some luck with innodb_force_recovery. Either way, it is going to be unpleasant experience best avoided by mysql-specific backup strategy.
Peace Karen. On 09.01.2013, at 7:33, Jan Steinman wrote: > I accidentally dropped a crucial database. My only backup is via Apple's Time > Machine. > > First, I stopped mysqld and copied (via tar) the database in question from > the backup. Restarted, but drat -- most of the tables were apparently using > innodb's ibdata1 file, as only the MyISAM tables showed up in phpMyAdmin. > > I copied the ibdata1, but then mysqld wouldn't start, complaining about no > mysql.sock, which was odd, because it was there. > > I then copied (via tar) the entire set of all databases, but am still having > problems, I think related to Time Machine's ACL lists and extended attributes. > > Anyone have experience and wise words on restoring a database from Time > Machine? > > Thanks! > > ---------------- > :::: Books are associated with communities of writers, printers, proofreaders > and a host of other people with whom the writer interacts... Granted, there > are some websites that provide well written and researched articles and > information. Unfortunately, many are not. The Internet may be more of a time > using machine than TV. And its usage is not always positive. -- Pat Murphy > :::: Jan Steinman, EcoReality Co-op :::: > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
