Method for extracting and storing records of data backup activity from a plurality of backup devices

• US 6,640,217 B1
• Filed: 09/19/2000
• Issued: 10/28/2003
• Est. Priority Date: 09/19/2000
• Status: Expired due to Term

• Current Assignee: Bocada LLC
• Original Assignee: Bocada Incorporated
• Inventors: Bear, Cory, Scanlan, Liam
• Primary Examiner(s): Corrielus, Jean M.
• Application Number:
  US09/665,267
• Time in Patent Office: 1,134 Days
• Field of Search: 707/200, 707/201, 707/204, 707/702, 707/3, 707/4, 707/10, 709/217, 709/226, 714/26
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A method and system for requesting, cross-referencing, extracting and storing historical records of data backup activity by using a software component that interfaces to a plurality of data backup software devices is disclosed. In the first aspect, a method of storing automated request-for-historical records of data backup activity schedules is disclosed. In the second aspect, a method for invoking requests through a component that interfaces to a plurality of data backup software devices is disclosed. In the third aspect, a method for receiving historical records of data backup activity from said component is disclosed. In a fourth aspect, a method for making alterations to said historical records of data backup activity is disclosed. In a fifth aspect, a method for inserting said historical records of data backup activity into a data table located in an open, relational database is disclosed. In a sixth aspect, a method for inserting subsets of said historical records of data backup activity into tables related to said central data table is disclosed. In a seventh aspect, a method for removing completed historical records of data backup activity refresh requests is disclosed. Through the use of a system and method in accordance with the present invention, the aforementioned database can be made self-refreshing, requiring minimal ongoing intervention subsequent to initial configuration. In addition, the aforementioned data refreshes can be manually invoked at any time.

Claims

1. A method for backing up data, the method comprising:

providing a computer network with data backup activity performed by a plurality of data backup products each with its own clients and servers,

providing a host computer interfaced to said network,

providing said host computer is running a software device or program that includes said method as one of its software components,

providing for each data backup product a backup engine plug-in that will obtain records of data backup activity from that data backup product,

providing records of data backup activity expressed as a canonical backup log containing backup job records including;

i. a date and time that a data backup attempt or operation took place,

ii. a proprietary name of the data backup client,

iii. a fully qualified host name of the data backup client,

iv. a number of bytes that were backed up or default value,

v. a number of files or objects that were backed up or a default value,

vi. a proprietary data backup level name or a default value,

vii. a canonical data backup level name or a default value,

viii. a description of where the information in the data backup job record was obtained,

ix. a number of seconds that elapsed during the data backup operation or a default value,

X. a number of errors or a default value,

xi. a data and time the data backup will expire or default value,

xii. a logical target name, and

xiii. a media label of a storage media the data backup was written to, and

providing a request for the said canonical backup activity log from a software device or program, whereby said canonical backup activity log becomes a part of said software device or program in response to the asynchronous requests made by said software device or program,

providing a database,

construction of a uniformly formatted record for insertion into one or more data tables containing records of data backup activity,

execution of a process to add said record to one or more data tables containing records of data backup activity,

construction of a uniformly formatted record for insertion into one or more data tables containing backup client records,

execution of a process to add said record to one or more data tables containing backup client records,

construction of a uniformly formatted record for insertion into one or more data tables containing backup target records,

execution of a process to add said record to one or more data tables containing backup target records,

construction of a uniformly formatted record for insertion into one or more data tables containing data backup device name records,

execution of a process to add said record to one or more data tables containing data backup device name records,

construction of a uniformly formatted record for insertion into one or more data tables containing backup level records,

executing a process to said record to one or more data tables containing backup level records,

executing scheduled requests for new records of data backup activity, and

executing operator initiated requests for new records of data backup activity, whereby a general purpose database is made available for cross referencing and analysis of backup activity using third party tools.

2. The method of claim 1, further comprising:

providing a data table of request record data,

providing said request table containing a record of the name of a backup data software program, providing said table containing a record the name of backup server on which the said backup program is running,

providing said table containing a record data relating to the specific data backup software program, and

providing said table containing data that are needed to communicate a request for records of data backup activity from said server such as;

i. passwords, and

ii. user name, whereby the invention will invoke the transmission of requests for data relating to new data backup activities.

3. An automatic refresh request generation system for a data backup system, comprising:

a computer network with data backup activity performed by a plurality of data backup products wherein each data backup product generates records relating to the data backup activity; and

a host computer connected to the computer network that executes a canonical backup device, the canonical backup device further comprising;

a backup engine plug-in that obtains records of data backup activity from each data backup product and consolidate the records in a database; and

