Entering content frame

 Overwrite Mode for the Log Area 

You can use this log setting to control whether the log area is overwritten cyclically without the log entries being backed up.

Normal Log Backups

By default, the log area can be overwritten only if the appropriate log entries have been backed up. For this reason, you must make log backups at regular intervals.

The log entries of the log area and the log backups are then available if you need to restore the database. As long as they are complete, you can use the data backup, log backups and the log entries in the log area to recover the database up to a chosen point in time.

If overwrite mode was activated and you then change back to normal log backups, you must then make a complete data backup.

Overwriting the Log Area Without a Log Backup

The log area is overwritten cyclically, and you do not need to back up the log entries.

This interrupts the log backup history. If you need to recover the database, only the log entries in the log area are available. This usually means that you cannot recover your database instance up to the last COMMIT before the crash, or to any other time; instead, you can restore it only to the state it had at the time of the last data backup.

You can only recover the database to a time of your choice if all the log entries written after the data backup exist in the log area (which means that the log area has not been overwritten since the data backup).

Only activate the overwrite mode if you are happy with only being able to recover your system to the state it had when the last available data backup was made.

Procedure

You can use the Database Manager GUI to set the overwrite mode (see Changing Log Settings).

 

Leaving content frame