WO2002025498A1 - Procede pour visualiser une activite de sauvegarde de donnees a partir de plusieurs dispositifs de sauvegarde - Google Patents

Procede pour visualiser une activite de sauvegarde de donnees a partir de plusieurs dispositifs de sauvegarde Download PDF

Info

Publication number
WO2002025498A1
WO2002025498A1 PCT/US2001/029434 US0129434W WO0225498A1 WO 2002025498 A1 WO2002025498 A1 WO 2002025498A1 US 0129434 W US0129434 W US 0129434W WO 0225498 A1 WO0225498 A1 WO 0225498A1
Authority
WO
WIPO (PCT)
Prior art keywords
backup
data
server
activity
client
Prior art date
Application number
PCT/US2001/029434
Other languages
English (en)
Inventor
Cory Bear
Liam Scanlan
Original Assignee
Bocada, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US09/665,270 external-priority patent/US6708188B1/en
Priority claimed from US09/665,267 external-priority patent/US6640217B1/en
Priority claimed from US09/665,269 external-priority patent/US6745210B1/en
Application filed by Bocada, Inc. filed Critical Bocada, Inc.
Priority to AU2001292862A priority Critical patent/AU2001292862A1/en
Publication of WO2002025498A1 publication Critical patent/WO2002025498A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database

