SaaS Backup and Recovery Through Hierarchical API Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems face challenges in providing efficient backup and recovery services for software-as-a-service (SaaS) applications due to their hierarchical nature and reliance on multiple application programming interfaces (APIs), complicating the access and management of relational tables with parent and child relationships.

Innovation Solution

A data management system (DMS) implements frameworks for discovery, backup, and restore that maintain hierarchical relationships between computing objects and tables, organizing them as logical entities and using APIs to access and restore data, enabling granular cascading restore operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If existing data management systems are used to manage SaaS data, then basic backup and recovery functions are provided, but the hierarchical nature and multiple APIs of SaaS applications complicate access and management of relational tables

Engineering Contradiction:
Improveaccess and management of relational tablesVSAvoidhierarchical nature and multiple APIs
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (data management system with discovery and restore frameworks) that mediates between the user and the complex SaaS hierarchical data structure. This intermediary automatically discovers hierarchical relationships, maps them to relational tables, and manages the complexity of multiple APIs, allowing users to access and manage data without directly dealing with the underlying complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the complex SaaS data hierarchy into manageable components by discovering and organizing data into parent-child relationships. The system divides the monolithic backup/recovery process into granular operations that can work with specific portions of the hierarchical structure, making access and management easier while handling the complexity internally.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If granular cascading restore operations are implemented, then precise control over restore scope is achieved, but system complexity increases

Engineering Contradiction:
Improvegranular control of restore operationsVSAvoidcascading restore framework
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic restore operations where the scope and depth of restoration can be adjusted based on user needs. The cascading restore framework dynamically determines which child objects to restore based on parent object selection, allowing flexible control over restore granularity without requiring complex manual configuration for each scenario.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary discovery actions to automatically map hierarchical relationships and dependencies before restore operations. By pre-establishing the understanding of parent-child relationships and data dependencies, the system enables granular restore control through simplified user interfaces without requiring complex real-time decision-making during the restore process.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If hierarchical relationships are maintained during backup and restore, then data integrity is preserved, but processing time and computational resources increase

Engineering Contradiction:
Improvedata integrityVSAvoidbackup and restore processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary discovery operations to pre-map hierarchical relationships and data dependencies before backup and restore operations. By establishing the hierarchical structure understanding in advance, the system can efficiently execute backups and restores while maintaining data integrity, avoiding the need to repeatedly analyze relationships during actual backup/restore operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12450128B2Backup and recovery for software-as-a-service data
Publication Date: 2025.10.21 RUBRIK INC
  • US12450128B2 patent drawing
  • US12450128B2 patent drawing
  • US12450128B2 patent drawing

AI summary

Methods, systems, and devices for data management are described. Software-as-a-service (SaaS) applications may host customers information in a distributed environment that is not directly accessible to the customers. In some SaaS applications each organization may have a settings computing object, a features computing object, and a set of projects computing objects. The hierarchical relationships in each of the projects computing objects may depend on the tables in the settings and features computing objects. A data management system (DMS) may include discovery, backup, refresh, and restore frameworks that maintain hierarchical relationships between computing objects and tables including the dependency of projects computing objects on settings or features computing objects.