With this function you can make the following settings to control the data archiving process. The settings you make are applicable to more than one archiving object at a time (cross-archiving-object).
This indicator serves to switch the data archiving monitor (transaction SAR_SHOW_MONITOR) on or off.
If this indicator is set before data archiving, archiving-relevant information about the write and delete jobs is generated and saved. This information can be analyzed using the Data Archiving Monitor. In addition, in case of errors, Alerts (error messages) are triggered.
The Data Archiving Monitor also provides the following information:
· Overview of all archiving objects that were executed
· Detail information about individual archiving sessions
· Progress report on processed archive files
· Help with the analysis of open alerts
The Data Archiving Monitor is part of the CCMS monitor group (transaction RZ20) and is available under SAP CCMS Monitor Templates ® Database ® Data Archiving.
For more information see Data Archiving Monitor.
With the help of this function you can check whether an archive file is available for access in archive administration, when you select archives for reading, deletion, analysis or reloading. The check can be performed separately for stored archive files and archive files that are still in the file system.
· If you select For Files in File System, the access check will cover all files in the file system.
· If you select For Stored Files, the access check will cover all archive files that are in a storage system.
Archive files for which the access check was negative are shown as “not accessible” in the selection screen.
The access check for stored files requires accesses to the storage system. This means that the check can be very time intensive and should only be used after careful consideration.
With this function you can specify that archive files receive additional verification information, which is to be analyzed at a predetermined point in time. The saving of this additional information does not affect the size of the archive file. The verification information is necessary for later analysis during deletion, reading or reloading.
The information is used to verify the state of the archive file before the file is accessed. Corrupt files are recognized and reported, and as a result the data is not deleted from the database.
When archive files are written the system automatically saves verification information. With the Delete, Read, or Reload indicator, you can determine when this verification information is to be analyzed. It is also possible to set more than one indicator.
If supported by the archiving object, you can interrupt the write phase and continue it at a later point in time. The time of interruption can be specified using the following criteria:
· Max. Duration Hours
Here you specify how much time (in hours) has to pass since the write job was started, before the write session of all archiving objects that support interruption, is stopped.
· Max. MB per Session
Here you specify the amount of data (in MB) that has to be reached for the write phase to be interrupted. This affects all archiving objects that support interruption.
Both interruption criteria are independent of each other: The criterion that is first fulfilled automatically triggers the interruption; the other criterion does not have to be fulfilled.
Whether an archiving object supports the interruption function or not is visible in transaction AOBJ, via the Interruption possible indicator.
For more information see Automatic Interruption of an Archiving Session.
Here you can specify on which application server or servers the archiving jobs (write, delete, read, etc.) are to run in the background, independently of the archiving object. If no server group exists yet, it can be created using transaction SM61.
The system distributed the archiving jobs across the application servers of the server group.
Preprocessing, postprocessing and write jobs that were scheduled via Archive Administration (transaction SARA) have the following characteristics:
· These jobs are scheduled with a higher priority (job class A).
· If the specified server group contains an application server that runs on the database server, then the jobs are scheduled there.
The higher prioritization of the write jobs and the fact that the jobs are scheduled on the database server, decreases the network load during data selection and when the archive files are written to a file system that belongs to the database server.
Limitations on the side of the application server can increase the runtime of the entire archiving process, especially if fewer background work processes are active as delete programs.
Choose only those servers for a server group, on which background work processes are active during archiving.
If you have created a server group and entered it in cross-archiving-object Customizing, then other activities such as reloading, reading of archive files, and index build/delete functions, will be performed on that server group.