Definitions

  • the present invention is related generally to electronic/software backup and more particularly to simultaneous and seamless examination of such historical records of backup activity performed across a plurality of backup engines.
  • backup tape drives are usually connected directly to the backup "server”.
  • backup server There is also usually more than one backup server, each of which is responsible for the backup of data of numerous clients.
  • a central function of the activity of backup is the ability to "restore" data in the case of damage to the data that is in use.
  • the backup server computer too usually controls this restore process. Understandably, the time it takes to recover data, and the confidence that the data recovery process will succeed, are two critical aspects of the backup and restore function as a whole.
  • Disk drive capacities and data volumes, and consequently the volumes of data to be backed up have historically been increasing at a greater rate than the backup server speed, tape drive capacity and network bandwidth are increasing to handle it. Accordingly, new technologies have been added to help. Such new technologies include fiber-optic cables (for fast data transfer across the network), faster chips, tape drives that handle more tapes, faster tape drives, "Storage Area Networks" and so on.
  • Legato GEMS ReporterTM which provides trend analysis and text-based failures analysis. This product works with Legato NetWorker. It is built to handle up to approximately 4 or 5 average-sized backup servers.
  • Veritas Advanced ReporterTM 3.2 from Veritas is similar to GEMS
  • SAMS VantageTM provides statistical reports from backup activity of
  • No known prior art combines backup statistics from a plurality of backup engines with monetary values to produce billing reports.
  • No known prior art provides billing reports based on backup activity statistics.
  • No known prior art uses an association with owners of data to control the grouping of data within such a billing report.
  • No known prior art allows the association of backup data amount pro rated pricing to control the amounts appearing on such billing reports.
  • the present invention provides a method of visually representing historical records of backup activity across a plurality of backup engines, stored in a relational database, in such a way that key backup performance metrics are made obvious.
  • said records are also organized and represented in such a way as to allow organizations to charge 3 rd parties for backup services rendered to those 3 rd parties.
  • This invention provides:
  • the invention combines backup statistics from a plurality of backup engines with monetary values to produce billing reports.
  • the invention provides billing reports based on backup activity statistics.
  • the invention uses an association with owners of data to control the grouping of data within such a billing report.
  • the invention allows the association of backup data amount pro rated pricing to control the amounts appearing on such billing reports.
  • a system and method in accordance with the present invention has significant utility over conventional backup activity examination.
  • Figure 1 A flowchart illustrating how the Backup Failures Analysis Report is created
  • Figure 2 illustrations of the visual objects that are used in the creation of the Backup Failures Analysis Report
  • Figure 3 a flowchart outlining the logic used and actions taken during the production of the optional three extra levels of detail in the Backup Failures Analysis Report
  • Figure 4 an illustration of the visual object that is created for the purposes of providing a further 3 levels of backup detail to the user of the invention
  • Figure 5 an illustration of three database tables relevant to the Billing Report method
  • Figure 6 an illustration of the Billing Report container, showing the critical elements used to invoke the production of a Billing Report and showing the Billing Report container;
  • Figure 7 an illustration of how a billing report looks when executed using the embodiment described in this document.
  • Figure 8 a view of the 3 -dimensional 7day x 24hr load analysis report as it appears after visual representation.
  • backup engine means any software program, or part of a program, designed to backup electronic data onto a data storage medium such as magnetic tape.
  • Veritas Backup ExecTM and IBM TivoliTM Storage Manager are two well-known examples.
  • SQL Server Microsoft SQL Server
  • One or more databases can be stored in and managed by an installation of SQL Server.
  • This embodiment uses one database, named "backupreport”.
  • the tables directly or indirectly pertaining to this embodiment are detailed in figure 5.
  • SQL Server is the preferred embodiment.
  • BRG an acronym used in this document for "Backup Report Graphical User Interface” is used to represent the embodiment disclosed in this patent application.
  • RDB an acronym for Relational Database
  • the RDB contains historical records relating to backup activity across a plurality of backup engines.
  • the RDB resides in an implementation of Microsoft SQL ServerTM (described above).
  • Backup means the actual transfer of data that is in regular use, usually across a network, to a data storage medium, such as a magnetic tape, for the purposes of retrieval at a later date, should the data in regular use become damaged.
  • Backup Engine means any software product or program that is used for the purposes of Backup described in the previous paragraph. For example, Legato NetWorkerTM, Veritas BackupExecTM, BakBone NetVaultTM.
  • interface it is meant the ability to request and receive historical records of backup activity from those backup engines.
  • the preferred embodiment uses an industry-standard "grid-style" component known as XGridTM as a container for the Backup Failures report, but any one of several different grid-style components could have been used instead. It is indeed also possible to use a non-grid container that allows objects such as red and green squares to be created inside the container to implement the same essential method.
  • the preferred embodiment uses a product called ReportBuilderTM Pro for Billing Reports. Alternative embodiments are possible. There are numerous software products like ReportBuilder on the market, any one of which could have been used to produce the same result using a different embodiment.
  • BRG relates to the unique means of providing backup failure identification, billing report and trend analysis production, across data originating from a plurality of backup engines and residing in a multi-purpose relational database (RDB).
  • RDB relational database
  • Field BT7 shows that table BT includes a plurality of backup engines that have performed backup activity.
  • the invention user is presented with an empty Failures Report container F2 (on figure 2).
  • the “container” F2 (on figure 2) for the report, highlighted using a rectangular box, is presented to the user in the form of a "window".
  • this container are: (1) several listboxes that the user can pick and choose from to narrow down the amount of data that will be included in the report, (2) an empty area on the right where the report will ultimately be displayed, and (3) a Run Report button that the user can click after they have made the selections in the listboxes in F2.B and F2.C (in figure 2) they wanted.
  • the selections are programmatically extracted from F2.B and F2.C (in Figure 2).
  • the program has received a request to run/refresh the report.
  • the program begins to prepare a SQL Statement.
  • the SQL statement is very broad, that is, if it were used as is, the report would include potentially all of the data from the database. It is expected, especially where data volumes are very large, the user would make selections to narrow down the data before running the report, thereby producing a smaller, more manageably sized report.
  • V.ignoreuntil ⁇ 36761.5600594097 ORDER BY V. servername, V. clientname, V. targetname, S.backupdatetime
  • the SQL statement is so structured so that it will take ALL references to "targets" (pieces of data that, at some time in the past, have been backed up at least once), regardless of whether or not backup records exist within the data range specified by the days the report is supposed to cover.
  • LEFT OUTER JOIN is a method that would be immediately understood by anyone familiar in the art. LEFT OUTER JOIN is used anywhere the desired result is to get ALL records from one table, joined with whatever records may be available, if any, from a second table.
  • LEFT OUTER JOIN "forces" targets to appear in the report even if there are no recent backup records in the database for them.
  • Such use of OUTER JOIN is used in accordance with principles well known in the art.
  • Extra text will be added to the SQL statement toward the end of the base statement.
  • This extra text is a "filter” that gives the SQL Server several criteria upon which it should include records. This is best illustrated with an example. Ifthe selections shown in figure F2.D (in figure 2) were made, the SQL statement would look like this:
  • V. servername S . servername
  • the report contents are also sorted.
  • SQL request is sent to Server (see F7 in Figure 1)
  • the program then transmits to the SQL Server the prepared SQL statement.
  • this transmission is done using a means called
  • DBLIB which is supplied with every SQL Server installation.
  • DBLIB is a means of connecting a software program with a SQL Server.
  • SQL Server When SQL Server has executed the SQL Statement, it then returns records to the program in the form of a batch of records of the same form. Depending on what historical records exists in the database, and what selections the user has made, any number of records may be in this batch, from none at all, to millions.
  • the program takes each subsequent record until either (1) all records are processed or (2) it reaches capacity for the report container, and piece-by-piece begins to assemble the report.
  • the first or next record is read (see F10 in Figure 1)
  • each record in the batch is read. Because the returned historical records are ordered by server, it is obvious when all the records for a given target are complete because, if comparing the target name field from record to record produces a change, we know that we must begin a new section in the report for that new target.
  • the program examines the row of colored squares the program belonging to the last target just read, and changes the colors of the client row and the server row above it accordingly. This is how it decides what squares to change to what color for a given day.
  • a target has a red square and if the backup client it belongs to has a green square, and if it is the first target for that client, it changes the client's square to red.
  • a target has a red square and the client it belongs to has a green square, and it is NOT the first target row for that client, it will change the color of the client square to mixed red and green (see example: F2.H in figure 2).
  • the target has a green square, and the client that target belongs to is green, it does not change any color. 5. If the target has a green square and the client has a red square, and it is the first target row for that client, it will change the color of the client's square to green.
  • the target has a green square and the server row to which the target belongs has a red square, and it is the first target row for the server, then it will change the server square to green.
  • the target has a green square and the server row to which it belongs has a red square and it is NOT the first target for that server, then it will change the server square to mixed red/green.
  • the target has a mixed red/green square it will change the client square to mixed red/green, and also change the server row to which that client belongs to mixed red/green.
  • a new row (example of a server row: F2.N in figure 2) is added for that new server, and a new client row (example of a client row: F2.P in figure 2) is added for that new client. For each such row added, all the squares to the right are set to red.
  • a new row is added, for the newly encountered target, to the bottom of the report.
  • the target name is inserted as text into the left-most cell. AU of the squares to the right of that target name are then colored red.
  • the date of the record is then examined.
  • the program processes more and more records, and the report gets longer and longer and more and more clients, targets and servers get added to the report, the total number of rows is increased as needed. Every time a new row needs to be added to the report, the program first checks to see if there is enough free (empty) rows available for one more row to be added. If not, then 100 extra rows are added at a time. This is for optimization; as will be understood by any person familiar in the art, it is faster to add 100 rows once, than add 1 row 100 times. This is just an optimization used in this embodiment. The same result can be achieved by simply adding each row as required. When the report is complete, then any unused (empty) rows in the report are removed.
  • the report F2.L (on figure 2) is created with four levels of detail.
  • the highest level is Backup Server (level 1); within each server are multiple backup clients (level 2); within each backup client are multiple backup targets (level 3); within each of these first three levels is a row of colored squares, one square for each day (level 4).
  • the grid F2.L contains a column that is not shown. It is referred to as column -1 (minus one). In that column, details about what the row of the report contains are placed: the backup product name, the server name, and the backup client name are placed as one single piece of string, with a semi-colon between each field, in each cell of column - 1.
  • the report when the report is created, it is created with "half of the data". In other words, not every last detail about each backup activity is stuffed into the report. There is a lot more data, both in the BackupReprot2000 database and in the backup servers themselves. So, instead of creating the report to show all available data, the report is created with high and medium level data.
  • G3 (figure 3) A request is sent to BX asking for any messages that may be stored on the backup server itself relating to backup events on the specified day, backup server and client.
  • G6 (figure 3) The program does not wait (i.e. doing nothing) for BX to respond.
  • the reason it does not wait is that the time it is expected to take for the backup server to respond with an answer to the request may be several seconds, perhaps minutes (in extreme situations), so for optimization, the program continues with its other tasks and handles the response later.
  • B.targetname 'C: ⁇ program ⁇ nsr ⁇ index ⁇ apollo ' GROUP BY servername, clientfqhostname, targetname, backupproductname
  • SQL statement and this request is for detailed, record-by-record data about the backup activity for that server, client and target for that day.
  • the SQL statement typically will look like this:
  • the SQL Server will respond by sending all the records without doing any summarization of the records.
  • the data is placed in F4.C(see figure 4) if it is still visible.
  • the Backup Billing Reports are created by combining the contents of three (3) data tables, table BT (see figure 5), table CT (see figure 5), and table TI (see figure 5) in the database, sometimes summarizing the results, and placing them in a particular order in a "report container".
  • table BT see figure 5
  • table CT see figure 5
  • table TI see figure 5
  • the following sections describe how that is done, and what specific pieces of data and software are used in the process.
  • the charges that appear on the billing report are calculated by multiplying the number of megabytes by the charge per megabyte stored in field T1.2 (see figure 5). Added to that is a charge per megabyte, taken from field T1.3 (see figure 5). So, even if a backup fails, which means a record with a zero value in the field BTll (see figure 5), is found in the table BT (see figure 5), there will be a charge amount in the billing report for that backup.
  • the billing reports ignore the values contained in these fields, because the billing process is designed to produce backup activity billing reports regardless of what type of backup software performed the actual backup. Indeed, it is a central purpose, and a defining uniqueness, of this invention, to seamlessly mix data from any number of backup software products that are in use by the person(s) using the invention.
  • the user of the program initiates a report request.
  • the SQL statement is then "sent" to the SQL Server to be applied to the database, and the program waits for a response.
  • the data is returned to the program
  • the SQL Server When the SQL Server responds, it is in the form of a batch of records.
  • the Billing Report container 6.6 (see figure 6) is a software component called ReportBuilderTM Pro that was selected because of its specialized report-building capabilities.
  • ReportBuilder allows the programmer to quickly configure within the report container an interface to the data, specifying the form of data it should use, and also specifying how the data should appear when the data is placed in the report container.
  • the creation of the 7x24 analysis report 8.6 is similar to how creation of the previous report in this document (Backup Billing Report) is described.
  • the container for the 7x24 analysis report 8.6 (see figure 8) is a commonly used charting tool that can be embedded in a programming environment. Although the one chosen for this particular embodiment was TeeMach ChartProTM, anyone familiar in the art might pick any one of dozens of other charting components available in the marketplace and reproduce this method.
  • the at-first empty report container is prepared by the creation of an object with 3 dimensions, the first two of which are critical to this patent. These dimensions are 8.7 (see figure 8) and 8.8 (see figure 8), the 24 hours of the day along the X-axis, and the days of the week along the Z-axis.
  • the value of the field SOTB in the SQL statement above is added to the relevant column.
  • a single set of examination tools that can operate with data from a plurality of backup engines offers the invention user an order of magnitude improvement in productivity and reliability over the hitherto requirement of using a multitude of engines each of which operates only with a single backup engine.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Cette invention se rapporte à un procédé et à un système servant à examiner les enregistrements d'une activité de sauvegarde consolidée par plusieurs moteurs de sauvegarde (BT), utilisant un système de traitement de données. Dans son premier aspect, un tel procédé consiste à réorganiser les enregistrements de l'activité de sauvegarde provenant de plusieurs moteurs de sauvegarde en une représentation visuelle unique, afin de faciliter l'identification rapide et fiable des erreurs de l'activité de sauvegarde. Ce procédé consiste également à envoyer une demande préparée (F7) à partir d'une interface graphique de rapport de sauvegarde (BRG) vers une base de données relationnelle (RDB), puis à recevoir (G1) les données provenant de la base de données relationnelle (RDB). Dans un autre de ses aspects, cette invention concerne un procédé servant à représenter un nombre élevé unique de niveaux d'extraction de données concernant les échecs et les succès d'une activité de sauvegarde.
