Method, system, and apparatus for creating an archive routine for protecting data in a data protection system

• US 20060053178A1
• Filed: 09/09/2004
• Published: 03/09/2006
• Est. Priority Date: 09/09/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sen, Vijay, Anand, Karandeep Singh, van Ingen, Catharine, Pai, Sunil, Ali, Abid, Berkowitz, Brian T., Baid, Sushil, Duddi, Suresh P., Badami, Vinay
• Granted Patent: US 7,769,709 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A method for creating an archive protection plan for archiving a backup of data is provided. An indication of an archive data protection kind and an archive data protection duration are received. In response to receiving the archive data protection kind and the archive data protection duration, an archive scheme is determined and an archive protection plan representative of the archive scheme is generated.

Claims

1. A method for creating an archive protection plan for archiving a backup of data, comprising:

receiving an indication of an archive data protection kind;

receiving an indication of an archive data protection duration;

in response to receiving the archive data protection kind and the archive data protection duration, determining an archive scheme; and

generating an archive protection plan representative of the archive scheme.

2. The method of claim 1, further comprising receiving scheduling intentions for the archive protection plan.

3. The method of claim 1, further comprising:

providing the archive scheme;

receiving overrides to the archive scheme;

modifying the archive scheme; and

wherein the generated archive protection plan is representative of the modified archive scheme.

4. The method of claim 1, wherein the archive protection plan includes a resource plan, preparation plan, and a protection plan.

5. The method of claim 1, wherein the identified archive data protection kind is on-site data protection.

6. The method of claim 1, wherein the identified archive data protection kind is off-site data protection.

7. The method of claim 1, wherein the identified archive data protection kind is on-site data protection and off-site data protection.

8. The method of claim 1, wherein the identified archive data protection duration is years.

9. The method of claim 8, wherein the determined archive scheme comprises:

a yearly full backup of the data;

a monthly full backup of the data;

a weekly full backup of the data; and

a daily partial backup of the data.

10. The method of claim 9, wherein the yearly full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time.

11. The method of claim 9, wherein the monthly full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time.

12. The method of claim 9, wherein the weekly full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time.

13. The method of claim 9, wherein the daily partial backup is maintained on-site for a predetermined period of time.

14. The method of claim 9, wherein the yearly full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time;

wherein the monthly full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time;

wherein the weekly full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time; and

wherein the daily partial backup is maintained on-site for a predetermined period of time.

15. The method of claim 9, wherein the yearly backup of data, the monthly backup of data, the weekly backup of data, and the daily backup of data are stored on at least a portion of a same item of media.

16. The method of claim 1, wherein the identified archive data protection duration is months.

17. The method of claim 16, wherein the determined archive scheme comprises:

a monthly backup of the data;

a weekly backup of the data; and

a daily backup of the data.

18. The method of claim 17, wherein the monthly backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time.

19. The method of claim 17, wherein the weekly backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time.

20. The method of claim 17, wherein the daily backup is maintained on-site for a predetermined period of time;

and

wherein the daily backup is a partial backup.

21. The method of claim 17, wherein the monthly backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time;

wherein the weekly backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time; and

wherein the daily backup is maintained on-site for a predetermined period of time.

22. The method of claim 1, wherein the identified archive data protection duration is weeks.

23. The method of claim 22, wherein the determined archive scheme comprises:

a weekly full backup of the data; and

a daily partial backup of the data.

24. The method of claim 23, wherein the weekly full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time.

25. The method of claim 23, wherein the daily partial backup is maintained on-site for a predetermined period.

26. The method of claim 23, wherein the weekly full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time;

and

wherein the daily partial backup is maintained on-site for a predetermined period of time.

27. The method of claim 1, wherein the identified archive data protection duration is days.

28. The method of claim 27, wherein the determined archive scheme comprises:

a daily full backup of the data.

29. The method of claim 28, wherein the daily full backup is maintained on-site for a predetermined period of time and subsequently maintained off-site for a predetermined period of time.

30. The method of claim 1, wherein the archive protection plan includes, generating a full backup and a partial backup.

31. The method of claim 1, wherein the archive protection plan includes, generating a full backup and a partial backup.

32. The method of claim 1, further including receiving an indication of a data protection format.

33. The method of claim 32, wherein the data protection format is incremental.

34. The method of claim 32, wherein the data protection format is differential.

35. The method of claim 32, wherein the data protection format is full.

36. A mechanism for managing a plurality of media for storing data at an archive location in response to receiving a request to store the data, the mechanism comprising:

a Job Collocation intent, wherein for each request associated with a job for storing data, the job collocation intent allocates a same item of media from the plurality of media; and

a Sons Collocation intent, wherein for a first Son job for a predetermined period of time, the Son collocation intent allocates a new item of media from the plurality of media, and for subsequent Son jobs during the predetermined period of time, the Son collocation intent allocates the new item of media from the plurality of media.

37. The mechanism of claim 36, wherein the Job Collocation intent determines whether the request to store data is a replacement request, replacing a failed request to store media;

and

in response to determining that the request is a replacement request, allocating a same item of media that was allocated to the failed request.

38. The mechanism of claim 36, wherein the Job Collocation intent determines whether the request to store data is a first request of a plurality of request;

and

in response to determining that the request is not a first request, allocates a same item of media that was allocated to a prior request.

39. The mechanism of claim 36, wherein the Son Collocation intent determines whether the request to store data is a request to store data of a Son dataset;

and

in response to determining that the request to store data is a request to store data of a Son dataset, allocates a same item of media used by a last Son dataset.

40. The mechanism of claim 36, further comprising:

a Father Son collocation intent, wherein for a Son job, the Father Son collocation intent allocates an item of media containing a father dataset.

41. The mechanism of claim 40, wherein the mechanism is configured to store a plurality of Father datasets, and wherein a first Father dataset of the plurality of Father datasets is stored on at least a portion of a first item of media and a second Father dataset of the plurality of Father datasets is stored on at least a portion of a second item of media.

42. The mechanism of claim 40, wherein the first item of media contains a plurality of Father datasets;

and

wherein the plurality of father datasets are related.

43. The mechanism of claim 36, further comprising:

a dataset recycle intent, configured to recycle available media.

44. The mechanism of claim 43, wherein the dataset recycle intent determines whether media from a same generation as the request to store data is available;

and

in response to determining that media from a same generation is available, allocates an oldest available media from the same generation.

45. The mechanism of claim 43, wherein the dataset recycle intent determines whether media from a portion of the plurality of media is available;

and

in response to determining that media from the portion of the plurality of media is available, allocates the available media.