Supporting non-snappable data sources
US-2024248991-A1 · Jul 25, 2024 · US
US12450128B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12450128-B2 |
| Application number | US-202318513288-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 17, 2023 |
| Priority date | Nov 17, 2023 |
| Publication date | Oct 21, 2025 |
| Grant date | Oct 21, 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. 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.
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 a settings computing object, a features computing object, and a set of other computing objects, wherein the settings computing object comprises a first set of tables having a first set of hierarchical relationships, wherein the features computing object comprises a second set of tables having a second set of hierarchical relationships, and wherein other computing objects within the set of other computing objects comprise respective third sets of tables having respective third sets of hierarchical relationships, the respective third sets of hierarchical relationships based at least in part on the first set of tables; 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 first set of tables, the second set of tables, and the respective third 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 and information regarding the first set of hierarchical relationships, the second set of hierarchical relationships, and the respective third sets of hierarchical relationships in a second storage environment associated with the data management system, wherein the snapshots comprise the first set of tables, the second set of tables, and the respective third sets of tables, and wherein, within the second storage environment, the first set of tables, the second set of tables, and the respective third 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 other computing objects and the respective third sets of hierarchical relationships, wherein the accessing, the assigning, and the storing is based at least in part on identification of the set of other computing objects and the respective third sets of hierarchical relationships. 3. The method of claim 2 , further comprising: identifying, at a second time subsequent to the first time by the data management system and via the set of application programming interfaces, an update to the set of other computing objects and the respective third sets of hierarchical relationships. 4. The method of claim 2 , wherein: a first quantity of tables included in the first set of tables is static, a second quantity of tables included in the second set of tables is static, and a third quantity of tables included in the respective third sets of tables is static. 5. The method of claim 4 , wherein: a first set of table groups from among the respective table groups are associated with the settings computing object, a second set of table groups from among the respective table groups are associated with the features computing object, and a third set of table groups of the respective table groups are associated with the set of other computing objects. 6. The method of claim 5 , wherein: a first quantity of table groups included in the first set of table groups is static, a second quantity of table groups included in the second set of table groups is static, and a third quantity of table groups included in the third set of table groups is static. 7. The method of claim 4 , wherein tables in the first set of tables, the second set of tables, and the respective third sets of tables are static tables. 8. The method of claim 1 , further comprising: recording, by the data management system, respective tokens upon completion of storing respective table groups. 9. The method of claim 8 , 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. 10. The method of claim 1 , wherein: snapshots of the settings computing object and of the features computing object are full snapshots, and snapshots of the set of other computing objects comprise incremental snapshots. 11. The method of claim 1 , further comprising: receiving, by the data management system, a second request to restore a first computing object to the first storage environment, the first computing object being one of the settings computing object, the features computing object, or one of the set of other computing objects; 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 first set of hierarchical relationships, the second set of hierarchical relationships, or the respective third sets of hierarchical relationships, wherein the one or more second computing objects are one or more of the settings computing object, the features computing object, or one of the set of other computing objects; 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 11 , further comprising: presenting, via a user interface, a plurality of computing objects in hierarchical relationships with the first computing object, the plurality of computing objects comprising the one or more second computing objects; and receiving, via the user interface, a selection of the one or more second computing objects of the plurality of computing objects. 13. The method of claim 11 , wherein the second request comprises a request to restore a table of the first set of tables, the second set of tables, or the respective third sets of tables, the method further comprising: identifying the first computing object based at least in part on the request to restore the table. 14. The method of claim 11 , wherein the second request comprises a request to restore a logical component of the software-as-a-service application, the method further comprising: determining that the first computing object is included in a group of computing objects associated with the logical component. 15. The method of claim 1 , further comprising: receiving, by the data management system, a second request to restore a first computing object to a third storage environment, the first computing object being one of the settings computing object, the features computing object, or one of the set of other computing objects; identifying, by the
by selection of backup contents · CPC title
Display of status information · CPC title
Using snapshots, i.e. a logical point-in-time copy of the data · CPC title
Backup scheduling policy · CPC title
for networked environments · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.