Optimizing data location in data storage arrays

• US 9,459,809 B1
• Filed: 06/30/2014
• Issued: 10/04/2016
• Est. Priority Date: 06/30/2014
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Chen, Xiangping, de Forest, Miles A., Duprey, Dennis T., Owen, Karl M., Bono, Jean-Pierre, O'Brien, Walter A. III
• Primary Examiner(s): Riad, Amine
• Application Number:
  US14/319,566
• Time in Patent Office: 827 Days
• Field of Search: 714/6.23
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/2092 Techniques of failing over between control units
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 2212/1016 Performance improvement
• CPC Class Codes: G06F 2212/262 configured as RAID
• CPC Class Codes: G06F 2212/286 Mirrored cache memory
• CPC Class Codes: G06F 2212/466 Metadata, control data
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0617 in relation to availability
• CPC Class Codes: G06F 3/0644 Management of space entities, e.g. partitions, extents, pools
• 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]
• CPC Class Codes: G06F 3/0683 Plurality of storage devices
• CPC Class Codes: G06F 3/0685 Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays

Abstract

A technique is used for optimizing data location in data storage arrays. A primary storage array is associated with a secondary storage array, the primary storage array and secondary storage array including auto-tiering functionality, where the secondary storage array is configured as a backup storage array for the primary storage array. Tiering metadata is derived for a storage object stored on the primary storage array. The tiering metadata is transmitted to the secondary storage array. Auto-tiering is initiated at the secondary storage array, where the received tiering metadata is provided as input to the secondary storage array'"'"'s auto-tiering function when auto-tiering replicated storage object associated with the tiering metadata.

Claims

1. A method for optimizing location of storage objects in a storage array, the method comprising:

associating a primary storage array with a secondary storage array, the primary storage array and secondary storage array including auto-tiering functionality, wherein the secondary storage array is configured as a backup storage array for the primary storage array;

deriving tiering metadata for storage object stored on the primary storage array;

transmitting the tiering metadata for the storage object to the secondary storage array;

receiving, at the secondary storage array, tiering metadata derived at the primary storage array;

initiating auto-tiering at the secondary storage array, wherein the received tiering metadata is provided as input to the auto-tiering function when auto-tiering replicated storage objects associated with the tiering metadata;

identifying a failover event at the primary storage array;

initiating failover for one or more production sites associated with the primary storage array from the primary storage array to the secondary storage array;

deriving subsequent data tiering metadata based on an activity level of the storage object activity occurring at the secondary storage array; and

using the subsequent data tiering metadata as input to the secondary storage array'"'"'s auto-tiering function.

2. The method of claim 1, wherein the tiering metadata includes temperature data associated with the storage object.

3. The method of claim 1, wherein the tiering metadata includes temperature data and user preference information associated with the storage object.

4. The method of claim 1, wherein deriving tiering metadata includes determining temperature data for the storage object, wherein the temperature data calculated as a function of the auto-tiering.

5. The method of claim 1, wherein the tiering metadata is transmitted from the primary storage array to the secondary storage array on a periodic, aperiodic, event driven, user initiated or on-demand basis.

6. The method of claim 1, wherein the auto-tiering functionality includes migrating high temperature storage objects to high performance tiers and low temperature storage objects to low performance tiers.

7. The method of claim 1, wherein storage objects stored on the secondary storage array are a copy of the storage objects stored on the primary array and, upon initiating failover, the performance of storage objects stored on the secondary storage array substantially equals performance of the storage objects stored on the primary storage array prior to initiating failover.

8. The method of claim 1, wherein replicated storage objects are stored on secondary storage array tier types that correspond to primary storage array tier types where the storage objects from which the replicated storage objects were replicated are stored.

9. The method of claim 1, wherein the tiering metadata includes information derived from read activity and write activity of the primary storage array storage object.

10. A system for optimizing location of storage objects in a storage array, the system configured to:

a primary storage array associated with a secondary storage array, the primary storage array and secondary storage array including auto-tiering functionality, wherein the secondary storage array is configured as a backup storage array for the primary storage array;

a first auto-tiering module configured to derive tiering metadata for a storage object stored on the primary storage array;

transmit the tiering metadata for the multiple storage object to the secondary storage array;

receive, at the secondary storage array, tiering metadata derived at the primary storage array;

a second auto-tiering module configured to initiate auto-tiering at the secondary storage array, wherein the received tiering metadata is used as input to the auto-tiering function when auto-tiering replicated storage objects associated with the tiering metadata;

identify a failover event at the primary storage array;

initiate failover for one or more production sites associated with the primary storage array from the primary storage array to the secondary storage array;

derive subsequent data tiering metadata based on an activity level of the storage object activity occurring at the secondary storage array; and

provide the subsequent data tiering metadata as input to the secondary storage array'"'"'s auto-tiering function.

11. The system of claim 10, wherein the tiering metadata includes temperature data associated with the storage object.

12. The system of claim 10, wherein the tiering metadata includes temperature data and user preference information associated with the storage object.

13. The system of claim 10, wherein derive tiering metadata includes determining temperature data for the storage object, wherein the temperature data calculated as a function of the auto-tiering.

14. The system of claim 10, wherein the tiering metadata is transmitted from the primary storage array to the secondary storage array on a periodic, aperiodic, event driven, user initiated or on-demand basis.

15. The system of claim 10, wherein the auto-tiering module initiates migration of high temperature storage objects to high performance tiers and low temperature storage objects to low performance tiers.

16. The system of claim 10, wherein storage objects stored on the secondary storage array are a copy of the storage objects stored on the primary array and, upon initiating failover, the performance of storage objects stored on the secondary storage array substantially equals the performance of the storage objects stored on the primary storage array prior to initiating failover.

17. The system of claim 10, wherein replicated storage objects are stored on secondary storage array tier types that correspond to primary storage array tier types where the storage objects from which the replicated storage objects were replicated are stored.

18. The system of claim 10, wherein the tiering metadata includes information derived from read activity and write activity of the primary storage array storage object.