Cloud Backup Configuration Template Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for configuring backup and restore application instances in public clouds are cumbersome, error-prone, and difficult to maintain, especially when using cloud-init or Data Domain command line interface commands.
Innovation Solution
A configuration template framework that leverages cloud-init only to pass a configuration template from a deployment orchestration framework to the backup and restore application instance during deployment, and then uses custom plugins and a cloud provider's secret manager service to securely configure and manage the application instance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If cloud-init or Data Domain command line interface commands are used to configure backup and restore application instances, then the application can be deployed in public clouds, but the configuration process becomes cumbersome, error-prone, and difficult to maintain
Solution Approach 1:
The patent introduces a configuration template as an intermediary between the deployment orchestration framework and the backup and restore application instance. This template serves as a standardized interface that simplifies configuration by providing a structured format with predefined parameters, eliminating the need to directly use complex cloud-init commands or Data Domain CLI commands. The template acts as a mediator that translates high-level configuration intentions into specific deployment commands, making the process easier to operate and maintain while preserving cloud deployability.
2Ease of manufacture
If sensitive data is included in the configuration template, then the configuration is complete, but security is compromised
Solution Approach 1:
The patent extracts sensitive data from the configuration template and stores it separately in secure secret manager services provided by cloud providers. The configuration template contains only non-sensitive parameters needed for application deployment, while sensitive information such as credentials and keys are retrieved dynamically from external secure storage during the configuration process. This separation maintains configuration completeness while eliminating security risks associated with storing sensitive data in plain text within templates.
3Adaptability or versatility
If manual configuration methods are used, then flexibility is maintained, but errors increase and maintenance difficulty increases
Solution Approach 1:
The patent segments the configuration process into distinct components: a structured configuration template defining deployment parameters, validation rules that automatically check for errors, and automated processing steps that execute the configuration. This segmentation allows flexibility to be maintained through customizable template parameters while reducing errors through automated validation and processing. The structured approach also simplifies maintenance by allowing individual components to be modified independently without affecting the entire configuration process.
Data Source
AI summary
Providing template-based configuration for backup and restore applications in public clouds is described. A system identifies a deployment of an instance of a backup and restore application in a public cloud, and retrieves a configuration template, generated for the backup and restore application, from within the public cloud. The system retrieves restricted access data, which is excluded from the configuration template, from a secret manager service provided by a cloud provider associated with the public cloud. The system configures the instance of the backup and restore application based on the configuration template, generated for the backup and restore application, and the restricted access data, thereby initiating execution of the configured instance of the backup and restore application to back up a workload.