Procedure documentationBacking Up Databases Locate this document in the navigation structure

 

Regularly back up your data and redo log entries from the data and log areas of your database to data carriers. No downtime is required for backups: you can execute backups in the ONLINE operational state, meaning that the database is available to users during backups.

This graphic is explained in the accompanying text.

Backing Up: Schematic Overview

If there is a database failure 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 from the backups. You can use backups you created on a Microsoft Windows system on Unix and Linux systems, and the other way round.

Procedure

For backing up, use Database Studio, Database Manager CLI, or CCMS (in SAP systems only). Note that neither data exports created with the Loader database tool nor data area snapshots are data backups: they are not suitable for restoring a database.

Recommendation Recommendation

Test your backup and restore process on a test computer before starting up your production system.

End of the recommendation.
  1. Make a plan of when you want to carry out backups.

    More information: Periodic Administration Tasks

  2. Define backup templates.

    More information: Backup Templates and Data Carriers

  3. Regularly back up data and redo log entries during normal database operation.

    More information:

    Options

  4. Check if the database system carried out the backup successfully.

    More information: Monitoring Databases

  5. If you use data carriers of the FILE type for log backups (backup files), then archive the backup files regularly.

    More information: Archiving Backup Files

More Information

Restoring Databases

Concepts of the Database Systems, How Databases Store Data and Log Entries