Managing snaps at a destination based on policies specified at a source

US10678650B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-10678650-B1
Application numberUS-201514674358-A
CountryUS
Kind codeB1
Filing dateMar 31, 2015
Priority dateMar 31, 2015
Publication dateJun 9, 2020
Grant dateJun 9, 2020

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Improved techniques for managing snaps of a data object hosted by a source data storage system (source) involve specifying, by the source, a set of policies for snaps of the data object that are stored on a destination data storage system (destination). The technique includes transferring the set of policies from the source to the destination, to enable the destination to implement the specified set of policies on the snaps at the destination.

First claim

Opening claim text (preview).

What is claimed is: 1. A method of managing snaps of data objects, the method comprising: establishing, on a source data storage system (source) storing a data object, policy information specifying a set of policies to be implemented at a destination data storage system (destination) on snaps of the data object created at the source and mirrored to the destination, each of the snaps at the destination (destination snaps) representing a point-in-time version of the data object at the source; and transferring the policy information established at the source to the destination to enable the destination to implement the set of policies specified by the policy information on the destination snaps at the destination, wherein the data object is a file system, wherein the policy information includes snap-specific policy information transmitted from the source to the destination for respective destination snaps, wherein the snap-specific policy information for a particular destination snap includes a file system consistency check policy, the file system consistency check policy specifying whether the destination is to perform a file system consistency check on the destination snap to verify that file system metadata of the destination snap is internally consistent, and wherein the method further comprises receiving, by the source, a result of a file system consistency check performed by the destination on the particular destination snap, the result indicating a set of errors in the metadata of the particular destination snap, the set of errors including an error indicating that the destination found certain metadata within the particular snap to be inconsistent with other metadata within the particular snap, wherein the policy information includes data-object-specific policy information transmitted from the source to the destination for the destination snaps of the data object created at the source and mirrored to the destination, and wherein the data-object-specific policy information for the destination snaps of the data object created at the source and mirrored to the destination includes a file-based restore policy, the file-based restore policy specifying a fraction of the destination snaps on which a file-based restore operation may be performed to restore, to the data object on the source, a file in a destination snap of the fraction of the destination snaps. 2. A method as in claim 1 , wherein the set of policies to be implemented at the destination includes a retention policy to be implemented on one or more of the destination snaps, the retention policy specifying a length of time that the destination snaps are to be retained at the destination, and wherein the method further comprises retaining, by the destination, a set of the snaps at the destination for a length of time not less than the length of time specified by the retention policy. 3. A method as in claim 2 , wherein the snap-specific policy information for a particular destination snap includes a file-based restore policy, the file-based restore policy specifying whether a file-based restore operation may be performed on the destination snap to restore a file in the destination snap to the data object on the source. 4. A method as in claim 3 , further comprising: receiving, by the source from a host, a request to perform the file-based restore operation, the request pertaining to a particular directory in the file system; obtaining, from the destination by the source, a list of the destination snaps that include the specified directory; and restoring, from one of the destination snaps on the list of destination snaps, a set of files in the specified directory to the specified directory on the file system on the source. 5. A method as in claim 2 , wherein the set of policies includes a deduplication policy, the deduplication policy specifying whether the destination is to perform block-based deduplication on the destination snaps; wherein the method further comprises the destination performing block-based deduplication on the destination snaps in response to the deduplication policy indicating that the destination is to perform block-based deduplication on the destination snaps. 6. A method as in claim 2 , wherein the set of policies a compression policy, the compression policy specifying whether the destination is to perform data compression on the destination snaps; wherein the method further comprises the destination performing data compression on the destination snaps in response to the compression policy indicating that the destination is to perform data compression on the destination snaps. 7. A method as in claim 2 , further comprising: providing a container file system in the source for storing source container files that realize the data object and snaps of the data object at the source, wherein the set of policies includes a container file system policy specifying a configuration of a destination container file system in the destination for storing the destination snaps, and wherein transferring the policy information to the destination enables the destination to configure the destination container file system as specified by the container file system policy. 8. A method as in claim 2 , further comprising: on the source, comparing a first source snap of the data object with a second source snap of the data object to produce a difference; transmitting the difference from the source to the destination; and on the destination, adding the difference to a first destination snap to produce a second destination snap, the first destination snap being a mirror of the first source snap and the second destination snap being a mirror of the second source snap, wherein the policy information includes snap-specific policy information transmitted from the source to the destination for respective destination snaps, and wherein transferring the snap-specific policy information from the source to the destination is performed when transmitting the difference from the source to the destination. 9. A method as in claim 1 , further comprising: updating the data object at the source to correct the set of errors indicated in the result of a file system consistency check performed by the destination. 10. A method as in claim 1 , further comprising: receiving, by the source, a result of a second file system consistency check performed by the destination on a second destination snap, the result indicating that the second destination snap is in a consistent state, and upon a detection of improper behavior of the data object at the source, restoring the data object at the source from the second destination snap at the destination. 11. A method as in claim 1 wherein transferring the policy information established at the source to the destination includes specifying an event, in the snap-specific policy information for the particular destination snap, which triggers the destination to perform the file system consistency check on the particular file system. 12. A method as in claim 11 wherein, when receiving the result of the file system consistency check performed on the destination, the method further includes receiving, by the source from the destination, suggestions for repairing the file system. 13. A system configured to manage snaps of data objects, the system comprising: a source data storage system (source); and a destination data storage system (destination), the source data storage system constructed and arranged to: establish policy information specifying a set of policies to be implemented at a destination data storage system (destination) on snaps of the data object c

Assignees

Inventors

Classifications

  • by selection of backup contents · CPC title

  • characterised by the use of retention policies (retention policies for HSM systems G06F16/185) · CPC title

  • using de-duplication of the data · CPC title

  • Ensuring data consistency and integrity · CPC title

  • Using snapshots, i.e. a logical point-in-time copy of the data · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10678650B1 cover?
Improved techniques for managing snaps of a data object hosted by a source data storage system (source) involve specifying, by the source, a set of policies for snaps of the data object that are stored on a destination data storage system (destination). The technique includes transferring the set of policies from the source to the destination, to enable the destination to implement the specifie…
Who is the assignee on this patent?
Emc Corp, Emc Ip Holding Co Llc
What technology area does this patent fall under?
Primary CPC classification G06F11/1451. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jun 09 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 4 related publications on this page (citations in our corpus or others sharing the same primary CPC).