Resilient Backup Storage with Application Catalogs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing backup systems rely on application-generated backups that are unusable without accompanying information, making them dependent on other types of backups for restoration, which can fail due to data corruption or unavailability.
Innovation Solution
A system that generates and stores application catalogs containing backup use information alongside application-specific backups in backup storages, allowing for independent restoration without relying on other backup types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If application-specific backups are stored without accompanying backup use information, then storage space is optimized, but the backups become unusable for restoration
Solution Approach 1:
The backup system is segmented into two independent components: application-specific backups and backup use information (application catalogs). These segments are stored separately but can be independently managed, allowing the backup data to be stored efficiently while the metadata is stored in a separate, easily accessible location.
Solution Approach 2:
An application catalog acts as an intermediary between the backup data and the restoration process. The catalog contains the necessary metadata and instructions that enable restoration without requiring the original application or additional backup information, bridging the gap between compact backup storage and reliable restoration.
2Reliability
If application catalogs are always stored with backups, then restoration reliability is improved, but storage requirements increase
Solution Approach 1:
The system performs preliminary actions by creating application catalogs during the backup process, but stores them in a separate, optimized location rather than duplicating them with each backup. This preliminary preparation ensures restoration capability without proportionally increasing storage requirements.
Solution Approach 2:
Instead of storing complete application catalogs with every backup, the system creates lightweight references or minimal metadata copies that point to the actual catalog information, reducing storage overhead while maintaining full restoration capability.
3Adaptability or versatility
If the system relies on other backup types for restoration, then backup versatility is improved, but system complexity increases due to interdependencies
Solution Approach 1:
The essential restoration information is extracted from the complex interdependent backup system and placed into standalone application catalogs. This extraction allows each backup type to be restored independently without requiring other backup types, reducing system complexity while maintaining versatility.
Solution Approach 2:
Each backup becomes self-sufficient by including or referencing its own application catalog, which contains all necessary restoration information. The backup system serves itself without requiring external dependency on other backup types, simplifying the overall system architecture.
Data Source
AI summary
A manager for providing services to clients includes persistent storage and an orchestration manager. The persistent storage includes protection policies. The orchestration manager obtains a backup from a client of the clients based on a protection policy of the protection policies; makes a determination that an application catalog associated with the client is not stored in backup storages; in response to making the determination: obtains the application catalog from the client; stores the application catalog in the backup storages; and stores the obtained backup in the backup storages.