BACKUP POLICIES FOR USING DIFFERENT STORAGE TIERS

• US 20120117029A1
• Filed: 11/08/2010
• Published: 05/10/2012
• Est. Priority Date: 11/08/2010
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Gold, Stephen
• Application Number:
  US12/942,006
• Publication Number:
  US 20120117029A1
• Time in Patent Office: Days
• US Class Current: 707/651
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1453 using de-duplication of the data
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 2201/815 Virtual middleware or OS functionality using virtual machines to implement generic software techniques for error detection or fault masking G06F11/1484

Abstract

Systems and methods of using different storage tiers based on a backup policy are disclosed. An example of a method includes receiving a backup job from a client for data on a plurality of virtualized storage nodes. The method also includes identifying at least one property of the backup job. The method also includes accessing the backup policy for the backup job. The method also includes selecting between storing incoming data for the backup job on the plurality of virtualized storage nodes in a first tier or a second tier based on the backup policy.

Claims

1. A method of using different storage tiers based on a backup policy, comprising:

receiving a backup job from a client for data on a plurality of virtualized storage nodes;

identifying at least one property of the backup job;

accessing the backup policy for the backup job; and

selecting between storing incoming data for the backup job on the plurality of virtualized storage nodes in a first tier or a second tier based on the backup policy.

2. The method of claim 1, further comprising storing the backup job in a first state in the first tier based on the backup policy.

3. The method of claim 1, further comprising storing the backup job in a second state in the second tier based on the backup policy.

4. The method of claim 1, further comprising storing at least one backup job in a first state and at least one backup job in a second state without conversion between a first state and a second state.

5. The method of claim 1, wherein the first tier uses non-deduplication and the second tier uses in-line deduplication.

6. The method of claim 1, further comprising providing faster restore of the backup job on the first tier than on the second tier.

7. The method of claim 1, further comprising providing greater storage capacity on the second tier than on the first tier.

8. The method of claim 1, further comprising triggering use of the backup policy only when the backup job includes at least one property other than null.

9. A backup system comprising:

an interface between a plurality of virtualized storage nodes and a client, the interface configured to identify at least one property of a backup job from the client for backing up data on a virtualized storage node in one of at least two states; and

a storage manager operatively associated with the interface, the storage manager configured to manage storing of incoming data for the backup job on the plurality of virtualized storage nodes in either a first tier or a second tier based on a backup policy.

10. The system of claim 9, wherein the at least two states are deduplication format and non-deduplication format.

11. The system of claim 9, wherein the first tier is for fast restore and the second tier is for slow restore.

12. The system of claim 9, wherein the backup policy is user-defined, and the backup policy specifies the state for storing the backup job.

13. The system of claim 9, wherein the at least one property of the backup job is encoded in metadata associated with the backup job, the metadata defining at least two of:

a name of a client device;

a name of the backup job;

a type of the backup job;

an origin of the backup job; and

a capability of a source of the backup job.

14. The system of claim 13, wherein the type of backup job is one of full and incremental.

15. The system of claim 13, wherein the origin of the backup job is one of high priority servers and low priority servers.

16. The system of claim 13, wherein the capability of the source of the backup job is one of deduplication-enabled servers and deduplication-non-enabled servers.

17. A backup system comprising program code stored on computer readable storage and executable by a processor to:

identify at least one property of a backup job from a client for data on at least one virtualized storage node;

access a backup policy; and

select between storing incoming data for the backup job on the at least one virtualized storage node in a first tier or a second tier based on the backup policy.

18. The system of claim 17, wherein the processor further tests a plurality of conditions to identify which tier to store incoming data for the backup job.

19. The system of claim 18, wherein the plurality of conditions include nested conditions.

20. The system of claim 17, wherein the first tier provides faster restore to the client of the backup job than the second tier, and the second tier provides greater storage capacity than the first tier.