[...] > >> But what will happen in the same scenario when changes are >> not in the Datavolume, but only in the cache, and the Logvolume >> was cleared because it was full 1 second before the powerfailure? > >Here the operator loose the right to use this name !!! > >Don't ever try to use a database productively and clear log volumes or >switch it to "Auto Overwrite" or best: delete log volumes etc. > >Better don't think about this, simply do your data and log backups >regularely in the official way and be good. > >> Or in other words: >> - Is it guaranteed, that in Logmode: Overwrite all changes >are written >> to the Datavolume, before the Logvolume ist cleared, when its full? > >Never, you play with your log continuation :-). Better don't try this >in productive environment. > >Ralf
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. 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]
