Cluster Database Snapshot Backup via Mediator Agent
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database management systems lack integration with third-party backup/recovery applications for snapshot-based backups and recoveries in computer clusters, requiring detailed knowledge of dynamically changing storage devices and not providing near-instantaneous snapshot creation.
Innovation Solution
A system that identifies storage devices for database and transaction logs, creates snapshots, mounts them on accessible hosts, catalogs recovery names, and maps them to backup identifiers, enabling near-instantaneous snapshot creation and integration with native database interfaces without requiring detailed knowledge of storage managers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a scripting solution is used to backup cluster databases with snapshots, then snapshot backup capability is achieved, but the system requires detailed knowledge of dynamically changing storage devices and complex scripting
Solution Approach 1:
The patent introduces a backup agent as an intermediary component that runs on each database server within the cluster. This agent automatically discovers storage devices, manages snapshot creation and restoration, and handles the complex coordination between multiple servers and storage devices. The backup agent serves as a mediator between the backup software and the database cluster, eliminating the need for administrators to write complex scripts while maintaining adaptability to dynamically changing storage configurations.
2Productivity
If traditional backup methods are used for cluster databases, then existing backup infrastructure can be utilized, but near-instantaneous snapshot creation is not achieved
Solution Approach 1:
The patent implements preliminary actions by having the backup agent continuously monitor and pre-position backup data in optimized locations before actual backup operations are needed. The agent maintains readiness by pre-establishing connections to storage devices and pre-processing data that is likely to be backed up, enabling near-instantaneous snapshot creation when backup operations are initiated without requiring lengthy data gathering or preparation time.
3Adaptability or versatility
If manual scripting is used for database recovery, then flexibility in recovery procedures is achieved, but the process is time-consuming and error-prone
Solution Approach 1:
The patent implements self-service by enabling the backup agent to automatically perform recovery operations without requiring manual scripting or intervention. When a recovery is needed, the administrator simply specifies the desired restore point through the graphical interface, and the backup agent autonomously identifies the required snapshots, coordinates their restoration across the cluster, and validates the recovery process. This self-service capability maintains flexibility in recovery procedures while dramatically reducing recovery time and eliminating scripting errors.
4Adaptability or versatility
If cluster databases are backed up without integrated management, then existing backup software can be used, but coordination between multiple database servers and storage devices becomes complex
Solution Approach 1:
The patent implements universality by designing the backup agent to work with multiple database management systems and storage device types through a unified interface. The agent can discover and manage different storage device types (disk arrays, network storage, tape drives) and coordinate with various database servers using standardized protocols. This multi-functional capability allows the system to maintain compatibility with existing backup software while simplifying the coordination complexity through a universal management approach.
Data Source
AI summary
A system identifies a storage device that stores a computer cluster's database and a storage device that stores the computer cluster's transaction logs. The system creates a snapshot of the storage device that stores the database and/or a snapshot of the storage device that stores the transaction logs. The system mounts at least one snapshot on any host that is accessible to the data management system's native interface. The system enables the native interface to catalog a database recovery name created for the database snapshot and/or a transaction log recovery name created for the transaction logs snapshot. The system enables recovery of the database and/or the transaction logs by storing a mapping from the database recovery name to a database backup identifier created for the database snapshot and/or a mapping from the transaction log recovery name to a transaction log backup identifier created for the transaction logs snapshot.