Backup data associated with a primary storage system is received. At least a view of the received backup data associated with the primary storage system is generated. The view of the of the received backup data associated with the primary storage system includes a tree data structure comprising a root node, a first plurality of child nodes, and a first plurality of leaf nodes. At least some of the first plurality of leaf nodes include corresponding pointers to a corresponding binary large object. A read request for data exposed by the view of the received backup data associated with the primary storage system is received from an external system. In response to receiving the read request, the view of the received backup data associated with the primary storage system is exposed to a requesting system utilizing a protocol associated with the external system.
Legal claims defining the scope of protection, as filed with the USPTO.
2. The method of claim 1, wherein the view of the received backup data associated with the primary storage system is associated with a namespace.
3. The method of claim 2, wherein the namespace is a file namespace, an object namespace, or a configuration namespace.
4. The method of claim 1, wherein at least a first leaf node of the first plurality of leaf nodes includes a key-value pair describing file system metadata.
5. The method of claim 1, wherein the primary storage system is running a database application, an OpenStack cluster, or a virtual machine cluster.
6. The method of claim 1, wherein the external system is running a non-production workload.
7. The method of claim 1, wherein the view of the received backup data associated with the primary storage system is exposed using server message block, a network file system, an internet small computer system interface, a Hadoop Distributed File system, or a representational state transfer (REST) protocol.
8. The method of claim 1, wherein the secondary storage system utilizes a protocol associated with the primary storage system to receive the backup data associated with the primary storage system.
9. The method of claim 1, wherein the view of the received backup data associated with the primary storage system is generated by cloning a second root node of a second tree data structure associated with a second view of the primary storage system.
10. The method of claim 9, wherein the cloned second root node includes pointers that reference some of the first plurality of the child nodes referenced by the second root node of the second tree data structure.
11. The method of claim 1, wherein a first leaf node of the first plurality of leaf nodes stores data as a value in a key-value pair.
12. The method of claim 1, wherein a size of the data is less than a limit.
13. The method of claim 1, wherein the view of the received backup data associated with the primary storage system is an incremental backup of the primary storage system.
15. The computer program product of claim 14, wherein the view of the received backup data associated with the primary storage system is associated with a namespace.
16. The computer program product of claim 15, wherein the namespace is a file namespace, an object namespace, or a configuration namespace.
17. The computer program product of claim 15, wherein the view of the received backup data associated with the primary storage system is exposed using server message block, a network file system, an internet small computer system interface, a Hadoop Distributed File system, or a representational state transfer (REST) protocol.
18. The computer program product of claim 14, wherein the view of the received backup data associated with the primary storage system is generated by cloning a second root node of a second tree data structure associated with a second view of the primary storage system.
19. The computer program product of claim 18, wherein the cloned second root node includes pointers that reference some of the first plurality of the child nodes referenced by the second root node of the second tree data structure.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
July 10, 2023
December 10, 2024
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.