From: Rayner, J. <ra...@ei...> - 2013-02-15 19:28:57
|
Thanks Demain! We're planning at test next week, and we'll send any lessons learned back to the list. Regards June From: Demian Katz [mailto:dem...@vi...] Sent: Friday, February 15, 2013 2:07 PM To: Rayner, June; vuf...@li... Subject: RE: VuFind Database Recovery procedures I think that plan should work. Worst case scenario, if things didn't work directly from the restored backup, you could probably remove and reinstall the MySQL package prior to running mysqldump to ensure that bad data was eliminated. I don't have personal experience trying this, though, so I'm only speaking theoretically -- if anyone else has practical advice, perhaps they will share it (though perhaps we're all lucky enough to have never been placed in this position). A little bit of Googling turned up this page, which has some details that might be helpful: http://stackoverflow.com/questions/484750/restoring-mysql-database-from-physical-files - Demian ________________________________ From: Rayner, June [ra...@ei...] Sent: Thursday, February 14, 2013 9:34 AM To: Demian Katz; vuf...@li... Subject: RE: VuFind Database Recovery procedures Thanks Demain Some follow up questions about this. We've got a mysqldump running daily, and we also have a filesystem backup that is not backing up anything in the actual mysql database directory in /var/lib/mysql/ except the log files. We want to do a test of recovering the entire filesystem, including the mysql database. Our general thought is that we would recover the filesystem from backup, and then use the mysqldump to restore the database. So, here's the questions Are there any other mysql files that we should include in the filesystem backup? Is there anything that we need to do with mysql after a complete filesystem recovery before we restore the mysqldump files? Can you point us to any documentation that may be helpful? Regards, June From: Demian Katz [mailto:dem...@vi...] Sent: Thursday, January 17, 2013 2:30 PM To: Rayner, June; vuf...@li... Subject: RE: VuFind Database Recovery procedures So far we haven't had any MySQL problems over here - it tends to be a fairly robust system. The worst scenario we've run into so far involved the MySQL server running out of disk space, but even that didn't corrupt anything - we just had to free some space and restart the service, and it picked up right where it left off. It's certainly a good idea to run regular mysqldumps just in case... but fortunately these are very easy to use in a recovery situation, and since they're plain text, you can even programmatically process them if the data needs to be filtered before reingestion. - Demian From: Rayner, June [mailto:ra...@ei...] Sent: Thursday, January 17, 2013 2:11 PM To: vuf...@li... Subject: [VuFind-Tech] VuFind Database Recovery procedures Hi Folks We're working on recovery procedures for different recovery scenarios for corrupt data, either in the MySQL database or the Solr index. In many cases, it seems like the easiest solution is to recreate the indexes through the reindex process. Has anyone had a scenario where they had to do a database restore? Did you restore the entire database, or only selected tables? Are there any other tools that have been helpful to you in a recovery situation? Regards, June Rayner ILS Application Team (412) 622-1941 ra...@ei...<mailto:ra...@ei...> The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. |