Bug #58150 | MEB: Restore does not issue warning msg if character set is missing from server | ||
---|---|---|---|
Submitted: | 11 Nov 2010 23:44 | Modified: | 19 Nov 2010 18:37 |
Reporter: | Hema Sridharan | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Enterprise Backup | Severity: | S3 (Non-critical) |
Version: | MEB 3.5.next | OS: | Linux |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[11 Nov 2010 23:44]
Hema Sridharan
[11 Nov 2010 23:46]
Hema Sridharan
Test case to reproduce the error
Attachment: charset_bug.test..txt (text/plain), 2.91 KiB.
[16 Nov 2010 14:26]
Satya B
Our restore is 'offline'. So we can't do much to warn about the missing charset files. Some of the solutions can be: ----------------------------- Backup checksums: ----------------- When Backup checksum is implemented, we can detect the checksum doesn't match at restore stage and flag an error. But this is WORSE because we now refuse to start because of missing charset which might be used by only some tables. Backup Manifest File: --------------------- After WL#5511, We have detailed list of files backed up, So any file missing at restore can be verified and flag a warning or error. But this is another feature request/WL.