Container Data Protection via Segmented Backup and Self-Service Agents

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data protection systems for cloud-based deployments, particularly those using OpenStack, Kubernetes, and OpenShift, face challenges in scaling to large distributed environments and managing complex containerized applications, leading to inefficiencies in backup and recovery processes.

Innovation Solution

A container-based data protection method and system that supports hybrid clouds, providing scalable backup and restore operations across distributed computing environments, including private and public clouds, and allows for application-layer resiliency, infrastructure migration, and version management, using object storage systems and templates like Helm charts to maintain configuration metadata and application state.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional data protection systems are used for cloud-based deployments, then data backup and recovery can be performed, but the systems cannot scale efficiently to large distributed environments and complex containerized applications

Engineering Contradiction:

Improvescalability to large distributed environmentsVSAvoidcomplexity of backup and recovery processes

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the distributed computing environment into individual container units, each with its own data protection namespace. This allows the backup system to scale by processing containers independently rather than managing the entire distributed environment as a single complex system, resolving the contradiction between scalability and complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The data protection system implements a universal backup mechanism that works across multiple container orchestration platforms (Kubernetes, OpenShift, Docker Swarm) and cloud environments through a standardized interface. This universal approach enables the system to scale to diverse distributed environments without proportionally increasing operational complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of operation

If centralized data protection management is implemented, then comprehensive control over backup operations is achieved, but the need for centralized administration increases operational overhead and costs

Engineering Contradiction:

Improvecentralized control over backup operationsVSAvoidoperational overhead and administration requirements

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system implements self-service data protection where containers automatically register themselves with the backup system and manage their own backup operations through embedded sidecar components. This eliminates the need for complex centralized administration while maintaining comprehensive control, as each container autonomously participates in the backup process.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system introduces an intermediary backup agent that runs within each container's namespace, mediating between the container application and the centralized backup management system. This intermediary handles local backup operations autonomously while reporting to the central system, reducing administrative overhead by distributing operational complexity to the intermediary layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If complete backup of containerized applications is performed, then data protection coverage is maximized, but the time and resources required for backup and restoration increase

Engineering Contradiction:

Improvecompleteness of data protection coverageVSAvoidbackup and restoration time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system applies local quality by tailoring the backup approach to each container's specific characteristics, data volume, and change frequency. High-priority containers with critical data receive more frequent and complete backups, while less critical containers use incremental or on-demand backup strategies. This selective approach maintains comprehensive protection coverage while optimizing backup time and resource consumption based on local container properties.

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS11288130B2Container-based application data protection method and system

Publication Date: 2022.03.29 TRILIO DATA INC

AI summary

A computer-implemented method of data protection for containerized applications includes initiating a backup process for a containerized application comprising an application template, application information, and application data. An application template associated with the application is saved to a first repository. Application information is identified and saved to a second repository. A persistent volume containing the application data is identified and at least some of the application data from the persistent volume is saved to a third repository. The application is then restored based on the saved template, application information and application data.