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. 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.

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.

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.

Abstract: An extensible method and system for obtaining an historical record of data backup activity (and errors) from a plurality of data backup software devices, and converting the same into a canonical format, is disclosed. In the first aspect, a method comprises the steps of providing a late-binding mechanism that provides the invention with extensibility so that it can be made to inter-operate with an arbitrary variety of backup software devices. In the second aspect, an interface for requesting and returning a canonical backup activity log is disclosed. In the third aspect, an interface for requesting and returning a canonical backup error log is disclosed. In the fourth aspect, the use of a canonical format enables the data to be cross-referenced, consolidated and compared.

Abstract: An extensible method and system for obtaining an historical record of data backup activity (and errors) from a plurality of data backup software devices, and converting the same into a canonical format, is disclosed. In the first aspect, a method comprises the steps of providing a late-binding mechanism that provides the invention with extensibility so that it can be made to inter-operate with an arbitrary variety of backup software devices. In the second aspect, an interface for requesting and returning a canonical backup activity log is disclosed. In the third aspect, an interface for requesting and returning a canonical backup error log is disclosed. In the fourth aspect, the use of a canonical format enables the data to be cross-referenced, consolidated and compared.

Abstract: An extensible method and system for obtaining an historical record of data backup activity (and errors) from a plurality of data backup software devices, and converting the same into a canonical format, is disclosed. In the first aspect, a method comprises the steps of providing a late-binding mechanism that provides the invention with extensibility so that it can be made to inter-operate with an arbitrary variety of backup software devices. In the second aspect, an interface for requesting and returning a canonical backup activity log is disclosed. In the third aspect, an interface for requesting and returning a canonical backup error log is disclosed. In the fourth aspect, the use of a canonical format enables the data to be cross-referenced, consolidated and compared.

Abstract: A method and system for examining historical records of backup activity consolidated from a plurality of backup engines, utilizing a data processing system, is disclosed. In the first aspect, a method comprises the steps of reorganizing historical records of backup activity originating from a plurality of backup engines into unique visual representations to facilitate the speedy and reliable identification of backup activity failures. The method also includes sending prepared requests from BRG to RDB, and then receiving data from RDB. In another aspect, it is disclosed a method of representing a uniquely high number of levels of data extraction relating to backup successes and failures. In another aspect, it is disclosed a method of representing variations other than simply Failure or Success of backup activities, namely Partial failures.

Abstract: An extensible method and system for obtaining an historical record of data backup activity (and errors) from a plurality of data backup software devices, and converting the same into a canonical format, is disclosed. In the first aspect, a method comprises the steps of providing a late-binding mechanism that provides the invention with extensibility so that it can be made to inter-operate with an arbitrary variety of backup software devices. In the second aspect, an interface for requesting and returning a canonical backup activity log is disclosed. In the third aspect, an interface for requesting and returning a canonical backup error log is disclosed. In the fourth aspect, the use of a canonical format enables the data to be cross-referenced, consolidated and compared.

Abstract: An extensible method and system for obtaining an historical record of data backup activity (and errors) from a plurality of data backup software devices, and converting the same into a canonical format, is disclosed. In the first aspect, a method comprises the steps of providing a late-binding mechanism that provides the invention with extensibility so that it can be made to inter-operate with an arbitrary variety of backup software devices. In the second aspect, an interface for requesting and returning a canonical backup activity log is disclosed. In the third aspect, an interface for requesting and returning a canonical backup error log is disclosed. In the fourth aspect, the use of a canonical format enables the data to be cross-referenced, consolidated and compared.

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.