MYSQL Save Restore Challenges -- WEB400

Subject: MYSQL Save Restore Challenges
From: Paul Holm <pholm@xxxxxxxxxxxxxxxxx>
Date: Thu, 20 Jan 2011 11:58:55 -0800
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

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 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.