a refresh request unit that operates in the background of the host computer, the refresh request unit further comprising;

a timer that determines if an hour of the current day has changed since a previous refresh request,

means for checking a string of values to determine if a refresh request is to be created, and

means for creating the refresh request for a particular server-backup product combination.

4. The system of claim 3, wherein the refresh request unit further comprises means for deleting completed refresh requests.

5. The system of claim 4, wherein the deletion means further comprises means for scanning a status field in a request table of a database for a completed value and means for deleting the record having the completed value.

6. The system of claim 3, wherein the refresh request unit further comprises a database table having an indicator to indicate when a refresh request is to be initiated.

7. The system of claim 6, wherein the string of values comprises a string of bits wherein each bit corresponds to a particular hour in a day and wherein the refresh request unit further comprises means for checking a bit corresponding to a particular hour of a day when the particular hour of the day occurs.

8. The system of claim 3, wherein the means for creating a refresh request further comprises means for writing data into a database table in order to initiate a refresh operation.

9. The system of claim 8, wherein the writing means further comprises means for changing a status field in a request database table to waiting in order to initiate a refresh request.

10. An automatic refresh request generation device for a data backup system having a plurality of data backup products, each data backup product connected to a computer network and each data backup product generating records relating to the data backup activity for the data backup product, the device comprising:

a backup engine plug-in that will obtain records of data backup activity from the plurality of data backup products and consolidate the records in a database that allows cross-referencing between the records from the plurality of data backup products; and

a refresh request unit that operates in the background of the device, the refresh request unit further comprising a timer that determines if an hour of the current day has changed, means for checking a string of values to determine if a refresh request is to be automatically initiated and means for initiating a refresh request for a particular server-backup product combination.

11. The device of claim 10, wherein the refresh request unit further comprises means for deleting completed refresh requests.

12. The device of claim 11, wherein the deletion means further comprises means for scanning a status field in a request table of a database for a completed value and means for deleting the record having the completed value.

13. The device of claim 10, wherein the refresh request unit further comprises a database table having an indicator to indicate when a refresh request is to be initiated.

14. The device of claim 13, wherein the indicator comprises a string of bits wherein each bit corresponds to a particular hour in a day and wherein the automatic request determiner further comprises means for checking a bit corresponding to a particular hour of a day when the particular hour of the day occurs.

15. The device of claim 10, wherein the initiating means further comprises means for writing data into a database table in order to initiate a refresh operation.

16. The device of claim 15, wherein the writing means further comprises means for changing a status field in a request database table to waiting in order to initiate a refresh request.

17. An automatic refresh request generation method for a data backup system having a plurality of data backup products, each data backup product connected to a computer network and each data backup product generating records relating to the data backup activity for the data backup product, the method comprising:

obtaining records of data backup activity from each data backup product;

consolidating the records in a database that allows cross-referencing between records from the plurality of data backup products; and

automatically requesting the refresh of a particular data backup product, comprising determining if an hour of the current day has changed, checking a string of values to determine if a refresh request for the particular server is automatically initiated and initiating a refresh for a particular server-backup product combination if the refresh request has been initiated by inserting a record into the database.

18. The method of claim 17, wherein requesting the refresh further comprises deleting completed refresh requests.

19. The method of claim 18, wherein the deletion further comprises scanning a status field in a request table of a database for a completed value and deleting the record having the completed value.

20. The method of claim 17, wherein the automatic request determining further comprises a database table having an indicator to indicate when a refresh request is to be initiated.

21. The method of claim 20, wherein the indicator comprises a string of bits wherein each bit corresponds to a particular hour in a day and wherein the automatic request determiner further comprises checking a bit corresponding to a particular hour of a day when the particular hour of the day occurs.

22. The method of claim 17, wherein the initiating further comprises writing data into a database table in order to initiate a refresh operation.

23. The method of claim 22, wherein the writing further comprises changing a status field in a request database table to waiting in order to initiate a refresh request.

24. A system for inserting records from one or more data backup products into a canonical database, comprising:

a computer network with data backup activity performed by a plurality of data backup products wherein each data backup product generates records relating to the data backup activity;

a host computer connected to the computer network that executes a canonical backup device; and

the canonical backup device further comprising;

a backup engine plug-in that obtains records of data backup activity from each data backup product; and

a database insertion unit that inserts the data from each record of a data backup product into a canonical database that allows cross-referencing between records from the plurality of data backup products, the database insertion unit further comprising means for inserting data from the record into a data backup portion, means for inserting data from the record into a backup client portion, means for inserting data from the record into a backup target portion, means for inserting data from the record into a backup device name portion and means for inserting data from the record into a backup level portion.

