Proxy Server Containerization for Concurrent DBMS Backup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional storage management systems face inefficiencies due to namespace limitations, leading to increased network complexity and costs when performing concurrent and overlapping backup operations for database management systems, requiring multiple servers and complex workarounds to avoid namespace clashes.
Innovation Solution
The implementation of software containerization techniques allows a single proxy server to dynamically configure concurrent and overlapping storage and testing operations for multiple DBMS instances, using software containers that operate independently and do not interfere with each other, thereby isolating production environments from testing and storage operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple proxy servers are used to handle concurrent and overlapping backup operations, then backup operations can be performed simultaneously without namespace clashes, but network complexity and equipment costs increase substantially
Solution Approach 1:
The patent segments the proxy server functionality into multiple isolated software containers (e.g., Oracle container, SQL container, test container). Each container operates independently with its own namespace, allowing concurrent backup operations without interference. This segmentation enables multiple backup operations to run simultaneously on a single physical server while maintaining namespace isolation.
Solution Approach 2:
The patent introduces a new dimension of virtualization by implementing software containers that create isolated execution environments within the same physical server. This dimensional shift from physical server multiplication to virtual containerization allows concurrent operations without requiring additional physical infrastructure, thereby reducing network complexity while maintaining productivity.
2Productivity
If multiple proxy servers are deployed to handle overlapping backup operations, then namespace limitations are avoided, but equipment costs and maintenance expenses increase
Solution Approach 1:
The patent merges multiple proxy server functionalities into a single physical server by implementing software containers. Each container (Oracle container, SQL container, test container) consolidates specific database backup operations within isolated namespaces on the same hardware platform. This merging reduces the total number of physical servers required while maintaining the capability to handle overlapping backup operations.
Solution Approach 2:
The single proxy server becomes universal by hosting multiple software containers that can handle different database types (Oracle, SQL) and different operations (backup, restore, testing) simultaneously. This multi-functionality eliminates the need for dedicated servers for each operation type, reducing equipment costs while maintaining productivity.
3Device complexity
If database names are changed to avoid namespace clashes during backup operations, then concurrent operations can proceed on the same server, but the process becomes time-consuming and risky
Solution Approach 1:
The patent establishes software container definitions and namespace configurations in advance, before backup operations begin. Each container is pre-configured with its own isolated namespace, eliminating the need for runtime renaming operations. This preliminary setup allows immediate execution of concurrent backup operations without time-consuming name changes.
Solution Approach 2:
The software container acts as an intermediary layer between the physical server and the database backup operations. This intermediary provides namespace isolation automatically, eliminating the need for direct manipulation of database names. The containerization mechanism mediates namespace conflicts without requiring time-consuming renaming procedures.
4Adaptability or versatility
If different versions of DBMS software are run concurrently on the same server, then version compatibility testing can be performed, but namespace clashes prevent this in traditional systems
Solution Approach 1:
The patent segments different DBMS versions into separate software containers (e.g., Oracle container, SQL container, test container), each with its own isolated namespace. This segmentation allows concurrent execution of different DBMS versions on the same physical server without namespace interference, enabling version compatibility testing while maintaining simple software configuration management.
Data Source
AI summary
An illustrative data storage management system relies on a specially configured proxy server to operate software containers on a proxy server, maintain resources needed by the software containers, and interwork with other system components. Illustratively, a catalog service on the proxy server maintains a software cache according to maintenance rules and also maintains an associated cache catalog. The software containers are generally managed and operated by an illustrative container manager also hosted by the proxy server. The illustrative software cache comprises contents needed by the software containers, such as pre-configured container templates, DBMS software components, lightervisors representing target operating systems, and storage management software for performing test and storage operations. The maintenance rules govern when cache contents should be purged and moved into offline archive copies.