[...] >> Hello Andre, >> >> 'auto log overwrite' "clears" only these parts of the log which are >> older then the last savepoint. >> So you can always restart after a powerfailure. The 'auto >log overwrite' >> feature is only to avoid log backups and has nothing to do with the >> savepoint and its main job to flush changed pages from the >data cache to >> the data discs. > >just to be sure: >- we do a dayly full backup >- we have logmode overwrite >- overwrite mode only clears parts of the log which are > already made "permanent" in the data volume >- our goal is to have a dayly full backup in case of a crash >- so we do not really need log-backups > (considered that the dayly full backup is sufficient ) >are these stamements correct? >
If you have no log backups you will not be _sure_ to be able to recover to the last committed transaction in case of disk failures. We do not recommend to set the log mode to automatic overwrite! It only makes sense for special applications. Kind regards, Uwe >Greetings, and thank you very much in advance, >Andre' > >> >> But I think Ralf wants to tell you that a productive database always >> needs data and log backups to be _fully_ recoverable (disc failure, >> backup failure, etc...). >> >> Perhaps it is helpfull for you to read the MaxDB paper "backup >> concepts". >> >> Kind regards >> Uwe >> > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
