Virtual Database System Using Point-in-Time Block Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of managing databases increases resource costs and inefficiencies, particularly in lifecycle workflows, due to the need for redundant hardware and time-consuming data copying processes, which also complicates access permissions and resource utilization.
Innovation Solution
The creation of virtual databases that efficiently use storage and computing resources by reading point-in-time copies of a source database, allowing multiple virtual databases to share database blocks and enabling flexible provisioning and access control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If physical copies of databases are made for each lifecycle stage, then data availability for different teams is improved, but hardware infrastructure costs and storage requirements increase
Solution Approach 1:
The patent implements virtual copying of database blocks to create multiple virtual database instances from a single physical source database. Each virtual database appears as a complete copy to its user but actually shares underlying storage blocks, eliminating the need for multiple physical database servers while providing isolated data views for different lifecycle stages.
Solution Approach 2:
A single physical source database serves multiple functions simultaneously by providing data to multiple virtual databases used across different lifecycle stages (development, testing, quality assurance, production). The source database becomes a universal data provider that replaces multiple specialized physical databases.
2Adaptability or versatility
If physical copies of databases are made for each lifecycle stage, then data availability for different teams is improved, but storage space and resource utilization worsen
Solution Approach 1:
Multiple virtual databases are merged at the storage level by sharing common database blocks from a single source database. Instead of storing separate physical copies, the system combines storage resources by having multiple virtual instances reference the same underlying data blocks, dramatically reducing total storage requirements.
Solution Approach 2:
Virtual copies of database blocks are created through logical references rather than physical duplication. The system uses storage-efficient copying mechanisms where virtual databases point to shared source blocks, eliminating redundant storage while maintaining the appearance of complete database copies for each lifecycle stage.
3Adaptability or versatility
If redundant hardware is deployed for lifecycle workflows, then data accessibility across teams is improved, but resource utilization efficiency deteriorates
Solution Approach 1:
The source database is designed as a universal data source that simultaneously serves multiple virtual databases across different lifecycle stages. This multi-functional approach allows a single physical database to provide data accessibility to development, testing, QA, and production teams without requiring separate hardware for each function.
Solution Approach 2:
The system creates virtual copies of the source database that can be accessed by different teams simultaneously. These virtual copies provide the appearance of dedicated database instances for each lifecycle stage while actually sharing the same physical storage resources, thereby improving resource utilization efficiency.
4Adaptability or versatility
If multiple physical databases are maintained for lifecycle stages, then team-specific data access is improved, but system complexity and administration overhead increase
Solution Approach 1:
The patent uses virtual copying to create simplified views of the source database for each lifecycle stage. Instead of maintaining complex physical copies across multiple servers, the system creates lightweight virtual instances that reference shared source blocks, reducing system complexity while preserving team-specific data access requirements.
Solution Approach 2:
A single source database with multi-functional capabilities replaces multiple specialized physical databases. The source database is designed to serve multiple lifecycle stages simultaneously through virtualization, reducing the number of database instances from many to one while maintaining team-specific access through virtual database interfaces.
Data Source
AI summary
Information from multiple databases is retrieved and stored on a database storage system. Multiple point-in-time copies are obtained for each database. A point-in-time copy retrieves data changed in the database since the retrieval of a previous point-in-time copy. A virtual database (VDB) is created by creating a set of files in the data storage system. Each file in the set of files created for a VDB is linked to the database blocks on the database storage system associated with a point-in-time copy of the source database. The set of files associated with the VDB are mounted on a database server allowing the database server to read from and write to the set of files. Workflows based on VDBs allow various usage scenarios based on databases to be implemented efficiently, for example, testing and development, backup and recovery, and data warehouse building.