DATA ARCHIVING AND RETRIEVAL SYSTEM

• US 20100257140A1
• Filed: 03/31/2010
• Published: 10/07/2010
• Est. Priority Date: 03/31/2009
• Status: Abandoned Application

• Current Assignee: Cumulus Data, LLC (Talen Energy Corporation)
• Original Assignee: Cumulus Data, LLC (Talen Energy Corporation)
• Inventors: Hall, Nathan Louis, Davis, Philip John, Gould, Elliot Lawrence, Moore, Daniel Joseph, Love, Joel Michael
• Application Number:
  US12/751,436
• Publication Number:
  US 20100257140A1
• Time in Patent Office: Days
• US Class Current: 707/661
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A method and system to store and retrieve archival data and indefinitely storing the data is disclosed. By using caches and large volumes of commodity disk drives controlled in a dynamic or scheduled way, power consumption of the archive system is reduced. Archive data is transferred to the archive facility via a channel, such as electronic or physical transportation, depending on a set of customer service level parameters. Archived data is replicated to a second facility to guard against multiple device failures or site disasters. The archived data is protected from erasure by both keeping the media predominantly unpowered and disabling writing to the media once it has been filled to capacity. The system provides access to indexable host and customer-specific metadata across the entire infrastructure without powering the media. All customer archive data is segregated from all other data by residing on per customer dedicated media.

Claims

1. A method of archiving data of a customer in to one or more remote archive data stores, the method comprising:

selecting at least one data transport channel through which to transfer archival data including the content data to the one or more archive data stores, based on at least one service level parameter associated with the customer;

transferring the archival package through at least one transport channel to the one or more remote archive data stores;

receiving an acknowledgment of a successful archiving of the archival package at the one or more archive data stores; and

optionally deleting the content data at the data provider in response to receipt of the acknowledgment.

2. The method of claim 1, wherein the archival package is built based on combining customer metadata, gateway metadata, and the content data.

3. The method of claim 2, wherein the archival package is built based upon at least one of the following:

the total size of the package, the time elapsed between archive sessions, or some predetermined event has occurred.

4. The method of claim 1, further comprising the step of scheduling a transfer event for transferring the archival package through the selected channel.

5. A method of retrieving archived data of a customer through at least one or more transport channels from one or more remote archive data stores, the method comprising:

issuing a request for retrieval of the specified content data from the one or more archive data stores;

establishing the plurality of transport channels;

receiving a notification of the at least one channel via which the specified content data will be received from the one or more remote archive data stores;

receiving the specified content data via at least one transport channel from the archive data stores; and

acknowledging receipt of content data.

6. The method of claim 5 whereby accessing a library of metadata describing archived data available to the customer and stored in the one or more remote archive data stores.

7. The method of claim 6 whereby the data within the remote archived data store includes metadata.

8. A method of archiving customer data received from customer, the method comprising:

receiving data for archiving from a customer, the data for archiving including the content data and a customer identifier;

indentifying an archival storage pool dedicated to the customer based on the customer identification, the dedicated archival storage pool being physically segregated from archival storage pools dedicated to other customers; and

transferring the customer content data to the identified archival storage pool.

9. The method of claim 8 whereby scheduling a transfer event for transferring the content data to the identified archival storage pool is based on customer metadata.

10. A method of transferring archived data from a storage pool to a customer, the method comprising:

receiving a request for the archived content data from the customer, the request including a customer identification and an archived content data identifier;

identifying a storage pool dedicated to the customer;

bringing the identified storage pool online to allow access to data stored on the identified storage pool;

reading the archived content data from the identified storage pool; and

transferring the read archived content data to the customer.

11. The method of claim 10 whereby data from different customers are segregated in different storage pools.

12. An archive management system for archiving customer data, comprising:

an archive manager;

at least one archive storage array; and

a customer metadata database;

wherein the archive manager receives data for archiving from multiple customers, caches, and aggregates the data for a determinable length of time, and manages routing of the data for archiving intervals to the at least one archive storage array in response to customer data stored in the customer metadata database, thereby archiving the data.

13. The system of claim 12, wherein the archive manager comprises a plurality of storage pools for storing the data for archiving.

14. The system of claim 13, wherein each customer'"'"'s archived data is stored in separate storage pools.

15. The system of claim 13, further comprising an archive master database containing location, status, and a unique identifier for all storage pools.

16. The system of claim 15, wherein the unique identifier for each storage pool comprises a customer identification and a sequence number.

17. The system of claim 12, further comprising at least one additional archive management system having substantially identical archived data.

18. The system of claim 12, further comprising at least one gateway interface for each customer, the gateway interface providing an interface between the corresponding customer and the archive management system.