We recommend that you activate the automatic log backup. Log backups are the prerequisite for a complete backup history.
Do not overwrite a backup medium with the next backup straightaway, use a different backup medium instead. If the last backup cannot be used because of a hardware error, then you can access the backup previous to that when you restore the data.
The following table is an example of scheduling backup and maintenance action.
Example: Scheduling backup and maintenance action
Action |
Frequency |
Remarks |
Complete data backup |
On each productive day |
If you cannot or do not want to perform a complete data backup every day, then at least perform an incremental data backup on each productive day. The more current the last data backup is, the fewer log entries have to be imported again if you need to restore the database instance. |
Interactive log backup |
Once a week |
Only necessary if you are not using automatic log backup. |
Archive version files of the log backups |
Once a week |
Only necessary if you are using version files for the log backup. Copy the version files with operating system commands or with the Database Manager CLI from the hard disk to an external backup medium. After archiving, you can delete the version files and thus ensure that sufficient space is always available. |
Check the free storage space in the log area |
Once a week |
Only necessary if you are not using automatic log backup and the overwrite mode for the log area is switched off. If no new log entries can be written due to lack of storage space in the log area, the database system shuts down. |
Once a week |
We recommend that you check the database structures at times when the workload is low, or using a system copy. |
|
Once a week |
|