Live configurable storage

• US 9,891,835 B2
• Filed: 01/30/2017
• Issued: 02/13/2018
• Est. Priority Date: 03/11/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Patel, Sachin Chiman, Rajpal, Shiv, Mehra, Karan
• Primary Examiner(s): Mackall, Larry T
• Application Number:
  US15/419,792
• Publication Number:
  US 20170235498A1
• Time in Patent Office: 379 Days
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0608 Saving storage space on storage systems
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0614 Improving the reliability of storage systems
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0631 by allocating resources to storage systems
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/0649 Lifecycle management
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0685 Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD

Abstract

A system for storing data in a dynamic fashion. The system includes a storage entity. The storage entity includes portions of a plurality of different persistent storage devices. Each storage device has a set of constraints. The storage entity is configured to store data in a dynamic fashion in a layout on the persistent storage devices of the storage entity that meets the different data requirements for the data while still being within the constraints for the persistent storage devices. The storage entity is configured to change the layout for a portion of the data as requirements related to at least one of performance or resiliency for a portion of the data change while the storage entity continues to provide the data from the storage entity.

Claims

1. A persistent storage entity comprising:

a plurality of storage tiers, at least one storage tier comprising a first type of persistent storage device and at least one other storage tier comprising a second type of persistent storage device;

one or more computer-readable media storing computer-executable instructions;

one or more processors which, when executing the computer-executable instructions, cause the persistent storage entity to dynamically change a layout configuration for data stored at storage tiers of the persistent storage entity, and wherein dynamically changing the layout configuration comprises;

receiving a request to store data;

identifying requirements for storing the received data, wherein the requirements comprise at least one of performance relating to how quickly the data is required to be accessed, or resiliency relating to maintaining availability within a specified statistical figure of the data in the event of a hardware failure at the persistent storage entity;

in accordance with either or both of the performance and resilience requirements identified for the received data, changing an initial data layout of the at least one storage tier, wherein changing the initial data layout does not disturb performance or resilience requirements of data already stored in the initial data layout; and

using the changed data layout of the at least one storage tier, storing the data at the at least one storage tier.

2. The system of claim 1, wherein the first type of persistent storage device comprises one or more hard disk drives (HDDs), and wherein the second type of persistent storage device comprises one or more solid state drives (SSDs).

3. The system of claim 1, wherein the persistent storage entity dynamically changes the initial data layout while the persistent storage entity is storing and providing data.

4. The system of claim 1, wherein the persistent storage entity dynamically changes the initial data layout from simple to mirrored storage by copying existing data from one persistent storage device to another persistent storage device while the persistent storage entity is storing and providing data from the first persistent storage device.

5. The system of claim 1, wherein the persistent storage entity dynamically changes the initial data layout from simple to striped storage by copying at least a portion of existing data from one persistent storage device to another persistent storage device while the persistent storage entity is storing and providing data from the first persistent storage device.

6. The system of claim 1, wherein the persistent storage entity dynamically changes the initial data layout from simple to parity storage by copying at least a portion of existing data from one persistent storage device to another persistent storage device while the persistent storage entity is storing and providing data from the first persistent storage device.

7. The system of claim 1, wherein the persistent storage entity dynamically changes the capacity of the storage entity while the persistent storage entity is storing and providing data.

8. The system of claim 1, wherein the persistent storage entity dynamically changes the resiliency of at least a portion of data stored at the persistent storage entity while the persistent storage entity is storing and providing data.

9. The system of claim 1, wherein the persistent storage entity dynamically changes the performance of at least a portion of data stored at the persistent storage entity while the persistent storage entity is storing and providing data.

10. A computer-implemented method of changing a layout configuration for data stored at storage tiers of a persistent storage entity to allow for changing requirements regarding performance or resiliency of data, the computer-implemented method being performed by one or more processors executing computer executable instructions for the computer-implemented method, and the computer-implemented method comprising:

receiving at a persistent storage entity a request to store data;

identifying requirements for storing the received data, wherein the requirements comprise at least one of performance relating to how quickly the data is required to be accessed, or resiliency relating to maintaining availability within a specified statistical figure of the data in the event of a hardware failure at the persistent storage entity;

in accordance with either or both of the performance and resilience requirements identified for the received data, changing an initial data layout of the at least one storage tier, wherein changing the initial data layout does not disturb performance or resilience requirements of data already stored in the initial data layout; and

using the changed data layout of the at least one storage tier, storing the data at the at least one storage tier.

11. The method of claim 10, wherein dynamically changing the initial data layout for the data in the persistent storage entity comprises dynamically changing the initial data layout by converting the data from mirror to parity.

12. The method of claim 10, wherein changing the initial data layout for the data in the persistent storage entity comprises dynamically changing the initial data layout by converting the data from striped mirror to non-striped mirror.

13. The method of claim 10, wherein changing the initial data layout for the data in the persistent storage entity comprises dynamically changing the initial data layout by transferring the data from the persistent storage device of the first type to the persistent storage device of the second type.

14. The method of claim 10, wherein changing the initial data layout for the data in the persistent storage entity comprises dynamically changing the initial data layout by converting the data from a device that is resilient to a first number of device failures to a second different number of device failures.

15. The method of claim 10, wherein changing the initial data layout results in a dynamic change to the capacity of the persistent storage entity.

16. The method of claim 10, wherein changing the initial data layout results in a dynamic change to the performance of data access of the data.

17. The method of claim 10, wherein changing the initial data layout results in a dynamic change to the resiliency of the data.

18. The method of claim 10, wherein the identified requirements for the received data are based on one or more of access patterns, an application operating on or creating data, user role of a user creating or operating on data, service agreement levels, enterprise department generating or operating on data, time of day, network characteristics, or protocols of data.

19. The method of claim 10, wherein identifying constraints of the persistent storage devices in the persistent storage entity, comprises identifying one or more of capacity, drive type, or drive speed.

20. A computer-implemented method of dynamically changing a layout configuration for data stored at a persistent storage entity to allow for changing requirements regarding performance or resiliency of data that is stored over time, the computer-implemented method being performed by one or more processors executing computer executable instructions for the computer-implemented method, and the computer-implemented method computer-implemented method comprising:

receiving at a persistent storage entity a request to store data, wherein the persistent storage entity has at least one storage tier comprising at least a first type of persistent storage device;

identifying requirements for storing the received data, wherein the requirements comprise at least one of performance relating to how quickly the data is required to be accessed, or resiliency relating to maintaining availability within a specified statistical figure of the data in the event of a hardware failure at the persistent storage entity;

identifying an initial data layout used at the at least one storage tier of the persistent storage entity, including identifying constraints of the at least first type of persistent storage device;

in accordance with either or both of the performance and resilience requirements identified for the received data, dynamically changing the initial data layout of the at least one storage tier while the persistent storage entity is storing and providing data, and wherein the dynamic change does not alter the identified constraints for the at least first type of persistent storage device so that performance or resilience requirements of data already stored in the initial data layout is undisturbed; and

using the changed data layout of the at least one storage tier, storing the data at the at least one storage tier.

21. The computer-implemented method of claim 20, wherein the at least first type of persistent storage device is used for different layout schemes.