In the past when I used mysqldump, I used a slave database for backups and periodically
My process for testing:
- Stop the slave process (so the db doesn't get updated).
- Run the backup.
- Create restore_test database.
- Restore the backup to the restore_test database.
- Use mysqldbcompare to compare the two databases.
- Drop restore_test database.
- Start the slave process.
I have this scripted so it just runs and emails me the results.
From: Gary [mailto:listgj-mysql@stripped]
Sent: Wednesday, November 07, 2012 7:52 AM
Subject: How to verify mysqldump files
Can anyone suggest how I could verify that the files created by mysqldump are "okay"? They
are being created for backup purposes, and the last thing I want to do is find out that
the backups themselves are in some way corrupt.
I know I can check the output of the command itself, but what if.. I don't know... if
there are problems with the disc it writes to, or something like that. Is there any way
to check whether the output file is "valid" in the sense that it is complete and
Gary Please do NOT send me 'courtesy' replies off-list.
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
Notice: This communication may contain privileged and/or confidential information. If you
are not the intended recipient, please notify the sender by email, and immediately delete
the message and any attachments without copying or disclosing them. LBI may, for any
reason, intercept, access, use, and disclose any information that is communicated by or
through, or which is stored on, its networks, applications, services, and devices.