Now that you have created a database and tables, and moved data into the tables, you should do an initial backup of the database.
Figure 20. Backup Database SmartGuide
![]() |
The SmartGuide asks you a series of questions and then recommends settings and schedules the backups. It focuses on basic options. If you want to investigate more elaborate procedures, click with mouse button 2 on a database in the Control Center and select Backup.
Select the Next push button to proceed.
Select the option that best represents when your database needs to be back up and running. This influences how often your database will be backed up and what type of backup will be used.
Choose Complete recovery (Archive Logging) so that all logs up to the last complete transaction can be replayed. Archive logging sets the LOGRETAIN parameter to Yes. You need to complete a full off-line backup after setting on log archiving. An off-line backup is a backup of a database that is made when the database is not being accessed by applications. An on-line backup is a backup of a database that is made while the database is being accessed by other applications.
We recommend that you do not make any changes to your database until you have set up archive logging. Setting the LOGRETAIN parameter to Yes allows for active and archived logs to be kept and results in the ability for the database to have roll-forward recovery.
See Chapter 5. "More About Protecting the Data" for more detail on backup and restore. DB2 logs are described in "About the Logs that DB2 Keeps".
Use the slider to represent how much of the data in your database is new or changes each day. This influences how often the database should be backed up. You can override the suggested value.
After completing the SmartGuide, and based on your responses to the questions asked, your database could be backed up:
The recovery history file helps you locate information once you have performed a backup. For example, it helps you determine the location of a backup, or in which backup a DB2 object can be found. If a backup is moved to different media, say from disk to tape, this file can be updated to keep track of the new location of the backup.
To view the contents of the recovery history file:
Every DB2 backup made contains a copy of this file, and it can be restored from any backup. If you choose to restore it, use caution to avoid overwriting the database's existing history file. Although the recovery history file is an ASCII file, manually editing the file should be done only at your own risk and is not recommended.