Skip to main content

Search

Welcome to Tibero GTS!

Files Required When Configuring Clone DB Based on Cold/Hot Backup

Document TypeㅣTechnical Information

CategoryㅣBackup/Recovery

Applicable Product Versionsㅣ6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS

Document NumberㅣTBATI016

 

Overview

This explains the files required and important considerations when configuring a Clone DB using Cold/Hot Backup.
 
 

Method

Clone DB configuration can be carried out by choosing one of the two methods below.
 

Complete Recovery After Performing Cold Backup

Complete recovery is the process of applying all Online Redo contents to restore up to the most recent point in time.
For this, the backed-up datafile, controlfile, all archive log files generated after begin backup, redo log files, and passwd file are required.
The recovery process is performed by stopping the DB and copying all database-related files.
Caution
Even if the DB is reconfigured through complete recovery, the moment it starts in normal mode, the existing (as-is) DB and the recovered (to-be) DB are recognized as different databases, so file compatibility is not possible.
Therefore, after the DB starts following complete recovery, a new backup must be performed.
 

Incomplete Recovery After Performing Hot Backup

Incomplete recovery is the process of restoring only up to a specific point in time, not using Online Redo for the latest point restoration.
Note
After performing begin backup, copy the datafile and apply only up to the archive log files.
For this, the backed-up datafile, controlfile, archive log files up to the desired recovery point, and passwd file are required.
An advantage is that datafile copying is possible without stopping the DB, but the operating online redo log cannot be applied.
Caution
  • After incomplete recovery, the DB is started with resetlogs, and all online log files are initialized.
  • Datafiles and log files before and after resetlogs startup are not compatible, and recovery to a later point using backup or log files from before resetlogs is not possible.
  • Therefore, after starting with resetlogs, a new backup is absolutely necessary.
 
 
 

Related to