PCT/US2001/029434 2000-09-19 2001-09-19 Procede pour visualiser une activite de sauvegarde de donnees a partir de plusieurs dispositifs de sauvegarde WO2002025498A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001292862A AU2001292862A1 (en) 2000-09-19 2001-09-19 A method for visualizing data backup activity from a plurality of backup devices

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US09/665,270 US6708188B1 (en) 2000-09-19 2000-09-19 Extensible method for obtaining an historical record of data backup activity (and errors) and converting same into a canonical format
US09/665,269 2000-09-19
US09/665,267 US6640217B1 (en) 2000-09-19 2000-09-19 Method for extracting and storing records of data backup activity from a plurality of backup devices
US09/665,270 2000-09-19
US09/665,269 US6745210B1 (en) 2000-09-19 2000-09-19 Method for visualizing data backup activity from a plurality of backup devices
US09/665,267 2000-09-19

Publications (1)

Publication Number Publication Date
WO2002025498A1 true WO2002025498A1 (fr) 2002-03-28

Family

ID=27418131

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/US2001/029434 WO2002025498A1 (fr) 2000-09-19 2001-09-19 Procede pour visualiser une activite de sauvegarde de donnees a partir de plusieurs dispositifs de sauvegarde
PCT/US2001/029435 WO2002025499A1 (fr) 2000-09-19 2001-09-19 Procede pour extraire et stocker des enregistrements d'une activite de sauvegarde de donnees a partir de plusieurs dispositifs de sauvegarde
PCT/US2001/029521 WO2002025462A1 (fr) 2000-09-19 2001-09-19 Procede pour obtenir un enregistrement de sauvegarde de donnees et le convertir dans un format canonique