25. The system of claim 24, wherein inserting means further comprises means for inserting the data from the record into one or more data tables containing data backup records, means for inserting data from the record into one or more data tables containing backup client records, means for inserting data from the record into one or more data tables containing backup target records, means for inserting data from the record into one or more data tables containing backup device name records and means for inserting data from the record into one or more data tables containing backup level records.

26. The system of claim 24, wherein the database insertion unit further comprises means for constructing a uniformly formatted record for insertion into one or more data tables.

27. The system of claim 24, wherein the canonical backup device further comprising a refresh request unit that operates in the background of the host computer, the refresh request unit further comprising a timer that determines if an hour of the current day has changed since a previous refresh request, means for checking a string of values to determine if a refresh request for the particular server is automatically initiated and means for initiating a refresh request if the refresh request has been initiated.

28. The system of claim 27, wherein the refresh request unit further comprises means for deleting completed refresh requests.

29. The system of claim 28, wherein the deletion means further comprises means for scanning a status field in a request table of a database for a completed value and means for deleting the record having the completed value.

30. The system of claim 27, wherein the automatic request determiner further comprises a database table having an indicator to indicate when a refresh request is to be initiated.

31. The system of claim 30, wherein the indicator comprises a string of bits wherein each bit corresponds to a particular hour in a day and wherein the automatic request determiner further comprises means for checking a bit corresponding to a particular hour of a day when the particular hour of the day occurs.

32. The system of claim 27, wherein the initiating means further comprises means for writing data into a database table in order to initiate a refresh operation.

33. The system of claim 32, wherein the writing means further comprises means for changing a status field in a request database table to waiting in order to initiate a refresh request.

34. A device for inserting records from one or more data backup products into a canonical database, each data backup product connected to a computer network and each data backup product generating records relating to the data backup activity for the data backup product, the device comprising:

a backup engine plug-in that will obtain records of data backup activity from each data backup product; and

a database insertion unit that inserts the data from each record of a data backup product into a canonical database that allows cross-referencing between records from different data backup products, the database insertion unit further comprising means for inserting data from the record into a data backup portion, means for inserting data from the record into a backup client portion, means for inserting data from the record into a backup target portion, means for inserting data from the record into a backup device name portion and means for inserting data from the record into a backup level portion.

35. The device of claim 34, wherein inserting means further comprises means for inserting the data from the record into one or more data tables containing data backup records, means for inserting data from the record into one or more data tables containing backup client records, means for inserting data from the record into one or more data tables containing backup target records, means for inserting data from the record into one or more data tables containing backup device name records and means for inserting data from the record into one or more data tables containing backup level records.

36. The device of claim 34, wherein the database insertion unit further comprises means for constructing a uniformly formatted record for insertion into one or more data tables.

37. The device of claim 34, wherein the canonical backup device further comprising a refresh request unit that operates in the background of the host computer, the refresh request unit further comprising a timer that determines if an hour of the current day has changed since a previous refresh request, means for checking a string of values to determine if a refresh request for the particular server is automatically initiated and means for initiating a refresh request if the refresh request has been initiated.

38. The device of claim 37, wherein the refresh request unit further comprises means for deleting completed refresh requests.

39. The device of claim 38, wherein the deletion means further comprises means for scanning a status field in a request table of a database for a completed value and means for deleting the record having the completed value.

40. The device of claim 37, wherein the initiating means further comprises means for writing database table in order to initiate a refresh operation.

41. The device of claim 40, wherein the writing means further comprises means for changing a status field in a request database table to waiting in order to initiate a refresh request.

42. The device of claim 37, wherein the refresh request unit further comprises a database table having an indicator to indicate when a refresh request is to be initiated.

43. The device of claim 42, wherein the indicator comprises a string of bits wherein each bit corresponds to a particular hour in a day and wherein the automatic request determiner further comprises means for checking a bit corresponding to a particular hour of a day when the particular hour of the day occurs.

44. A method for inserting records from one or more data backup products into a canonical database, each data backup product connected to a computer network and each data backup product generating records relating to the data backup activity for the data backup product, the method comprising:

obtaining records of data backup activity from each data backup product; and

inserting the records into a canonical database that allows cross-referencing between records from different data backup products, the data insertion further comprising inserting data from the record into a data backup portion, inserting data from the record into a backup client portion, inserting data from the record into a backup target portion, inserting data from the record into a backup device name portion and inserting data from the record into a backup level portion.

