Definition
Online Backup
You can perform an online backup with the database running – that is, the users can continue to work normally. The management of database changes by the corresponding Oracle background processes is not affected.
Tablespace online backups on their own are inconsistent. To make the database consistent, you need to apply redo log entries from the backup period. If you use
RMAN for online backup, it takes care of internal block consistency during the backup.An online backup is made using operating system tools such as
cpio, tar, or dd – for example, under the control of BRBACKUP. Since these tools are not part of the database system, Oracle must be informed about the starting point of a backup. In this way, a unique restart point is defined from which the recreation of all the files of a tablespace can be performed in the event of an error. This process works as follows:RMAN normally takes care of this process internally, so it is not explicitly performed.
Offline Backup
After an offline backup of the complete database, you have a backup of the database that is consistent. If you work with the database after the backup, the backup is no longer up-to-date. In this case, you have to recover the database after you restore the backup, using the redo log files.
You must close the database for an offline backup, which means that you have to stop work in the SAP System. However, the SAP System does not have to be shut down for an offline backup. If the
RECONNECT mechanism is set in the SAP start profiles, the connection to the SAP System is remade after the database is restarted. This means that the information in the buffers of the SAP System is not lost, which implies better performance immediately following the start.