Fetching Query Results Through Cloud Object Stores
US-2024394271-A1 · Nov 28, 2024 · US
US2016110264A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016110264-A1 |
| Application number | US-201414517011-A |
| Country | US |
| Kind code | A1 |
| Filing date | Oct 17, 2014 |
| Priority date | Oct 17, 2014 |
| Publication date | Apr 21, 2016 |
| Grant date | — |
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 and systems for restoring storage objects are provided. The method includes determining if a source storage object and a target storage object are located within a same storage volume, where the source storage object is associated with a first drive and the target storage object is associated with a second drive; and using a point in time copy of the source storage object for restoring the source storage object at the second drive.
Opening claim text (preview).
What is claimed is: 1 . A machine implemented method, comprising: determining if a source storage object and a target storage object are located within a same storage volume, where the source storage object is associated with a first drive and the target storage object is associated with a second drive; and using a point in time copy of the source storage object for restoring the source storage object at the second drive. 2 . The method of claim 1 , further comprising: taking the target storage object offline; and providing a point in time copy name to a restore module, when the point in time copy name is specified in a restore request. 3 . The method of claim 2 , further comprising: taking a point in time copy of the source storage object, when the point in time copy name is not specified in the restore request. 4 . The method of claim 1 , further comprising: taking the target storage object offline and unmapping it from a computing device, when the source storage object and the target storage object are located within the same storage volume; and generating a clone of the source storage object and naming the clone with a same name as the target storage object. 5 . The method of claim 4 , further comprising: mapping the clone of the source storage object to the computing device using the second storage drive. 6 . The method of claim 1 , wherein the source storage object and the target storage object are logical unit numbers (LUNs) used for storing information at a storage device. 7 . The method of claim 1 , wherein a storage system interface module maintains a mapping data structure that is used for restoring the source storage object at the second drive. 8 . A non-transitory, machine readable storage medium having stored thereon instructions for performing a method, comprising machine executable code which when executed by at least one machine, causes the machine to: determine if a source storage object and a target storage object are located within a same storage volume, where the source storage object is associated with a first drive and the target storage object is associated with a second drive; and use a point in time copy of the source storage object for restoring the source storage object at the second drive. 9 . The storage medium of claim 8 , wherein the machine executable code further causes the machine to: take the target storage object offline; and provide a point in time copy name to a restore module, when the point in time copy name is specified in a restore request. 10 . The storage medium of claim 9 , wherein the machine executable code further causes the machine to: take a point in time copy of the source storage object, when the point in time copy name is not specified in the restore request. 11 . The storage medium of claim 8 , wherein the machine executable code further causes the machine to: take the target storage object offline and unmapping it from a computing device, when the source storage object and the target storage object are located within the same storage volume; and generate a clone of the source storage object and naming the clone with a same name as the target storage object. 12 . The storage medium of claim 11 , wherein the machine executable code further causes the machine to: map the clone of the source storage object to the computing device using the second storage drive. 13 . The storage medium of claim 8 , wherein the source storage object and the target storage object are logical unit numbers (LUNs) used for storing information at a storage device. 14 . The storage medium of claim 8 , wherein a storage system interface module maintains a mapping data structure that is used for restoring the source storage object at the second drive. 15 . A system comprising: a memory with machine readable medium comprising machine executable code having stored thereon instructions; and a processor module coupled to the memory, the processor module configured to execute the machine executable code to: determine if a source storage object and a target storage object are located within a same storage volume, where the source storage object is associated with a first drive and the target storage object is associated with a second drive; and use a point in time copy of the source storage object for restoring the source storage object at the second drive. 16 . The system of claim 15 , wherein the machine executable code further causes the machine to: take the target storage object offline; and provide a point in time copy name to a restore module, when the point in time copy name is specified in a restore request. 17 . The system of claim 16 , wherein the machine executable code further causes the machine to: take a point in time copy of the source storage object, when the point in time copy name is not specified in the restore request. 18 . The system of claim 15 , wherein the machine executable code further causes the machine to: take the target storage object offline and unmapping it from a computing device, when the source storage object and the target storage object are located within the same storage volume; and generate a clone of the source storage object and naming the clone with a same name as the target storage object. 19 . The system of claim 18 , wherein the machine executable code further causes the machine to: map the clone of the source storage object to the computing device using the second storage drive. 20 . The system of claim 15 , wherein the source storage object and the target storage object are logical unit numbers (LUNs) used for storing information at a storage device. 21 . The system of claim 15 , wherein a storage system interface module maintains a mapping data structure that is used for restoring the source storage object at the second drive.
the resynchronized component or unit being a persistent storage device (re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008) · CPC title
Redundant storage or storage space (G06F11/2056 takes precedence) · CPC title
for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title
for networked environments · CPC title
Using snapshots, i.e. a logical point-in-time copy of the data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.