>> If I would have some fancy mirroring solution it would have replicated
> the
>> problem. So that wouldn't have helped.
>> It's not an option to restore a database from the day before either.
>> I guess the only thing I can do is take a backup more often but it hurts
>> performance. I mean really it not that easy...
>> How often do you guys take a backup?
>
> If you use MySQL, you have the binary log. That allows you restore any
> changes done after the last full backup(or which point in time ever). The
> binary logfile can be saved easily every hour. It can also get moved to
> another machine, after you have cycled the logfiles.
If the database becomes corrupted at say 1am and you don't notice it until
your first cup of coffee at 9am, is the binary log going to be of any
help?
Is it possible to restore to a point the database was consistent and then
use the 'good' changes from the log?
Anne
_______________________________________________
DBmail mailing list
DBmaildbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
Re: backup database, how often?
2007-01-25 12:49:55
>
> If the database becomes corrupted at say 1am and you don't notice
> it until
> your first cup of coffee at 9am, is the binary log going to be of any
> help?
The log records *EVERY* query which is executed.
Therefor you can restore an old backup, and redo every query until
time-point X
You just have to keep pairs of complete backups and logs to restore.
The longer between complete backups the longer it takes to restore
because queries have to be executed.
You can effectively restore to every time you have the logs and the
backup of the server at which they start.
(I only use PostgreSQL so make sure of the differences between PITR
and the implementation of MySQL before
believing me on my word).
Marc
_______________________________________________
DBmail mailing list
DBmaildbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail