Supporting non-snappable data sources
US-2024248991-A1 · Jul 25, 2024 · US
US12455794B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12455794-B2 |
| Application number | US-202318513279-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 17, 2023 |
| Priority date | Nov 17, 2023 |
| Publication date | Oct 28, 2025 |
| Grant date | Oct 28, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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. SaaS applications may store data in the form of relational tables. Snapshots for SaaS applications may maintain hierarchical relationships between computing objects and tables to enable cascading recovery. A data management system (DMS) may identify the computing object hierarchy for an organization's data as hosted by a SaaS application and also may identify the APIs associated with accessing each computing object, which may each include multiple tables. Tables that are accessed via a same API may be organized as logical entities. The DMS may store the hierarchical relationship between the tables, and as the tables are stored as logical entities, the DMS may organize the tables in the backup database based on which APIs are used to access the relevant tables.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving, by a data management system, a request to back up a software-as-a-service application comprising a set of computing objects, wherein computing objects within the set of computing objects comprise respective sets of tables having respective hierarchical relationships; accessing, by the data management system based at least in part on the request and via a set of application programming interfaces for a first storage environment associated with the software-as-a-service application, the set of computing objects to obtain snapshots of the computing objects within the set of computing objects; assigning, by the data management system, tables within the respective sets of tables to respective table groups, wherein a table group comprises one or more tables associated with a same group of one or more application programming interfaces from among the set of application programming interfaces; and storing, by the data management system, the snapshots of the computing objects and information regarding the respective hierarchical relationships in a second storage environment associated with the data management system, wherein the snapshots comprise the respective sets of tables, and wherein, within the second storage environment, the respective sets of tables are stored in accordance with the assigned respective table groups. 2. The method of claim 1 , further comprising: identifying, at a first time by the data management system and using the set of application programming interfaces, computing objects within the set of computing objects and a first hierarchical relationship of the set of computing objects, wherein the accessing, the assigning, and the storing is based at least in part on identification of the set of computing objects and the first hierarchical relationship. 3. The method of claim 1 , further comprising: identifying, at a second time by the data management system and via the set of application programming interfaces, an update to the computing objects within the set of computing objects and a second hierarchical relationship of the set of computing objects. 4. The method of claim 3 , further comprising: determining, by the data management system, that a time period since a last update to the computing objects within the set of computing objects satisfies a threshold time period, wherein identifying the update and the second hierarchical relationship is based at least in part on the determining that the time period since the last update satisfies the threshold time period. 5. The method of claim 1 , wherein: a first set of table groups from among the respective table groups comprises dynamic tables, a second set of table groups from among the respective table groups comprises static tables, first schemas for the dynamic tables are determined via the accessing, and second schemas for the static tables are stored from prior snapshots of the computing objects. 6. The method of claim 1 , wherein storing the snapshots comprises: storing respective schemas of respective tables included in the respective sets of tables. 7. The method of claim 6 , wherein storing the respective schemas of the respective tables included in the respective sets of tables comprises: identifying updates to one or more of the respective schemas with respect to immediately prior snapshots of the computing objects. 8. The method of claim 1 , wherein an order in which the snapshots of the computing objects are stored is based at least in part on the respective table groups and the respective hierarchical relationships. 9. The method of claim 1 , further comprising: recording, by the data management system, respective tokens upon completion of storing respective table groups. 10. The method of claim 9 , further comprising: pausing the storing of the snapshots of the computing objects after storing a set of table groups included in the respective table groups; and resuming the storing of the snapshots of the computing objects to store a remainder of the respective table groups, wherein the remainder is identified based at least in part on the respective tokens, and wherein storing the snapshots of the computing objects comprises storing the remainder of the respective table groups. 11. The method of claim 1 , further comprising: receiving, by the data management system, a second request to restore a first computing object of the set of computing objects to the first storage environment; identifying, by the data management system and based at least in part on the second request, one or more second computing objects to restore based at least in part on the respective hierarchical relationships; identifying, a second set of application programming interfaces associated with the first computing object and the one or more second computing objects; and restoring, by the data management system and via the second set of application programming interfaces, the first computing object and the one or more second computing objects from the snapshots in the second storage environment to the first storage environment. 12. The method of claim 1 , wherein receiving the request comprises: receiving the request from a computing device associated with a user account of the data management system. 13. The method of claim 1 , wherein receiving the request comprises: identifying that a time for a scheduled backup operation for the software-as-a-service application has been satisfied. 14. An apparatus, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the apparatus to: receive, by a data management system, a request to back up a software-as-a-service application comprising a set of computing objects, wherein computing objects within the set of computing objects comprise respective sets of tables having respective hierarchical relationships; access, by the data management system based at least in part on the request and via a set of application programming interfaces for a first storage environment associated with the software-as-a-service application, the set of computing objects to obtain snapshots of the computing objects within the set of computing objects; assign, by the data management system, tables within the respective sets of tables to respective table groups, wherein a table group comprises one or more tables associated with a same group of one or more application programming interfaces from among the set of application programming interfaces; and store, by the data management system, the snapshots of the computing objects and information regarding the respective hierarchical relationships in a second storage environment associated with the data management system, wherein the snapshots comprise the respective sets of tables, and wherein the one or more processors are individually or collectively operable to execute the code to cause the apparatus to store the respective sets of tables within the second storage environment in accordance with the assigned respective table groups. 15. The apparatus of claim 14 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the apparatus to: identify, at a first time by the data management system and using the set of application programming interfaces, computing objects within the set of computing objects and a first hierarchical relationship of the set of computing objects, wherein the one or more processors are ind
by selection of backup contents · CPC title
Backup scheduling policy · CPC title
Using snapshots, i.e. a logical point-in-time copy of the data · CPC title
for networked environments · CPC title
Backup restoration techniques · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.