A data recovery method recovers corrupted data after a disaster event in a storage facility operating with deduplication in which copies of data are maintained between volumes through a copy services relationship. The deduplication operates with referencing domains, each having a source grain containing a reference pointing to a location where data is stored and referrers pointing to the source. The data recovery method identifies any source that is pointing to data which is corrupt and then establishes whether a copy services relationship exists between the referencing domain of the source with corrupted data and another referencing domain, in which case the other referencing domain will have a copy of the corrupted data. Provided that the copy is valid, it is written across to replace the corrupted data. The method allows corrupted source data to be recovered without having to perform a full resync or restore.
Legal claims defining the scope of protection, as filed with the USPTO.
2. The method of claim 1, wherein determining that the first copy services relationship exists between the first referencing domain and the second referencing domain includes checking for a first copy services relationship directly between the first source and another referencing domain.
3. The method of claim 1, wherein determining that the first copy services relationship exists between the first referencing domain and the second referencing domain includes scanning references to the first source to check whether a first copy services relationship exists between any referrer of the first source and another referencing domain.
6. The method of claim 1, wherein the determining whether the third copy is valid comprises checking that address ranges that are referred to by the third referencing domain are valid.
8. The system of claim 7, wherein determining that the first copy services relationship exists between the first referencing domain and the second referencing domain includes checking for a first copy services relationship directly between the first source and another referencing domain.
9. The system of claim 7, wherein determining that the first copy services relationship exists between the first referencing domain and the second referencing domain includes scanning references to the first source to check whether a first copy services relationship exists between any referrer of the first source and another referencing domain.
13. The computer program product of claim 12, wherein determining that the first copy services relationship exists between the first referencing domain and the second referencing domain includes checking for a first copy services relationship directly between the first source and another referencing domain.
14. The computer program product of claim 12, wherein determining that the first copy services relationship exists between the first referencing domain and the second referencing domain includes scanning references to the first source to check whether a first copy services relationship exists between any referrer of the first source and another referencing domain.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
March 16, 2020
August 30, 2022
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.