Database Group Management via Unified SLA and Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtual computing systems face challenges in efficiently managing databases, particularly in creating and protecting databases, due to their configuration and operational limitations.
Innovation Solution
A database management system that simplifies database provisioning by allowing users to quickly create and manage database groups, associate them with Service Level Agreements (SLAs) and protection schedules, and protect databases using a combination of snapshots and transactional logs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If databases are protected individually with separate SLAs and protection schedules, then data protection reliability is improved, but system complexity and management overhead increase
Solution Approach 1:
The patent combines multiple individual database protection mechanisms into a unified database group protection system. By grouping databases together and applying a single SLA and protection schedule to the entire group, the system reduces management complexity while maintaining protection reliability through centralized control and consistent policy application across all databases in the group.
Solution Approach 2:
The database group object serves multiple functions simultaneously: it acts as a container for multiple databases, a management unit for applying SLAs and protection schedules, and a organizational structure for resource allocation. This multi-functionality reduces the need for separate management mechanisms for each database while ensuring comprehensive protection.
2Adaptability or versatility
If multiple databases are managed individually, then database-specific control is improved, but provisioning time and operational efficiency decrease
Solution Approach 1:
The system segments database management into two levels: database group level for centralized management of common parameters (SLA, protection schedule) and individual database level for specific configurations. This segmentation allows efficient bulk operations at the group level while preserving the ability to manage individual databases when needed, thus improving provisioning efficiency without sacrificing adaptability.
Solution Approach 2:
The patent enables preliminary configuration of database groups with predefined SLAs and protection schedules before adding individual databases. This preliminary action allows for standardized, pre-planned protection policies to be applied automatically when databases are added to the group, significantly reducing provisioning time and improving operational efficiency compared to configuring each database individually from scratch.
3Productivity
If databases are grouped together with shared SLA and protection schedule, then resource utilization and management efficiency are improved, but flexibility in applying different protection levels to individual databases decreases
Solution Approach 1:
The database group structure is designed to be dynamic, allowing databases to be added or removed from groups based on changing requirements. The system can adapt the group composition and reassign databases to different groups with different SLAs as needs evolve, providing flexibility despite the standardized group-level protection approach.
Data Source
AI summary
A system and method include receiving request to create a database group, receiving selection of a database server virtual machine on which to create the database group, receiving selection of at least one database from a list of databases that are not part of another database group to add to the database group, receiving selection of a Service Level Agreement (“SLA”) and a protection schedule, and creating the database group on the database server virtual machine, including associating the database group with the SLA and the protection schedule and adding the at least one database to the database group. Each of the at least one database is protected using the same SLA and the protection schedule that is associated with the database group.