45. The method of claim 44, wherein inserting further comprises inserting the data from the record into one or more data tables containing data backup records, inserting data from the record into one or more data tables containing backup client records, inserting data from the record into one or more data tables containing backup target records, inserting data from the record into one or more data tables containing backup device name records and inserting data from the record into one or more data tables containing backup level records.

46. The method of claim 44, wherein the database insertion further comprises constructing a uniformly formatted record for insertion into one or more data tables.

47. The method of claim 44, wherein the canonical backup device further comprising a refresh request unit that operates in the background of the host computer, the refresh request unit further comprising a timer that determines if the hour of the current day has changed, means for checking an automatic request determiner to determine if a refresh request for the particular server is automatically initiated and means for initiating a refresh request if the refresh request has been initiated.

48. A system for inserting records from a plurality of data backup products having different formats into a canonical database, the system comprising:

a computer network with data backup activity performed by a plurality of data backup products wherein each data backup product generates records relating to the data backup activity;

a host computer connected to the computer network that executes a canonical backup device; and

the canonical backup device further comprising a backup engine plug-in that will obtain records of data backup activity from each data backup product and a database insertion unit that inserts the data from each record of a data backup product into a canonical database, the database insertion unit further comprising means for inserting data from the record into a data backup table having a backup time and date field, a server name field, a client name field, a client host name field, a client nickname field, a target name field, a backup product name field, a backup level field, a backup canonical name field, a backup local data and time field, a backup bytes field, a backup file number field, a backup error count field, a days of week field, an hour of the day field and a backup volume field, means for inserting data from the record into a backup client table having a client name field, a server name field, a client host name field, a client nickname field and a client owner field, means for inserting data from the record into a backup target table having a server name field, a client name field, a client host name field, a client nickname field, a target name field, an ignore field and a ignore until field, means for inserting data from the record into a backup device name table having a backup product name field and means for inserting data from the record into a backup level table having a backup product name field, a backup level field and a backup canonical level field.

49. The system of claim 48, wherein each record of each backup product includes one or more of a server name field, a client name field, a client host name field, a logical target field, an engine name field, a level name field, a canonical level field, a backup date field, a byte count field, a file count field, an error count field and a media label field.

50. A device for inserting records from one or more data backup products into a canonical database, each data backup product connected to a computer network and each data backup product generating records relating to the data backup activity for the data backup product, the device comprising:

a backup engine plug-in that will obtain records of data backup activity from each data backup product; and

a database insertion unit that inserts the data from each record of a data backup product into a canonical database, the database insertion unit further comprising means for inserting data from the record into a data backup table having a backup time and date field, a server name field, a client name field, a client host name field, a client nickname field, a target name field, a backup product name field, a backup level field, a backup canonical name field, a backup local data and time field, a backup bytes field, a backup file number field, a backup error count field, a days of week field, an hour of the day field and a backup volume field, means for inserting data from the record into a backup client table having a client name field, a server name field, a client host name field, a client nickname field and a client owner field, means for inserting data from the record into a backup target table having a server name field, a client name field, a client host name field, a client nickname field, a target name field, an ignore field and an ignore until field, means for inserting data from the record into a backup device name table having a backup product name field and means for inserting data from the record into a backup level table having a backup product name field, a backup level field and a backup canonical level field.

51. The device of claim 50, wherein each record of each backup product includes one or more of a server name field, a client name field, a client host name field, a logical target field, an engine name field, a level name field, a canonical level field, a backup date field, a byte count field, a file count field, an error count field and a media label field.

52. A method for inserting records from one or more data backup products into a canonical database, each data backup product connected to a computer network and each data backup product generating records relating to the data backup activity for the data backup product, the method comprising:

obtaining records of data backup activity from each data backup product; and

inserting the data from each record of a data backup product into a canonical database, a database/assertion comprising inserting data from the record into a data backup table having a backup time and date field, a server name field, a client name field, a client host name field, a client nickname field, a target name field, a backup product name field, a backup level field, a backup canonical name field, a backup local data and time field, a backup bytes field, a backup file number field, a backup error count field, a days of week field, an hour of the day field and a backup volume field, inserting data from the record into a backup client table having a client name field, a server name field, a client host name field, a client nickname field and a client owner field, inserting data from the record into a backup target table having a server name field, a client name field, a client host name field, a client nickname field, a target name field, an ignore field and an ignore until field, inserting data from the record into a backup device name table having a backup product name field and inserting data from the record into a backup level table having a backup product name field, a backup level field and a backup canonical level field.

53. The system of claim 52, wherein each record of each backup product includes one or more of a server name field, a client name field, a client host name field, a logical target field, an engine name field, a level name field, a canonical level field, a backup date field, a byte count field, a file count field, an error count field and a media label field.