Documentation Home
MySQL Enterprise Backup 4.0 User's Guide
Related Documentation Download this Manual
PDF (US Ltr) - 1.2Mb
PDF (A4) - 1.2Mb
HTML Download (TGZ) - 180.8Kb
HTML Download (Zip) - 206.8Kb

14.4 Validation Operations

To ensure the integrity of the backup data, MySQL Enterprise Backup provides a validate command for validating a backup by the checksum values of its data pages after the backup is created or transferred to another system.

mysqlbackup [STD-OPTIONS]

  • validate

    Verifies that a backup is not corrupted, truncated, or damaged. This operation validates the checksum value for each data page in a backup.

    To avoid spending excessive time and resources on files that are too heavily corrupted, mysqlbackup stops validating a .ibd file after more than twenty corrupted pages are found in it, and proceeds to the next file instead. In that case, the operation's summary will not give a full count of corrupted pages, but only says at least 20 pages are corrupted.

    The operation also has the following limitations:

    • If any .ibd or .frm files are missing from the data directory during a backup or have been deleted from a backup after the backup was made, the validate operation will not be able to detect the problem.

    • If a backup has been corrupted by removing or truncating pages from any of the .ibd files inside , the validate operation will not be able to detect the problem.

    • For any backup directory, the operation can only validate the InnoDB data files (ibdata* and *.ibd files) in it. Problems with other file types within a backup directory (for example, .frm file corruptions) are not detected.

    Here is a sample command for validating a backup image:

    mysqlbackup -uroot --backup-image=/logs/fullimage.mi  validate

    Advanced: Here is a sample command for validating a backup directory:

    mysqlbackup -uroot --backup-dir=/logs/backupext validate

    For more usage examples for the validate command, see Section 4.2.2, “Verifying a Backup”

User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.