Data storage resource allocation using blacklisting of resource request pools such as categories of data storage requests
US-2015324233-A1 · Nov 12, 2015 · US
US11983075B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11983075-B2 |
| Application number | US-202217901745-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 1, 2022 |
| Priority date | Feb 8, 2017 |
| Publication date | May 14, 2024 |
| Grant date | May 14, 2024 |
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.
A method and system for migrating data and metadata from a first backup system to a second backup system via a staging system is disclosed. The system accesses the backup data from the first backup system and restores it, along with the associated metadata, to a staging system. A metadata file is created at the staging system which comprises of the metadata that is to be migrated to the second backup system. The system then migrates the data from the staging system to the second backup system. The metadata is also migrated to the second backup system in a format such that it can be indexed. As a result, the migrated data can be browsed and searched based on one or more search criteria based on the associated metadata. Other details are provided herein.
Opening claim text (preview).
We claim: 1. A computer-implemented method for migrating data from a source backup system to a destination backup system, the computer-implemented method comprising: identifying at least one restored file stored at a staging system to migrate to a destination backup system, wherein: the at least one restored file has been restored to the staging system from a source backup system after having been previously backed up to the source backup system; generating first metadata associated with the at least one restored file, wherein the first metadata comprises metadata properties provided by a user, wherein the metadata properties comprise at least one property name and an associated value, wherein the first metadata indicates which of the at least one restored file stored at the staging system the first metadata is associated with; initiating a backup operation on the at least one restored file, wherein during the backup operation, the destination backup system: generates second metadata associated with the backup operation and the at least one restored file, and creates or updates an index with the second metadata, wherein the index is stored at the destination backup system; and incorporating the first metadata comprising the metadata properties into the index. 2. The computer-implemented method of claim 1 , further comprising causing the at least one restored file to be deleted from the staging system. 3. The computer-implemented method of claim 1 , further comprising: wherein the backup operation is executed on a subset of files restored at the staging system. 4. The computer-implemented method of claim 1 , further comprising: wherein the backup operation is initiated according to an information management policy. 5. The computer-implemented method of claim 4 , further comprising: wherein the information management policy provides migration criteria for which data to migrate from the source backup system to the destination backup system. 6. The computer-implemented method of claim 5 , further comprising: scanning the first metadata at the staging system to determine which files meet the migration criteria. 7. The computer-implemented method of claim 1 , further comprising: querying the index of the destination backup system based on a criteria, wherein the querying comprises accessing the first metadata. 8. The computer-implemented method of claim 1 , wherein the computer-implemented method is executed by one or more virtual machines. 9. The computer-implemented method of claim 1 , further comprising: receiving, at a user interface, an indication from a user to start migrating data from the source backup system to the destination backup system, wherein the indication is based on a migration schedule. 10. The computer-implemented method of claim 1 , further comprising: receiving, at a user interface, a location of the staging system, wherein the location is a Network File System (NFS) network path of the staging system. 11. The computer-implemented method of claim 1 , further comprising: receiving, at a user interface, a location of the staging system, wherein the location is an Internet Protocol (IP) address. 12. The computer-implemented method of claim 1 , wherein the first metadata is generated automatically using a scripting engine, wherein the scripting engine parses contents in the staging system to identify files for migration to the destination backup system. 13. The computer-implemented method of claim 1 , wherein the first metadata at the staging system is queried to determine a subset of files for migration to the destination backup system. 14. The computer-implemented method of claim 13 , further comprising: receiving request to back up the at least one restored file to the destination backup system, wherein the at least one restored file is part of the subset of files determined for migration to the destination backup system. 15. A computing system for migrating data from a source backup system to a destination backup system, the computing system configured to: using one or more computer processors: identify at least one restored file stored at a staging system to migrate to a destination backup system, wherein: the at least one restored file has been restored to the staging system from a source backup system after having been previously backed up to the source backup system; generate first metadata associated with the at least one restored file, wherein the first metadata comprises metadata properties provided by a user, wherein the metadata properties comprise at least one property name and an associated value, wherein the first metadata indicates which of the at least one restored file stored at the staging system the first metadata is associated with; initiate a backup operation on the at least one restored file, wherein during the backup operation, the destination backup system: generates second metadata associated with the backup operation and the at least one restored file, and creates or updates an index with the second metadata, wherein the index is stored at the destination backup system; and incorporate the first metadata comprising the metadata properties into the index. 16. The computing system of claim 15 , the computing system further configured to: cause the at least one restored file to be deleted from the staging system. 17. The computing system of claim 15 , wherein the backup operation is executed on a subset of files restored at the staging system. 18. The computing system of claim 15 , wherein the backup operation is initiated according to an information management policy. 19. The computing system of claim 18 , wherein the information management policy provides migration criteria for which data to migrate from the source backup system to the destination backup system. 20. The computing system of claim 19 , the computing system further configured to: scan the first metadata at the staging system to determine which files meet the migration criteria. 21. The computing system of claim 15 , the computing system further configured to: querying the index of the destination backup system based on a criteria, wherein the querying comprises accessing the first metadata. 22. The computing system of claim 15 , wherein the one or more computer processors is configured as one or more virtual machines. 23. The computing system of claim 15 , the computing system further configured to: receiving, at a user interface, an indication from a user to start migrating data from the source backup system to the destination backup system, wherein the indication is based on a migration schedule. 24. The computing system of claim 15 , the computing system further configured to: receiving, at a user interface, a location of the staging system, wherein the location is a Network File System (NFS) network path of the staging system. 25. The computing system of claim 15 , the computing system further configured to: receiving, at a user interface, a location of the staging system, wherein the location is an Internet Protocol (IP) address. 26. The computing system of claim 15 , wherein the first metadata is generated automatically using a scripting engine, wherein the scripting engine parses contents in the staging system to identify files for migration to the destination backup system. 27. The computing system of claim 15 , wherein
by selection of backup contents · CPC title
Management of the data involved in backup or backup restore · CPC title
for networked environments · CPC title
where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title
Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available (error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction of the data by redundancy in operations G06F11/14; error detection or correction by redundancy in hardware G06F11/16) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.