System and method for archiving data
View Patent ↗Systems, methods, apparatus and software can utilize a markup language to import and export data that is archived using a backup and restore system. An export utility extracts data produced or processed by an application program, converts it into a markup language format, and provides it to a backup and restore system. An import utility extracts data in a markup language format, converts it to another format, and provides the data for use by the application program. In one example, the application program is a database management system.
1. A system comprising:
a backup and restore module configured to:
generate a first data stream to be backed up, and
transmit the first data stream to a backup and restore server, wherein
the backup and restore server is configured to further transmit at least a portion of the first data stream to a storage device; and
a markup language module configured to:
translate data from an application into a markup language version of the data from the application,
translate metadata from the application into a markup language version of
the metadata from the application, wherein
the metadata from the application describes the data from the application, and
the markup language module is configured to perform the translation of the metadata from the application by
determining a type of the markup language being used, and
performing the translation of the metadata based on the type of the markup language, and
pass, to the backup and restore server,
(1) the markup language version of the data from the application, and
(2) the markup language version of the metadata from the application.
2. The system of claim 1 wherein the markup language module further comprises an export utility comprising:
a query processor configured to extract the data from the application.
3. The system of claim 2 wherein the export utility further comprises:
a markup language generator coupled to the query processor and configured to generate the markup language version of the data from the application using data extracted by the query processor.
4. The system of claim 1 wherein the markup language module is further configured to write the markup language version of the data from the application to at least one file.
5. The system of claim 1 wherein the markup language module uses extensible markup language (XML).
6. The system of claim 1 wherein the application is a database management system.
7. The system of claim 6 wherein
the metadata comprises at least one of table names, column names, column data types, and data value constraints.
8. The system of claim 1 wherein the metadata describes an organization of, the data types of, or constraints on the data from the application.
9. The system of claim 1 , wherein
the markup language module is configured to perform the translation of the metadata from the application into the markup language version of the metadata by:
translating the metadata from the application into an intermediate version of the metadata, and
generating the markup language version of the metadata based on the intermediate version of the metadata.
10. The system of claim 9 , wherein
the markup language module comprises a markup language generator, and
the markup language generator is configured to perform the generating of the markup language version of the metadata based on the intermediate version of the metadata.
11. A method comprising:
receiving a request to archive data of an application program;
extracting the data from the application program from at least one data file;
translating, using one or more processors, the data from the application program into a markup language version of the data from the application program;
translating, using the one or more processors, metadata from the application into a markup language version of the metadata from the application, wherein
the metadata from the application describes the data from the application, and
the translating of the metadata from the application comprises
determining a type of the markup language being used, and
performing the translation of the metadata based on the type of the markup language; and
transmitting, to at least one of a backup and restore module and an archive file,
the markup language version of the data from the application program, and
the markup language version of the metadata.
12. The method of 11 further comprising:
transmitting the markup language version of the from the application program from the backup and restore module to a backup and restore server.
13. The method of claim 11 wherein the extracting the data from the application program further comprises:
preparing a query for the application program;
executing the query for the application program; and
receiving the data from the application program based on the query.
14. The method of claim 11 wherein the markup language is extensible markup language (XML).
15. The method of claim 11 wherein the application program is a database management system.
16. The method of claim 15 wherein the metadata comprises at least one of table names, column names, column data types, and data value constraints.
17. The system of claim 11 wherein the metadata describes an organization of, the data types of, or constraints on the data from the application.
18. A memory storing instructions executable by one or more processors, wherein the one or more processors implement a method in response to executing the instructions, the method comprising:
generating a first data stream to be backed up,
transmitting the first data stream to a backup and restore server for further direction to a storage device;
translating data from an application into a markup language version of the data from the application;
translating metadata from the application into a markup language version of the metadata from the application, wherein
the metadata from the application describes the data from the application, and
the translating of the metadata from the application comprises
determining a type of the markup language being used, and
performing the translation of the metadata based on the type of the markup language; and
passing, to the backup and restore module,
(1) the markup language version of the data from the application, and
(2) the markup language version of the metadata.
19. The memory of claim 18 wherein the application is a database management system.
20. The memory of claim 19 wherein the metadata comprises at least one of table names, column names, column data types, and data value constraints.
21. The memory of claim 18 wherein the metadata describes an organization of, the data types of, or constraints on the data from the application.