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 -~----------~----~----~----~------~----~------~--~---
