This section provides basic guidelines for configuring a data archiving environment.
The first step in configuring an archiving enviroment is to define the components (computer network) where the archiving actitivies are to take place.
A major flexibility of Data Archiving for Adabas is that it can extract data from Adabas in one computer and place the data in another computer. This flexibility is needed because it is possible that the computer where Adabas is running is unable to store data into the archive (vault), either due to architecture issues or because the disks are not exposed to the (Adabas) computer or similar.
Also, even if the vault is accessible from all computers it is very likely that processing resources in the Adabas computer are very expensive and scarce so it is imperative that as much of the archive processing as possible is offloaded to a different computer, even a different architecture. Data Archiving for Adabas allows you to decide where each part of the process is to execute, and therefore how the costs will be borne within the context of your enterprise computing resources. There are some simple rules in deciding where each part of the process runs:
The extraction from Adabas must run locally to Adabas. This makes sense because usually archiving takes many millions of records from Adabas (read, then delete), so to do this processing across network linkages is not an optimal approach.
The accumulation into Adabas (in cases where the destination is to an Adabas file and not to the vault) must run locally to the (destination) Adabas.
So, for each archived Adabas file you must decide:
The computer where the source Adabas file runs. The extraction (at least) from this file must run in the same computer as Adabas.
The type of destination. Another Adabas file or the (flat file) vault.
The computer where the destination processing is to take place. The destination processing (accumulation) can run in the same computer or in a different computer to where the source Adabas runs.
Considering these things for all the files which you wish to archive gives you a picture of a logical computer network where all your archiving activities will take place. This logical network is defined as a group using the SMH user interface for Adabas System Coordinator.
please refer to the Adabas System Coordinator documentation for more information on how to define groups.
Once you have defined the group(s) you wish to operate you must then define the archiving plans and actions that will fulfill the goals you have for your archiving infrastructure. When you define the archive plan, you specify for which group the plan is to be used as well as which archive vault is to be used for the plan. You then define each action for the plan by specifying the archiving parameters to be used (extractor settings, data transfer settings, accumulator settings).
Vaults, plans and actions are managed by the Data Archiving for Adabas. You therefore use the SMH user interface for Data Archiving for Adabas for defining these components.
For more information on how to define archive plans and vaults, see Defining Archiving Plans and Defining Vaults.
The following provides an overall summary of the steps involved in setting up an archiving enviroment.
| Step | Activity | SMH Interface Location | For more information ... |
|---|---|---|---|
| Steps 1-5 | Define the archiving components using Adabas System Coordinator. | ||
| 1 | Identify all computers where archiving components are to be run. If they have not yet been defined, then define them. | Adabas System Coordinator (Computers) | See Adabas System Coordinator documentation. |
| 2 | For each archiving process, define an archive group if not already defined. | Adabas System Coordinator (Groups) | See Adabas System Coordinator documentation. |
| 3 | For each archive group, define the computers that will participate in this particular group. The computers must be selected from the list of computers defined in step 1. | Adabas System Coordinator (Groups/Computers) | See Adabas System Coordinator documentation. |
| 4 | For each computer defined in step 3, define the group members that are to be run on that computer for a given archive group. | Adabas System Coordinator (Groups/Computers/Members) | See Adabas System Coordinator documentation. |
| 5 | For each member defined in step 4, define the archive service to be performed. | Adabas System Coordinator (Groups/Computers/Members) | See Adabas System Coordinator documentation. |
| Steps 6-8 | Define archive vaults and archive plans using Data Archiving for Adabas. | ||
| 6 | Define the vault or vaults where the archived data is to be stored. For each vault you must define the access path to the vault for each computer that will access the vault. | Data Archiving for Adabas (Vaults) | Defining Vaults |
| 7 | Define an archive plan or plans. | Data Archiving for Adabas (Plans) | Defining Archiving Plans |
| 8 | For each archive plan defined in step 7, define the actions to be used with the plan. When you define an action, you provide the archiving parameters to be used (extractor settings, data transfer settings, accumulator settings). These are the parameters which identify the specific location of the data to be extracted for archiving, when archiving is to be performed, and the specific location where the data is to be stored. | Data Archiving for Adabas (Plans/Plan Names/Actions) | Defining Archiving Plans |
