Methods and apparatus for data lifecycle analysis

• US 9,454,324 B1
• Filed: 12/18/2013
• Issued: 09/27/2016
• Est. Priority Date: 12/18/2013
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Madhavapeddi, Vijay
• Primary Examiner(s): Rojas, Midys
• Assistant Examiner(s): Choi, Charles
• Application Number:
  US14/133,371
• Time in Patent Office: 1,014 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/14 Error detection or correction of the data by redundancy in operation G06F11/16 takes precedence
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0649 Lifecycle management
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

Methods and apparatuses to determine similarity among data lifecycles of data sets protected via a backup store having one or more storage devices are described. Each data set may be associated with one data lifecycle indicating a schedule to store one or more copies of the data set in the storage devices. The backup store can have one or more polices. Each life cycle may be specified in one of the policies. Two or more of the policies may be consolidated into one single policy specifying an updated data lifecycle. In one embodiment, the updated data lifecycle and data lifecycles of the two or more polices may be similar according to the similarity determined. A particular one of the data set may be associated with one of the data lifecycles of the two or more polices. The storage device may be configured to back up the particular data set according to the updated data lifecycle of the one single policy.

Claims

1. A computer implemented method comprising:

providing a history of data lifecycles for a plurality of data sets protected via a backup store having one or more storage devices, wherein each data lifecycle represents a data path across one or more of the storage devices in time during which a data set has been copied or moved according to one of a first set of policies for backup maintained by the backup store, the data path including information recording the one or more storage devices and time the data set was copied or moved at each of the one or more storage devices;

determining, by a similarity analysis module, similarity measures among the data lifecycles, wherein the similarity measures indicate whether data path of the data lifecycles accessing the data sets are similar, including determining whether any of data paths of the lifecycles leads to a common target storage device;

consolidating, by a policy updating module, the first set of policies into a second set of policies based on the similarity measures of the data lifecycles, wherein a number of the second set of policies is smaller than a number of the first set of policies, wherein at least two or more of the first set of policies are combined into one single policy, wherein the two or more of the first set of policies are similar according to the similarity measures; and

in response to a client request to protect a particular data set, configuring the storage devices to back up the particular data set according to one of the second set of policies that is associated with the particular data set.

2. The method of claim 1, wherein the storage devices are partitioned into one or more pools, wherein a data lifecycle of each data set specifies one or more backup operations that has been performed according to a schedule indicated in the data lifecycle to copy respective data set of the data lifecycle to a destination one of the pools, and wherein backup operations of two similar data lifecycles backed up data to at least one common destination pool.

3. The method of claim 2, wherein the backup operations are characterized by attributes having values, wherein each data lifecycle is represented via a collection of attribute values, and wherein the determining of the similarity measures comprises:

identifying a difference between two collections of attribute values of two separate data lifecycles, wherein the two separate data lifecycles are similar if the difference is within a threshold value.

4. The method of claim 3, further comprising:

presenting a graphical view of at least one data lifecycle via a user interface, wherein the graphical view indicates backup operations according to the schedule of the at least one data lifecycle.

5. The method of claim 4, wherein the graphical view is updated in real time and wherein the updated graphical view indicates where in the pools the data set of the data lifecycle is currently stored.

6. The method of claim 3, wherein each pool is identified by an identifier, and wherein the attributes include a destination identifier for the destination pool of the backup operation.

7. The method of claim 6, wherein at least one of backup operations specified in a data set associated with a particular data lifecycle copies the data set associated with the particular data lifecycle from a source one of the pools to a particular destination pool to clone the data set associated with the particular data lifecycle, the source pool identified by a source identifier, the particular destination pool identified by a particular destination identifier and wherein the attributes include an ordered pool pair of the source identifier and the particular destination identifier to represent the at least one backup operation.

8. The method of claim 7, wherein the two collections of attribute values include a first collection and a second collection separately representing a first one and a second one of the two separate data lifecycles, wherein the first collection includes a first ordered pool pair for a certain backup operation, wherein the difference between the two separate data lifecycles is greater than the threshold value if the second collection does not include the first ordered pool pair.

9. The method of claim 8, wherein the attributes include a schedule for each backup operation, wherein the attributes include a temporal sequence associated with scheduled times of the backup operations of the schedule, wherein the first collection includes a first temporal sequence for a first backup operations of the first one of the two separate data lifecycles, wherein the second collection includes a second temporal sequence for a second backup operation of the second one of the two separate data lifecycles, wherein the difference between the two separate data lifecycles is greater than the threshold value if the first temporal sequence and the second temporal sequence are not temporally alignable within a threshold time granularity, wherein the first temporal sequence includes a first number of time durations of the first temporal sequence, wherein the second temporal sequence includes a second number of time durations of the second temporal sequence, and wherein the first temporal sequence and the second temporal sequence are alignable if the first number and the second number are of a common number and each pair of corresponding time durations differ within a threshold value.

