Abstract: A method and system for recovering data from a storage system is disclosed. The method includes predicting, by a fault tolerance device, a fault within the storage system comprising one or more disk array enclosures, wherein each of the one or more disk array enclosures comprise a plurality of disks. The method further includes identifying, by the fault tolerance device, a data block going to be affected by occurrence of the predicted fault, wherein the data block is identified within a first disk in the plurality of disks. The method includes extracting, by the fault tolerance device, data stored in the data block before occurrence of the predicted fault. The method further includes transferring, by the fault tolerance device, the data extracted from the data block to a second disk not going to be affected by occurrence of the predicted fault. FIG. 2
Claims:WE CLAIM
1. A method of recovering data from a storage system, the method comprising:
predicting, by a fault tolerance device, a fault within the storage system comprising one or more disk array enclosures, wherein each of the one or more disk array enclosures comprise a plurality of disks;
identifying, by the fault tolerance device, a data block going to be affected by occurrence of the predicted fault, wherein the data block is identified within a first disk in the plurality of disks;
extracting, by the fault tolerance device, data stored in the data block before occurrence of the predicted fault; and
transferring, by the fault tolerance device, the data extracted from the data block to a second disk not going to be affected by occurrence of the predicted fault.
2. The method of claim 1 further comprising creating a hash map table comprising address mapping for each data block within the storage system, wherein address mapping for a data block within the storage system comprises memory address of the data block within a disk and identification of each of: the disk, a disk array enclosure comprising the disk, and a disk cluster comprising the disk array enclosure.
3. The method of claim 2, further comprising determining address of the data block going to be affected by occurrence of the predicted fault based on the hash map table.
4. The method of claim 3, wherein the data stored in the data block is extracted based on the determined address of the data block.
5. The method of claim 1 further comprising determining a type of the fault in order to identify the data block going to be affected by occurrence of the predicted fault.
6. The method of claim 1, wherein the first disk is within a first disk array enclosure from the one or more disk array enclosures and the second disk is within a second disk array enclosure from the one or more disk array enclosures.
7. The method of claim 6, wherein a management server enables transfer of the data in the data block within the first disk array enclosure to the second disk within the second disk array enclosure.
8. The method of claim 7 further comprising temporarily storing the data extracted from the data block in a memory within the management server before transferring to the second disk.
9. The method of claim 7, wherein when the management server is not capable of transferring the data, a fault tolerance module facilitates the transfer of data based on injection of one or more services of a master routing module in the management server.
10. A storage system comprising:
one or more disk array enclosures, wherein each of the one or more disk array enclosures comprises a plurality of disks; and
at least one controller communicatively coupled to the one or more disk array enclosures, wherein the at least one controller is configured to:
predict a fault within the storage system comprising one or more disk array enclosures, wherein each of the one or more disk array enclosures comprise a plurality of disks;
identify a data block going to be affected by occurrence of the predicted fault, wherein the data block is identified within a first disk in the plurality of disks;
extract data stored in the data block before occurrence of the predicted fault; and
transfer the data extracted from the data block to a second disk not going to be affected by occurrence of the predicted fault.
11. The storage system of claim 10, wherein the at least one controller is further configured to create a hash map table comprising address mapping for each data block within the storage system, wherein address mapping for a data block within the storage system comprises memory address of the data block within a disk and identification of each of: the disk, a disk array enclosure comprising the disk, and a disk cluster comprising the disk array enclosure.
12. The storage system of claim 11, wherein the at least one controller is further configured to determine address of the data block going to be affected by occurrence of the predicted fault based on the hash map table.
13. The storage system of claim 12, wherein the data stored in the data block is extracted based on the determined address of the data block.
14. The storage system of claim 10, wherein the at least one controller is further configured to determine a type of the fault in order to identify the data block going to be affected by occurrence of the predicted fault.
15. The storage system of claim 10, wherein the first disk is within a first disk array enclosure from the one or more disk array enclosures and the second disk is within a second disk array enclosure from the one or more disk array enclosures.
16. The storage system of claim 15, wherein a management server enables transfer of the data in the data block within the first disk array enclosure to the second disk within the second disk array enclosure.
17. The storage system of claim 16, wherein the controller is further configured to temporarily store the data extracted from the data block in a memory within the management server before transferring to the second disk.
18. The storage system of claim 16, wherein when the management server is not capable of transferring the data, a fault tolerance module is configured to facilitate the transfer of data based on injection of one or more services of a master routing module in the management server.
19. A management server for recovering data in a storage system, the disk management server comprising:
a processor;
a memory communicatively coupled to the processor and having instructions stored thereon, causing the processor, on execution to:
predict a fault within the storage system comprising one or more disk array enclosures, wherein each of the one or more disk array enclosures comprise a plurality of disks;
identify a data block going to be affected by occurrence of the predicted fault, wherein the data block is identified within a first disk in the plurality of disks;
extract data stored in the data block before occurrence of the predicted fault; and
transfer the data extracted from the data block to a second disk not going to be affected by occurrence of the predicted fault.
20. The disk management server of claim 18, wherein the instructions further cause the processor to create a hash map table comprising address mapping for each data block within the storage system, wherein address mapping for a data block within the storage system comprises memory address of the data block within a disk and identification of each of: the disk, a disk array enclosure comprising the disk, and a disk cluster comprising the disk array enclosure.
Dated this 30th day of June, 2017
R Ramya Rao
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
This disclosure relates generally to storage systems and more particularly to method and system for recovering data from storage systems.
| # | Name | Date |
|---|---|---|
| 1 | Power of Attorney [30-06-2017(online)].pdf | 2017-06-30 |
| 2 | Form 5 [30-06-2017(online)].pdf | 2017-06-30 |
| 3 | Form 3 [30-06-2017(online)].pdf | 2017-06-30 |
| 4 | Form 18 [30-06-2017(online)].pdf_154.pdf | 2017-06-30 |
| 5 | Form 18 [30-06-2017(online)].pdf | 2017-06-30 |
| 6 | Form 1 [30-06-2017(online)].pdf | 2017-06-30 |
| 7 | Drawing [30-06-2017(online)].pdf | 2017-06-30 |
| 8 | Description(Complete) [30-06-2017(online)].pdf_153.pdf | 2017-06-30 |
| 9 | Description(Complete) [30-06-2017(online)].pdf | 2017-06-30 |
| 10 | REQUEST FOR CERTIFIED COPY [03-07-2017(online)].pdf | 2017-07-03 |
| 11 | abstract 201741023081 .jpg | 2017-07-04 |
| 12 | 201741023081-Proof of Right (MANDATORY) [01-09-2017(online)].pdf | 2017-09-01 |
| 13 | Correspondence by Agent_Form 1_05-09-2017.pdf | 2017-09-05 |
| 14 | 201741023081-FER.pdf | 2020-07-07 |
| 15 | 201741023081-RELEVANT DOCUMENTS [16-12-2020(online)].pdf | 2020-12-16 |
| 16 | 201741023081-PETITION UNDER RULE 137 [16-12-2020(online)].pdf | 2020-12-16 |
| 17 | 201741023081-OTHERS [16-12-2020(online)].pdf | 2020-12-16 |
| 18 | 201741023081-Information under section 8(2) [16-12-2020(online)].pdf | 2020-12-16 |
| 19 | 201741023081-FORM 3 [16-12-2020(online)].pdf | 2020-12-16 |
| 20 | 201741023081-FER_SER_REPLY [16-12-2020(online)].pdf | 2020-12-16 |
| 21 | 201741023081-DRAWING [16-12-2020(online)].pdf | 2020-12-16 |
| 22 | 201741023081-CORRESPONDENCE [16-12-2020(online)].pdf | 2020-12-16 |
| 23 | 201741023081-COMPLETE SPECIFICATION [16-12-2020(online)].pdf | 2020-12-16 |
| 24 | 201741023081-CLAIMS [16-12-2020(online)].pdf | 2020-12-16 |
| 25 | 201741023081-ABSTRACT [16-12-2020(online)].pdf | 2020-12-16 |
| 26 | 201741023081-US(14)-HearingNotice-(HearingDate-01-05-2023).pdf | 2023-04-06 |
| 27 | 201741023081-POA [17-04-2023(online)].pdf | 2023-04-17 |
| 28 | 201741023081-FORM 13 [17-04-2023(online)].pdf | 2023-04-17 |
| 29 | 201741023081-Correspondence to notify the Controller [17-04-2023(online)].pdf | 2023-04-17 |
| 30 | 201741023081-AMENDED DOCUMENTS [17-04-2023(online)].pdf | 2023-04-17 |
| 31 | 201741023081-Written submissions and relevant documents [16-05-2023(online)].pdf | 2023-05-16 |
| 32 | 201741023081-FORM-26 [16-05-2023(online)].pdf | 2023-05-16 |
| 33 | 201741023081-FORM 3 [16-05-2023(online)].pdf | 2023-05-16 |
| 34 | 201741023081-PatentCertificate17-08-2023.pdf | 2023-08-17 |
| 35 | 201741023081-IntimationOfGrant17-08-2023.pdf | 2023-08-17 |
| 1 | SearchStrategyMatrix201741023081E_06-07-2020.pdf |