From: Ananda Kumar Date: November 7 2012 1:26pm Subject: Re: How to verify mysqldump files List-Archive: http://lists.mysql.com/mysql/228590 Message-Id: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d0407139d8bda8904cde7a944 --f46d0407139d8bda8904cde7a944 Content-Type: text/plain; charset=ISO-8859-1 you can use checksum to make sure there are not corruption in the file On Wed, Nov 7, 2012 at 6:39 PM, Claudio Nanni wrote: > Gary, > > It is always a good practice to test the whole solution backup/restore. > So nothing is better than testing a restore, actually it should be a > periodic procedure. > As for the validity of the file usually is delegated to the operating > system. > If you want to check it yourself you may create an algorithm that analyses > some patterns in the dump file to recognize that it is correct, > starting may be from one that is working as 'valid' sample. > > Cheers > > Claudio > > > > 2012/11/7 Gary > > > 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 syntactically correct? > > > > -- > > 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 > > > > > > > -- > Claudio > --f46d0407139d8bda8904cde7a944--