If you back up log entries on data carriers of the type ‘file’, we recommend that you archive these backup files at regular intervals. Archiving the backup files is necessary as the database hangs when the hard disk is full.
If the automatic log backup is switched on, the database system continuously writes backup files, which contain the redo log entries in chronological order. Thus the number of backup files on the hard disk grows continuously until there is no more storage space available.
If there is no more storage space available on the hard disk for log entries, then after a certain amount of time there is also no more storage space available in the log area of the database instance for redo log entries (exception: overwrite mode for the log area is on). If the database system cannot write any more redo log entries to the log area, no more data can be changed and the database comes to a halt.
You save your log entries on data carriers of the type file, see Backing Up Log Entries.
? To archive the backup files, you use operating system commands to copy the oldest backup files to another hard disk or another data carrier. Then you delete the original backup files.
If automatic log backup is on, the system saves new log entries to the newest backup file even during archiving.
To ensure that you only archive complete backup files, exclude the newest backup file during archiving.
? If you use backup tools from other providers, you can automate the process for archiving backup files.
To do this, use the Database Manager or CCMS functions:
Database Manager CLI, Further Commands for Backing Up
Database Management in CCMS, Archiving Backup Files