Use the Archive Process to select a precisely defined set of related rows from a database and save the rows to an external Archive File.
The Archive File is a sequential file that contains the archived data and the table-related definitions needed to re-create objects for restoration. You can browse or selectively restore data in an Archive File at any time.
You must use the Archive Request Editor to define parameters for an Archive Process and store them as an Archive Request. An Archive Request provides information needed to archive and delete data from source tables. The Archive Request references an Access Definition that describes the data to be archived and the data to be deleted. The Access Definition may also include supplemental SQL statements (or Actions) that are executed at selected phases of the Archive or Delete Process. Options in the Archive Request Editor allow you to defer the deletion of data at run time, or review and override deletion instructions specified in the Access Definition. You can also reference a named Storage Profile in the Archive Request to create a duplicate Archive File automatically, to copy an Archive File to a backup device, or to automatically delete the Archive File once the data is no longer active. Compression options allow you to choose a point in the processing cycle to compress the Archive File or to select individual tables to be compressed.
For infrequent or unplanned Archive Processes, you will typically use the Archive Request Editor to define and run the Archive Process from the graphical user interface. However, most organizations can plan their Archive Processes and run them automatically, using the command line interface or the scheduler. These organizations use the Archive Request Editor to define the Archive Request. However, the Archive Process is run in an automated fashion (typically in batch).
Overrides allow you to run the Archive Request from the command line, specifying a different Archive and Index File name or referencing a different Access Definition or criteria for selecting the data to archive.
You can create Archive Files on fixed or secondary media. Fixed media includes local hard drives or network drives. Examples of secondary media includes zip disks, diskettes, and backup devices (for example, tape).
Factors that influence the type of storage to use depend on your business objectives. Specific factors to consider include the cost effectiveness of each type of media, longevity of storage required, mandates for off-site storage, security, and resource management (time and personnel). For example, if quick access to data in Archive Files is of primary importance, you may decide to store Archive Files on a hard disk. However, as Archive Files accumulate, it may be important to move older files for which browsing or restoration is less likely, to cheaper, perhaps less accessible media. In addition to minimizing disk storage, a need for off-site storage or portability may make secondary media a logical choice. Durability of the media could be another consideration — for Archive Files you must retain for an extended period of time, a networked storage system may be the best choice. Conversely, tape storage might be more desirable for short-term storage, due to the large capacity and cost effectiveness of the media. For more information about storing Archive Files, refer to Manage Archive Media.
When an Archive File is created on secondary media, the capacity of the media must be considered. If an Archive File is larger than the space on the target media, the file must be divided into segments to allow the file to span more than one volume. The segment names used for an Archive File are recorded as part of the Archive Directory information for the Archive File. You can specify default segment size values in Personal Options. Refer to the Common Elements Manual for complete information.
In addition to Personal Options defaults, Archive provides Storage Profile Definitions to allow you to override default settings and provide additional secondary media parameters to the Archive Process.
You can use a Storage Profile Definition to automate the creation of a duplicate Archive File, or to copy an Archive File to a backup device. You can also use a Storage Profile to override Personal Options default values for segment size. Use a Storage Profile by specifying the name of the Storage Profile in an Archive Request. During processing, the storage parameters are referenced by the Archive Process.
The parameters you define in a Storage Profile Definition can be saved and reused. Use the Storage Profile Definition Editor to define, name, and save Storage Profile Definitions. Refer to Using the Storage Profile Definition Editor.
If the Archive File is to reside on an Optim™ Server, you can use the Storage Profile to set a retention policy for the file. The retention policy applies to the primary copy of the Archive File, usually saved to fixed media (for example, a local hard drive or network drive). Once the retention period has expired, the Optim Server automatically deletes the Archive File. Refer to Using the Storage Profile Definition Editor.
Archive can archive data from a variety of databases (DB2®, Oracle, Sybase ASE, SQL Server, and Informix®) and restore data to the same or a different type of database.
This section explains how to create, maintain, and process an Archive Request, including how to: