Transportable Pluggable Database Backup for Cross-Container Relocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database restoration methods for multitenant database systems face challenges such as significant downtime and increased costs due to the need for pluggable databases to be in read-only mode during cloning and relocation, as well as limitations in using third-party tools and the inoperability of backups across different container databases.
Innovation Solution
The solution involves creating a backup of a source pluggable database, unplugging it to create a transportable database package, and then plugging it into a target container database, along with translating redo log identifiers and transferring metadata to ensure seamless restoration and data integrity across different container databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a pluggable database is cloned using traditional methods, then the source PDB must be in read-only mode, but this causes significant downtime and limits work on the source PDB
Solution Approach 1:
The patent applies preliminary action by creating a backup of the source PDB before initiating the cloning process. This backup serves as a pre-prepared copy that can be used for cloning without requiring the source PDB to be in read-only mode, thereby eliminating downtime while ensuring data integrity through the use of the pre-created backup
Solution Approach 2:
The patent uses the copying principle by creating a backup copy of the source PDB and then using this copy for the cloning operation. Instead of cloning directly from the live source PDB (which would require read-only mode), the system creates a duplicate backup first, and this backup becomes the source for the clone, allowing the original to remain fully operational
2Ease of manufacture
If third-party tools are used to clone a PDB, then cloning can be performed, but database provisioning costs increase and application development slows down
Solution Approach 1:
The patent applies self-service by implementing native cloning capabilities within the Oracle multitenant database system itself, eliminating the need for external third-party tools. The database system provides built-in functionality to create backups and perform cloning operations, allowing administrators to self-serve without requiring additional software or tools, thereby reducing costs and improving provisioning speed
Solution Approach 2:
The patent demonstrates universality by creating a multi-functional native cloning system that can handle various cloning scenarios (same CDB, different CDB, cross-datacenter) using the same core backup and restore mechanisms. This universal approach replaces multiple specialized third-party tools with a single integrated solution that performs all cloning functions
3Adaptability or versatility
If a PDB is moved between container databases, then relocation is achieved, but the process is disruptive to users and takes significant time
Solution Approach 1:
The patent applies preliminary action by creating a backup of the source PDB before the move operation. This pre-created backup allows the PDB to be restored at the destination without requiring the source PDB to be taken offline, thereby enabling seamless relocation with minimal user disruption while maintaining full adaptability across different container databases
Solution Approach 2:
The patent uses the intermediary principle by introducing a backup as an intermediate copy between the source and destination PDB. The backup serves as a mediator that enables the transfer of data without requiring direct connection or synchronization between source and destination systems, reducing disruption and enabling smooth relocation
4Reliability
If backups are created for large PDBs, then data protection is achieved, but storage costs and maintenance burden increase
Solution Approach 1:
The patent applies the copying principle by creating backup copies of PDBs that can be stored efficiently and reused for multiple purposes (cloning, restoration, cross-datacenter replication). These copies enable reliable data protection while the system optimizes storage utilization through native backup mechanisms that can manage large volumes of backup data efficiently
Data Source
AI summary
Techniques are provided for creating a backup of a source pluggable database (SPD) of a source container database and porting the backup for recovery into a different target container database. In an embodiment, a source database server retrieves metadata that describes backups of the SPD. The source database server inserts, into an unplugged pluggable database of the SPD, the metadata that describes each of the backups. For example, unplugging the SPD may automatically create the unplugged pluggable database. Eventually, the unplugged pluggable database may be plugged into the target container database. A target database server transfers the metadata that describes each of the backups from the unplugged pluggable database and into the target container database. Based on at least one backup and the metadata that describes backups of the SPD, the target database server restores a target pluggable database within the target container database.