Document Type | Technical Information
Category | Backup/Recovery
Applicable Product Versions | Tibero6, Tibero7
Document Number | TBATI053
Overview
This document explains the backup configuration of databases operating in the Tibero environment by distinguishing between physical backup (regular) and logical backup (irregular) perspectives.
Physical backup is a method to regularly protect data files, archive logs, control files, etc., through BCV replication and NetBackup integration,
while logical backup is a method to perform Export on important tables based on the same replication procedure for use in table-level recovery.
This document provides guidance on the conceptual configuration, execution procedures, precautions, and recovery utilization methods for each backup method.
Method
Backup Configuration Diagram - Physical Backup (Regular)
Backup Process
| Step | Description |
|---|---|
| 1. Begin Backup | Execute Begin Backup on the production DB. |
| 2. BCV Replication | * Create BCV replicas of TAS DISK (raw device). |
| * The data points of all BCV replicated disks must be guaranteed to be the same. | |
| 3. End Backup and Essential File Replication | * Execute End Backup on the production DB. |
| * Perform forced archive of the production DB model log and copy it. | |
| * Copy the control file (with a distinguishing file name). | |
| 4. Start TAS and DB | * Using BCV data and the three files, start TAS and DB (1-node TAC mode); start the DB in Normal mode. |
| 5. NetBackup (tbrmgr) | * Perform NetBackup integrated backup through tbrmgr. (Daily) |
| 6. NetBackup (Archive) | * Periodically back up archive log files (stored in a general file system). (Hourly) |
| * This is done on a scheduled basis. | |
| ※ In case of Recovery | * Recover by Restore of NetBackup data ($tbrmgr$ backup, archive) on the DR server or production server. |
Backup Configuration Diagram - Logical Backup (Irregular)
Backup Process
| Step | Description |
|---|---|
| 1. Begin Backup | Execute Begin Backup on the production DB. |
| 2. BCV Replication | * Create BCV replicas of TAS DISK (raw device). |
| * The data points of all BCV replicated disks must be guaranteed to be the same. | |
| 3. End Backup and Essential File Replication | Execute End Backup on the production DB. |
| * Perform forced archive of the production DB model log and copy it. | |
| * Copy the control file (with a distinguishing file name). | |
| 4. Start TAS and DB | * Using BCV data and the three files, start TAS and DB (1-node TAC mode); start the DB in Normal mode. |
| * Perform export of selected important tables (logical backup) $\rightarrow$ Separate file system space is required. | |
| 5. NetBackup Integration | * Conduct on a scheduled basis if necessary. |
| ※ In case of Recovery | * Recover by Restore of NetBackup data on the DR server or production server. (Table-level recovery) |
Summary
This document explains the backup configuration in Tibero6 and Tibero7 environments by dividing it into physical backup and logical backup.
Physical backup is a method to establish a regular full recovery system through BCV replication, archive logs, control files, and NetBackup integration, while logical backup is a method that performs Export of important tables after the same replication procedure for table-level recovery.
By summarizing the execution procedures and recovery utilization methods of each backup method, this document is structured to serve as a reference when establishing a backup strategy suitable for the operating environment.