Family Applications After (2)

Application Number Title Priority Date Filing Date
PCT/US2001/029435 WO2002025499A1 (fr) 2000-09-19 2001-09-19 Procede pour extraire et stocker des enregistrements d'une activite de sauvegarde de donnees a partir de plusieurs dispositifs de sauvegarde
PCT/US2001/029521 WO2002025462A1 (fr) 2000-09-19 2001-09-19 Procede pour obtenir un enregistrement de sauvegarde de donnees et le convertir dans un format canonique

Country Status (3)

Country Link
EP (1) EP1330722A4 (fr)
AU (3) AU2001291169A1 (fr)
WO (3) WO2002025498A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1738260B1 (fr) * 2004-01-09 2010-02-10 T.W. Storage, Inc. Procede et dispositif permettant de rechercher des donnees de sauvegarde sur la base d'un contenu et d'attributs
US8239348B1 (en) * 2008-08-14 2012-08-07 Symantec Corporation Method and apparatus for automatically archiving data items from backup storage
CN102841897B (zh) * 2011-06-23 2016-03-02 阿里巴巴集团控股有限公司 一种实现增量数据抽取的方法、装置及系统
CN116048977B (zh) * 2022-12-30 2024-02-06 支付宝(杭州)信息技术有限公司 一种基于数据还原的测试方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5796999A (en) * 1994-04-15 1998-08-18 International Business Machines Corporation Method and system for selectable consistency level maintenance in a resilent database system
US5890165A (en) * 1996-03-29 1999-03-30 Emc Corporation Method and apparatus for automatic discovery of databases

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5574906A (en) * 1994-10-24 1996-11-12 International Business Machines Corporation System and method for reducing storage requirement in backup subsystems utilizing segmented compression and differencing
US5729735A (en) * 1995-02-08 1998-03-17 Meyering; Samuel C. Remote database file synchronizer
US5754782A (en) * 1995-12-04 1998-05-19 International Business Machines Corporation System and method for backing up and restoring groupware documents
US5852715A (en) * 1996-03-19 1998-12-22 Emc Corporation System for currently updating database by one host and reading the database by different host for the purpose of implementing decision support functions
US5857208A (en) * 1996-05-31 1999-01-05 Emc Corporation Method and apparatus for performing point in time backup operation in a computer system
US5758359A (en) * 1996-10-24 1998-05-26 Digital Equipment Corporation Method and apparatus for performing retroactive backups in a computer system
US6112237A (en) * 1996-11-26 2000-08-29 Global Maintech, Inc. Electronic monitoring system and method for externally monitoring processes in a computer system
US6038569A (en) * 1997-02-10 2000-03-14 International Business Machines Corporation System for data structure loading with concurrent image copy
US6026414A (en) * 1998-03-05 2000-02-15 International Business Machines Corporation System including a proxy client to backup files in a distributed computing environment
DE19911759C1 (de) * 1999-03-16 2000-09-07 Ibm Vorrichtung und Verfahren zur Ablaufüberwachung von Vorgängen in einem Digitalrechner

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5796999A (en) * 1994-04-15 1998-08-18 International Business Machines Corporation Method and system for selectable consistency level maintenance in a resilent database system
US5890165A (en) * 1996-03-29 1999-03-30 Emc Corporation Method and apparatus for automatic discovery of databases

