Dell products l.p. (20240103980). CREATING A TRANSACTIONAL CONSISTENT SNAPSHOT COPY OF A SQL SERVER CONTAINER IN KUBERNETES simplified abstract
Contents
- 1 CREATING A TRANSACTIONAL CONSISTENT SNAPSHOT COPY OF A SQL SERVER CONTAINER IN KUBERNETES
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 CREATING A TRANSACTIONAL CONSISTENT SNAPSHOT COPY OF A SQL SERVER CONTAINER IN KUBERNETES - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
CREATING A TRANSACTIONAL CONSISTENT SNAPSHOT COPY OF A SQL SERVER CONTAINER IN KUBERNETES
Organization Name
Inventor(s)
Animesh Tamrakar of Bangalore (IN)
Shruthi Sreedharan of Bangalore (IN)
CREATING A TRANSACTIONAL CONSISTENT SNAPSHOT COPY OF A SQL SERVER CONTAINER IN KUBERNETES - A simplified explanation of the abstract
This abstract first appeared for US patent application 20240103980 titled 'CREATING A TRANSACTIONAL CONSISTENT SNAPSHOT COPY OF A SQL SERVER CONTAINER IN KUBERNETES
Simplified Explanation
The patent application describes a method for creating transactional consistent snapshot copies of SQL Server containers in a Kubernetes system for copy reuse on different clusters to facilitate processing local snapshots for secondary workloads without impacting production quality of service.
- The copy data management (CDM) tool acts as an orchestrator.
- A backup toolkit is deployed in the namespace of the production cluster containers.
- A container storage interface (CSI) plugin supplies persistent storage to the containers.
- Before taking a copy, the process posts the toolkit in the container and performs a quiesce/unquiesce operation.
- The databases are quiesced, a snapshot copy is taken, and then the databases are unquiesced.
- The toolkit is then removed, producing a transactional consistent backup in a different namespace.
Potential Applications
This technology can be applied in data backup and disaster recovery solutions, database management systems, and cloud computing environments.
Problems Solved
This technology solves the problem of creating transactionally consistent snapshot copies of SQL Server containers in a Kubernetes system without impacting production quality of service.
Benefits
The benefits of this technology include improved data protection, reduced downtime, and enhanced data management capabilities.
Potential Commercial Applications
Potential commercial applications of this technology include data backup services, cloud storage solutions, and database management tools.
Possible Prior Art
There may be prior art related to data backup and disaster recovery solutions, containerized database management systems, and Kubernetes storage management tools.
Unanswered Questions
== How does this technology ensure data consistency across different clusters? The technology ensures data consistency by quiescing the databases before taking a snapshot copy and unquiescing them afterward, ensuring a transactionally consistent backup.
== What security measures are in place to protect the snapshot copies from unauthorized access? Security measures such as encryption, access controls, and authentication mechanisms can be implemented to protect the snapshot copies from unauthorized access.
Original Abstract Submitted
embodiments for creating transactional consistent snapshot copies of sql server containers in a kubernetes system for copy reuse on different clusters to facilitate processing local snapshots for secondary workloads without impacting production quality of service. a copy data management (cdm) tool acts as an orchestrator, while a backup toolkit is deployed in the namespace of the production cluster containers. a container storage interface (csi) plugin supplies persistent storage to the containers. before taking a copy, the process posts the toolkit in the container and a quiesce/unquiesce operation is then performed. the databases are first quiesced, the snapshot copy is taken, and then the databases are unquiesced. the toolkit is then removed, thus producing a transactional consistent backup in a different namespace.
