Yes, you should do a test restore when setting up your backup processes, and periodically
afterwards, to check for integrity (and to make sure you have the restore process
well-documented and practiced).
Doing a test restore will also demonstrate how often you should do full backups vs.
incremental backups. When you restore from backup, you would need to restore the full
backup and then each incremental backup since then plus the binlogs since the last
incremental backup, so take this timing into consideration.
For example, if you have very frequent changes, and you see that the test restore takes a
longer time than you're willing to withstand in cases of emergency, then you would
increase the frequency of full backups. I have worked with cases in which it made the most
sense to do full backups nightly and incrementals every 3 hours, and I bet there are use
cases indicating even more frequent full backups.
I would do your test restore with a full backup and the maximum number of incremental
backups and binlogs possible between a full backup and an incident, to show what the worse
case time required would be.
Begin forwarded message:
> From: Kaushal Shriyan <kaushalshriyan@stripped>
> Subject: Re: MySQL Master and Slave Replication
> Date: September 14, 2013 12:04:24 AM EDT
> To: Manuel Arostegui <manuel@stripped>
> Cc: Andrew Morgan <andrew.morgan@stripped>, Johan De Meersman
> <vegivamp@stripped>, "replication@stripped"
> Hi Again,
> I am running MySQL DB version mysql55-5.5.33-1.ius.el6.x86_64 on CentOS 6.4
> for OTRS application. Do i need to have full backup on weekends and
> incremental backups on weekdays as part of backup policy and restore the
> backup to check for integrity of data.
> Please suggest.