You archive the version files of the log backup using operating system commands or backup tools from other providers.
We recommend that you archive the version files regularly. There are several reasons for this:
· With automatic log backups, the database system continuously writes version files, which contain the redo log entries in chronological order. Thus the number of version files on the hard disk grows continuously until there is no more memory available.
If there is no more memory available on the hard disk for log entries, then after a certain amount of time there is also no more memory 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 instance comes to a halt.
· When the database system has backed up the redo log entries from the log area, it can then overwrite the backed up redo log entries in the log area. If you want to restore the database after a system failure and both the log area and the log backups have been damaged, you cannot completely restore the last database state.
You use backup media of the file type for log backups (see Backing Up Log Entries).
To archive the version files, you use operating system commands to copy the oldest version files to another hard disk and then delete them from the original spot.
If you use an external backup tool, you can automate the process for archiving version files.
· Database Manager CLI, Other Commands for Backing Up
·
Database Management in CCMS, Archiving Version
Files
See also:
Supported Backup Tools from Other Providers