× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WEB400
  3. January 2011

MYSQL Save Restore Challenges


Hitting some challenges with a client that has a Windows MYSQL DB (not on as400 but interacts with as400). Database with about 400 tables/views with a size about 40GB.

Challenges:
1. Restores to a disaster recovery system are taking 30-40 hours. (heavy use of indexes seems to dramatically show performance)

2. Save/restore just deal with dumped raw SQL statments in text format. Minimal or no logging of save/restore success and failures. Difficult to reconcile if all data was saved and restored.

3. Hitting corrupted tables but having trouble easily identifying what tables are corrupted. "Check table" command seems to run forever.



Thanks, Paul Holm


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.