Hello,
I’m currently in a situation where I need to backup a 250GB MySQL mixed InnoDB and MyISAM Database. I was wondering if it was the right choice to proceed like this:
Sunday - Full Backup
Monday till Saturday - Incremental Backups
After a while of testing we thought it was the optimal solution size-wise, but the reason we are not proceeding to put it in production is the following:
Let’s take 1 full and 6 incrementals as an example
In case we need to restore the DB as of day 4, but for some reasons wrongly restore day 5, would it be possible to go back in some ways?
We tried creating a mirror of the incrementals and prepare the full with them - not working
creating a mirror of the full and prepare it with the existing incremental - not working
Copy all the incrementals and the full and use them as a backup of backups - working
The problem with the last choice is of course the size occupied with all these backups.
What do you exactly mean by that? If I prepare the full backup with incremental5 how can I start back the restore process? I cannot prepare it with incremental1 because of the error:
This target seems to be already prepared with --apply-log-only.
This incremental backup seems not to be proper for the target.
Check ‘to_lsn’ of the target and ‘from_lsn’ of the incremental.
Thanks a lot for the --compress I didn’t know this option!
I’ve tried to create a copy of the full backup, the problem is that once an incremental have been merged into the full, it would not be possible to use it again on the copy.
So I think it is not possible to “go back” once I’ve restored the wrong full with the wrong incremental merged, right?
Could you explain better what you mean by “start over”?
Thanks and sorry if I’m not comprehending correctly.
Andrea