The ORACLE export/import programs enable you to back up specific objects in the database. These backups are not a suitable replacement for image backups of the database, however, because the database can then only be recovered to the condition at the time of the backup. Database changes made after the backup cannot be recovered.

R/3 tables are usually used by multiple users; this means that it is a good idea to make user-related backups with Export/Import. For example, you do not want a user to restore the table ATAB in order to retrieve lost entries in a particular R/3 table.

Logical backups of R/3 objects can be performed using the R/3 utility R3trans. R3trans exports R/3 System objects (among others) from the database into operating system files. If a user then inadvertently deletes an object, that object can be imported from the exported backup file. For more information, see to the documentation on Transport Tools.

Image backups are complete block-for-block copies of the database (online or offline). Image backups are required in order to recover the database in a consistent and current state.

You can perform complete image backups or image backups of specific tablespaces. Tablespaces that are used intensively should be backed up separately between full backups - this can speed up any necessary recovery.