Restore Process

The Restore Process obtains data from a source (one or more Archive Files) and copies that data to a destination (one or more tables in a database). There are two steps to a Restore Process. First, one or more Archive Files that contain the data to restore must be located, and the desired data selected. Second, the data is restored to the database using the Insert or Load Process.

To restore archived data, you must create a Restore Request. Using the Restore Request, you can select data from one or more Archive Files and restore it to the original or a different database. Because the object definitions are included in the Archive File, you can also clone the original database if desired. You can process the Restore Request immediately, or use the Restore Request as a template for application‑generated jobs run from the command line, using overrides as appropriate. A Restore Request can also be scheduled, if circumstances warrant.

Restore Request

In the Restore Request, you define the parameters for restoring the data to the database. These parameters include the name or names of source Archive Files, criteria for the data to be restored, the type of process (Load or Insert) used to restore the data, and Insert or Load Requests that can be used to restore the data.

Considerations that apply when deciding the method used to restore archived data include: the volume of data, the number of rows to be restored, the need for user access during a Restore Process, and the need to replace rows and insert rows in one step.

Restore Request Editor

You use the Restore Request Editor to create and edit Restore Requests.

Insert Request or Load Request

Use the Insert Request Editor to define parameters in an Insert Request or use the Load Request Editor to define parameters in a Load Request. Among other parameters, an Insert or a Load Request includes:

  • The name of the Extract or Archive File (this Source File may be the Archive File that is actually restored or, in an automated process, it may serve as a template for an Archive File that is restored).
  • The name of the Control File that tracks the process.
  • The Table Map that identifies and matches source with destination tables and can be used to exclude one or more tables from restoration.

Table Map

A Table Map matches tables in the restored Archive File to tables in the destination database. Individual tables can be excluded and tables with different names can be mapped. You can use an existing Table Map or define the Table Map as part of the Insert or Load Request specifications.

Object Definitions

If destination tables do not exist, Archive can generate SQL to create the tables, using the object definitions in the Archive File. The tables are created as part of the Insert Process or in a separate step. In addition to tables, other object definitions can be created.

Control File

A Control File records information about the success or failure of Insert or Load processing for each selected row in an Archive File. You must specify a Control File when you create an Insert or Load Request.

Restore Process Report

A Restore Process Report is generated as part of the Restore Process. The report contains general information and statistics about each step of the process and provides details about the data that has been restored.