Also Published As

Publication number Publication date
AU2001292862A1 (en) 2002-04-02
WO2002025462A1 (fr) 2002-03-28
AU2001292863A1 (en) 2002-04-02
EP1330722A1 (fr) 2003-07-30
WO2002025499A1 (fr) 2002-03-28
EP1330722A4 (fr) 2007-03-28
AU2001291169A1 (en) 2002-04-02

Similar Documents

Publication Publication Date Title
US6745210B1 (en) Method for visualizing data backup activity from a plurality of backup devices
US8407227B2 (en) Method for extracting and storing records of data backup activity from a plurality of backup devices
US7937420B2 (en) Method and system for intelligent storage management
US7107340B2 (en) System and method for collecting and storing event data from distributed transactional applications
US6553371B2 (en) Method and system for specifying and displaying table joins in relational database queries
US6700590B1 (en) System and method for retrieving and presenting data using class-based component and view model
US6651062B2 (en) Method and apparatus for managing data for use by data applications
US20060259349A1 (en) In-queue jobs information monitoring and filtering
US20030061225A1 (en) Hierarchical hybrid OLAP scenario management system
US20030061246A1 (en) Hierarchical hybrid online analytical processing services system
US6915298B1 (en) User-defined relationships for diagramming user-defined database relations
EP2188721B1 (fr) Système et procédé de gestion de stockage
EP1385101A2 (fr) Modèlisation statique de traversées de base de données
CN110442620A (zh) 一种大数据探索和认知方法、装置、设备以及计算机存储介质
McFadden Data warehouse for EIS: some issues and impacts
US7007023B2 (en) Method for flagging differences in resource attributes across multiple database and transaction systems
US7509334B2 (en) Methods, systems and computer program products for segmented presentation of service order status information
US20080221959A1 (en) System and architecture for managing distributed design chains
WO2002025498A1 (fr) Procede pour visualiser une activite de sauvegarde de donnees a partir de plusieurs dispositifs de sauvegarde
US6873989B1 (en) Graphical display of IMS space usage characteristics
US20030061226A1 (en) Data loader for handling imperfect data and supporting multiple servers and data sources
CN116383420A (zh) 运维数据的处理方法、装置和电子设备
US20080250050A1 (en) Method and system for developing a desired set of configuration profiles for an application program and storage medium for storing a set of computer instructions which effectuate the method
CA2435861C (fr) Modelisation de forage transversal statique
CN113836301A (zh) 房产类文章自动生成方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP