Demonstration 1: Backup and recovery tasks using the Db2 database.
This demonstration provides a comprehensive guide to performing backup and recovery tasks in the Db2 database. You will learn to configure log space, enable archive logging, create a backup image, and recover the database to a selected point in time.
Backup and recovery are critical tasks in database administration to ensure data integrity and availability in case of failures.
In this task, you will configure the database log space to handle applications with large transactions.
Logon to the Linux system using the user id inst23, with a password of ibm2blue.
Right-click the empty Linux desktop and select Open in Terminal.
Change to the directory $HOME/ddl to access the necessary files.
Use the following commands to configure the log space.
Use the db2pd command to check the current and deferred configuration settings.
Run the SQL command files to simulate changes and observe the effects on the log space.
If the log space is insufficient, database changes will fail with the SQL0964 message indicating that the transaction log is full. Use the increase_logs.ddl file to allocate sufficient log space.
By completing this task, you have successfully configured the log space for the database to handle large transactions.
In this task, you will configure the database for archive logging to enable more comprehensive recovery options.
Use the following commands to configure archive logging and set the appropriate log paths.
Switching from circular logging to archive logging requires an offline database backup to establish the starting point for archival logging.
By completing this task, you have successfully configured the database for archive logging, allowing for more comprehensive recovery options.
In this task, you will perform multiple sets of changes to the database and record the time for each set to facilitate point-in-time recovery.
Execute the stock_insert2.sql script to make changes and note the current time.
Record the current table size and the local date and time from the SQL result.
Execute the script a second time to generate another set of logged changes.
Record the current table size and the local date and time from the SQL result.
Use DSM to execute the stock_insert2.sql script and note the results.
Record the current table size and the local date and time from the SQL result.
Execute the script a second time to generate another set of logged changes.
Record the current table size and the local date and time from the SQL result.
Accurate recording of times and results is crucial for successful point-in-time recovery.
By completing this task, you have successfully generated multiple sets of table changes and recorded the times for each set.
In this task, you will use the RECOVER DATABASE command to restore the database to a specific point in time based on the recorded times from the previous task.
Terminate active sessions and prepare the database for recovery.
Wait about 1 minute before performing the recover command to allow the database to shut down.
Use the RECOVER DATABASE command to restore the database to the recorded time of the first execution of the SQL script.
Connect to the database and check the row count in the TEMP_STOCK table to verify recovery.
Ensure that the recovery target time value is specified correctly in the format yyyy-mm-dd-hh.mm.ss.
By completing this task, you have successfully recovered the database to a specific point in time, verifying the recovery by checking the row count in the TEMP_STOCK table.
This demonstration has provided a comprehensive guide to performing backup and recovery tasks in the Db2 database. By following the tasks and best practices outlined, you have gained hands-on experience with configuring log space, enabling archive logging, creating a backup image, and performing point-in-time recovery, enhancing your database administration skills.