It is a good idea to back up the data and log entries from the data and log areas of your database instance on backup media on a regular basis.
If the database instance breaks down due to a hardware defect or a logical error, you can restore the database to a consistent state by importing the data and log entries that have been saved on the backup media.
If you have a lot of data to import, restoring the database instance can take a long time. Because restoring is done in the ADMIN operational state, the database instance is not available while the restore is ongoing. For information about how to make the database instance available for users more quickly, see the Replication and High Availability section.
You use the Database Manager for backing up and restoring.
The Database Manager supports the use of backup tools from other providers.
...
1. You make a plan of when you want to perform which backups. See Regular Administration Tasks.
We recommend that you test backing up and restoring on a test computer before starting your production system.
2. With the Database Manager, you define backup media.
3. You back up the data and log entries regularly during normal database operation. Backups can be done in the ONLINE operational state, so the database instance is available for users during the backup. See:
Data exported with the Loader database tool is not a data backup. The data may not be consistent and is not suitable for restoring a database instance.
4. Check if the database instance carried out the backup successfully. See Monitoring.
5. If you use backup media of the file type (version files) for the backup, archive the version files regularly.
6. Using data and log backups, you can restore the database instance after a system breakdown.
Backup Process
Example: Backing Up and Restoring
See also:
Supported Backup Tools from Other Providers
Freezing the Data Area (Snapshot)