10. A non-transient machine readable storage medium having instructions therein, which when executed by a machine, cause the machine to perform operations, the operations comprising:

providing a history of data lifecycles for a plurality of data sets protected via a backup store having one or more storage devices, wherein each data lifecycle represents a data path across one or more of the storage devices in time during which a data set has been copied or moved according to one of a first set of policies for backup maintained by the backup store, the data path including information recording the one or more storage devices and time the data set was copied or moved at each of the one or more storage devices;

determining similarity measures among the data lifecycles, wherein the similarity measures indicate whether data paths of the data lifecycles accessing the data sets are similar, including determining whether any of data paths of the lifecycles leads to a common target storage device;

consolidating the first set of policies into a second set of policies based on the similarity measures, wherein a number of the second set of policies is smaller than a number of the first set of policies, wherein at least two or more of the policies are combined into one single policy, wherein the two or more of the first set of policies are similar according to the similarity measures; and

in response to a client request to protect a particular data set, configuring the storage devices to back up the particular data set according to one of the second set of policies that is associated with the particular data set.

11. The medium of claim 10, wherein the storage devices are partitioned into one or more pools, wherein a data lifecycle of each data set specifies one or more backup operations that has been performed according to a schedule indicated in the data lifecycle to copy respective data set of the data lifecycle to a destination one of the pools, and wherein backup operations of two similar data lifecycles backed up data to at least one common destination pool.

12. The medium of claim 11, wherein the backup operations are characterized by attributes having values, where each data lifecycle is represented via a collection of attribute values and wherein the determining of the similarity measures comprises:

identifying a difference between two collections of attribute values of two separate data lifecycles, wherein the two separate data lifecycles are similar if the difference is within a threshold value.

13. The medium of claim 12, wherein the attributes include a retention duration for each destination pool identified in each backup operation, wherein the data set of the data lifecycle is retained in the destination pool identified for the retention duration after being copied to the destination pool, wherein a similarity measure of the two data lifecycles depends on whether two retention durations for a commonly identified destination pool specified in the two data lifecycles differ within a threshold time margin.

14. The medium of claim 11, wherein the history of data lifecycles includes a selected recent portion of data lifecycles stored for the backup store and current data lifecycles.

15. The medium of claim 11, wherein the backup requirements specify a backup schedule to one of the destination pool and wherein the one consolidated policy includes one backup operation to the destination pool according to the backup schedule.

16. The medium of claim 15, wherein the additional policy is generated via a modification of the one consolidated policy according to the backup requirements.

17. A computer system comprising:

a memory storing executable instructions;

a network interface coupled to one or more storage devices;

a processor coupled to the memory and the network interface to execute the instructions from the memory, the processor being configured to provide a history of data lifecycles for a plurality of data sets protected via a backup store having one or more storage devices, wherein each data lifecycle represents a data path across one or more of the storage devices in time during which a data set has been copied or moved according to one of a first set of policies for backup maintained by the backup store, the data path including information recording the one or more storage devices and time the data set was copied or moved at each of the one or more storage devices;

determine similarity measures among the data lifecycles, wherein the similarity measures indicate whether data paths of the data lifecycles accessing the data sets are similar, including determining whether any of data paths of the lifecycle leads to a common target storage device;

consolidate the first set of policies into a second set of policies based on the similarity measures, wherein a number of the second set of policies is smaller than a number of the first set of policies, wherein at least two or more of the policies are combined into one single policy, wherein the two or more of the first set of policies are similar according to the similarity measures, and

in response to a client request to protect a particular data set, configure the storage devices to back up the particular data set according to one of the second set of policies that is associated with the particular data set.

18. The system of claim 17, wherein the storage devices are partitioned into one or more pools, wherein a data lifecycle of each data set specifies one or more backup operations that has been performed according to a schedule indicated in the data lifecycle to copy respective data set of the data lifecycle to a destination one of the pools, and wherein backup operations of two similar data lifecycles backed up data to at least one common destination pool.

19. The system of claim 18, wherein the backup operations are characterized by attributes having values, wherein each data lifecycle is represented via a collection of attribute values and wherein the determining of the similarity measures comprises:

identifying a difference between two collections of attribute values of two separate data lifecycles, where in the two separate data lifecycles are similar if the difference is within a threshold value.

20. The system of claim 19, the processor further configured to:

present a graphical view of at least one data lifecycle via a user interface, wherein the graphical view indicating backup operations according to a schedule of the at least one data lifecycle.

21. The system of claim 20, wherein the data set was copied to a particular one of the pools and wherein the graphical view indicates which period of time the data set was stored in the particular pool.