Storing data to cloud libraries in cloud native formats
Abstract
Systems and methods that facilitate an information management system to store sets of data, such as backup or secondary copies of production data, to cloud storage libraries in a format native to the cloud storage library are disclosed. The systems and methods create storage policies for the sets of data that identify the cloud storage libraries to which the sets of data are to be stored. Via the storage policies, one or more media agents or servers transfer data blocks of the sets of data to software development kits (SDKs) associated with the cloud storage libraries. The SDKs add external metadata, such as metadata associated with a native format for the cloud library (e.g., Microsoft Azure or other cloud computing service), to the data blocks, before the data blocks are stored to the cloud storage library.
Claims
exact text as granted — not AI-modified1 . (canceled)
2 . A computer-implemented method associated with an information management system, the method comprising:
by a storage manager of the information management system, storing a storage policy for a data set,
wherein the storage manager executes on a computing device comprising one or more hardware processors and computer memory,
wherein the storage policy identifies at least: the data set and a storage destination for a copy of the data set,
wherein the copy is to be generated by the information management system,
wherein the storage policy defines the destination as a cloud storage software development kit (SDK) of a cloud service subscription, and
wherein the cloud service providing the cloud service subscription comprises a cloud storage library for storing the copy;
by the storage manager, registering with the cloud service; by the storage manager, using the cloud storage SDK: to map the data set to one or more protected items of the cloud storage library, and to create a protection policy in the cloud service for the one or more protected items mapped to the data set; and by the storage manager, initiating a copy operation for the data set to the cloud storage library according to the storage policy, wherein the copy operation comprises:
generating a snapshot of the data set, and
at least by transferring data blocks in the snapshot to the cloud storage SDK, causing the cloud storage SDK to add cloud native metadata to the data blocks being stored at the cloud storage library.
3 . The method of claim 2 , wherein the data set is copied to the cloud storage library in a cloud native format.
4 . The method of claim 2 , wherein the data set is copied to the cloud storage library in a cloud native format, based at least in part on the storage policy and on the using of the cloud storage SDK.
5 . The method of claim 2 further comprising:
recovering the data set directly from the cloud storage library without using metadata of the information management system.
6 . The method of claim 2 , wherein a component of the information management system performs a software snapshot operation to generate the snapshot of the data set.
7 . The method of claim 2 , wherein a media agent component of the information management system, distinct from the storage manager, performs a software snapshot operation to generate the snapshot of the data set, and wherein the media agent executes on a computing device comprising one or more hardware processors and computer memory.
8 . The method of claim 2 , wherein the using of the cloud storage SDK by the storage manager causes the cloud service to associate the data set with the cloud storage library.
9 . The method of claim 2 , wherein the using of the cloud storage SDK by the storage manager further comprises creating a protection policy in the cloud service for the one or more protected items mapped to the data set.
10 . The method of claim 2 , wherein the using of the cloud storage SDK by the storage manager further comprises registering with the cloud service each backup job of the data set executed by the information management system, including the copy operation.
11 . The method of claim 2 , wherein the using of the cloud storage SDK by the storage manager further comprises selecting a snapshot engine in the cloud service.
12 . A non-transitory computer-readable medium comprising instructions that, when executed by a computing device comprising one or more hardware processors and computer memory, cause the computing device to perform operations in an information management system, the operations comprising:
executing a storage manager of the information management system; storing a storage policy for a data set,
wherein the storage policy identifies at least: the data set and a storage destination for a copy of the data set,
wherein the copy is to be generated by the information management system,
wherein the storage policy defines the destination as a cloud storage software development kit (SDK) of a cloud service subscription, and
wherein the cloud service providing the cloud service subscription comprises a cloud storage library for storing the copy;
registering with the cloud service; using the cloud storage SDK: to map the data set to one or more protected items of the cloud storage library, and to create a protection policy in the cloud service for the one or more protected items mapped to the data set; and initiating a copy operation for the data set to the cloud storage library according to the storage policy, comprising:
causing a snapshot of the data set to be generated, and
by causing the data blocks in the snapshot to be transmitted to the cloud storage SDK, causing the cloud storage SDK to add cloud native metadata to the data blocks, which are stored, with the cloud native metadata at the cloud storage library.
13 . The non-transitory computer-readable medium of claim 12 , wherein the data set is copied to the cloud storage library in a cloud native format.
14 . The non-transitory computer-readable medium of claim 12 , wherein the data set is copied to the cloud storage library in a cloud native format, based at least in part on the storage policy and on the using of the cloud storage SDK.
15 . The non-transitory computer-readable medium of claim 12 , the operations further comprising:
recovering the data set directly from the cloud storage library without using metadata of the information management system.
16 . The non-transitory computer-readable medium of claim 12 , the operations further comprising: causing another component of the information management system to perform a software snapshot operation to generate the snapshot of the data set.
17 . The non-transitory computer-readable medium of claim 12 , the operations further comprising: causing a media agent component of the information management system, distinct from the storage manager, to perform a software snapshot operation to generate the snapshot of the data set, wherein the media agent executes on an other computing device comprising one or more hardware processors and computer memory.
18 . The non-transitory computer-readable medium of claim 12 , wherein the using of the cloud storage SDK by the computing device executing the storage manager causes the cloud service to associate the data set with the cloud storage library.
19 . The non-transitory computer-readable medium of claim 12 , wherein the using of the cloud storage SDK by the computing device executing the storage manager further comprises creating a protection policy in the cloud service for the one or more protected items mapped to the data set.
20 . The non-transitory computer-readable medium of claim 12 , wherein the using of the cloud storage SDK by the computing device executing the storage manager further comprises registering with the cloud service each backup job of the data set executed by the information management system, including the copy operation.
21 . The non-transitory computer-readable medium of claim 12 , wherein the using of the cloud storage SDK by the computing device executing the storage manager further comprises selecting a snapshot engine in the cloud service.Join the waitlist — get patent alerts
Track US2021208977A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.