Virtual Database Workflow Automation for Datacenter Efficiency
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 security across multiple teams.
Innovation Solution
The implementation of virtual databases (VDBs) allows for efficient execution of workflow scenarios by linking a source database to a storage system, creating multiple point-in-time copies, and provisioning test and development environments, enabling remote testing and development, replication, and data warehousing, while managing access permissions and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If copies of the production database are made for each lifecycle stage, then the reliability and testing capability are improved, but the hardware infrastructure costs and resource requirements increase significantly
Solution Approach 1:
The patent uses virtualization to create virtual copies of database instances that share underlying physical hardware resources. Instead of requiring separate physical hardware for each lifecycle stage, virtual database instances are created as software abstractions that can be rapidly provisioned and destroyed, providing the necessary copying capability for testing while eliminating redundant hardware infrastructure.
Solution Approach 2:
The patent implements a universal hardware platform that can serve multiple lifecycle stages simultaneously through virtualization. The same physical infrastructure supports production, testing, development, and other stages by dynamically allocating virtual database instances, making the hardware infrastructure multi-functional rather than dedicated to single purposes.
2Reliability
If physical hardware is provided for each lifecycle stage, then the isolation and security are improved, but the floor space requirements and power consumption increase
Solution Approach 1:
The patent transitions from physical spatial separation to virtual logical separation by introducing a virtualization layer. Instead of isolating hardware physically across different floor spaces, security and isolation are achieved in the virtual dimension through virtual machine boundaries, access controls, and network virtualization, allowing multiple isolated environments to coexist on the same physical infrastructure.
3Adaptability or versatility
If redundant hardware is provided for database copies, then the testing and development capability are improved, but the resource utilization efficiency decreases
Solution Approach 1:
The patent implements dynamic resource allocation where virtual database instances can be created, modified, and destroyed on-demand based on lifecycle stage requirements. Resources are dynamically assigned to different virtual instances as needed, allowing the system to adapt to varying testing and development requirements without maintaining static redundant hardware, thereby improving resource utilization efficiency.
4Adaptability or versatility
If data copying is performed for each lifecycle stage, then the workflow progression is enabled, but the time overhead increases significantly
Solution Approach 1:
The patent performs preliminary actions by pre-configuring virtual database templates and images that can be rapidly instantiated. Instead of copying data at runtime for each lifecycle stage, the virtualization infrastructure prepares standardized virtual images in advance that can be quickly deployed and configured, significantly reducing the time overhead associated with data copying and workflow transitions.
Data Source
Figure 1
Figure 2(a)~2(b)
Figure 3
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.