The binary logs are important to be able to restore the database to a specific point in time. Ie: you know the accident that dropped some table happened at 5pm.
Assuming you had the snapshot and binlogs from the backup previous to 5pm, and the backup post 5pm, you could do a restore to another server of the previous backup, and replay the logs of the last backup up until 4:59pm. Saving said customer most of the day's transactions. Without the binlogs your ability to restore is limited to the resolution of your backups. With the binlogs and preserving previous snapshots you can increase your restore resolution to any point in time between two snapshots. Granted, it's going to be time consuming if you have to do it; having the option is always preferable than not. You are right, without storing multiple snapshots having the binlogs by themselves accomplishes nothing. That's why we would like to request that multiple snapshots are kept similar to how the database backups are kept in S3, and that binlogs are added to the snapshots. Perhaps there's a "paranoid" option that could be added to scalr for those who want the added protection. We have also been working on copying the snapshot from one farm id to another, if anybody else has a solution that they can share it would be much appreciated. On Feb 16, 10:39 pm, Arie Fishler <[email protected]> wrote: > the binary logs are not part of the backup. BTW my logic says that having > them WITH the backup itself is useless. Normally I believe that the binary > logs are used to recover a db when your backup is not the most current. You > restore from backup and then for the missing part (assuming you have the > most recent binary logs) you roll the logs to have an up to date db. > > This calls for a separate and more frequent backup of the binary logs and in > any case none is currently available from scalr according to my last > interrogation of the matter. > > On Mon, Feb 16, 2009 at 9:50 PM, Joel Franusic <[email protected]> wrote: > > > It was our understanding that the binlogs are supposed to be part of > > the snapshots that come from the mysqllvm role. However, upon > > inspection of the "mysql-snapshot.tar" file in the S3 bucket for our > > farm, it seems like the binlogs are not part of the backup. > > > Were we mistaken? If so, are there any suggestions for making the > > binlogs part of the snapshot? (Change the "log_bin" directive in > > my.cnf perhaps?) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
