The actual archiving run is scheduled and processed as a background job. It selects the data objects from the database. When doing this, the integrity conditions that characterize a data object are taken into account. The system then checks whether each data object can be archived. If it can be archived, the data object is written to the archive file. If the Customizing settings specify that the delete program is to run automatically, the associated deletion run is automatically started when a file is closed.
The delete run must be separately scheduled, if the delete program is not automatically run by the settings in the archiving object-specific Customizing. When scheduling separately, you must also select the archive files, from which the data objects are to be read in the current delete run, and then deleted from the database.
The delete run must be separately scheduled, if the delete program is not automatically run by the settings in the archiving object-specific Customizing. When scheduling separately, you must also select the archive files, from which the data objects are to be read in the current delete run, and then deleted from the database.
An archiving run is scheduled using transaction SARA by choosing the Write button.
It is divided into four steps:
1. Create an archiving variant
2. Specify the execution user
3. Specify the start time
4. Definine the spool parameters
The data that is to be archived for the selected archiving object is specified in archiving variants. In principle, archiving variants can only be reused if the associated jobs are deleted. The definition of the variant must also specify whether it is a test run or a production run.
The user under which the archiving program is started requires at least an appropriate authorization for the authorization object S_ARCHIVE. S_ARCHIVE is the main authorization object used for data archiving. By selecting the corresponding field entries for this authorization object, you can restrict the archiving objects to be used.
The user also requires the relevant authorizations for the application transaction for which data is to be archived. As data archiving runs in the background, the user also requires authorizations for background processing (authorization object S_BTCH_JOB).
The start times to be specified for archiving jobs are the same as those for standard job scheduling.
Since job logs can become large, it is advisable to set under Spool Parameters that the log is not immediately output on the output device. The selection options are the same as the standard background printing parameters.
Monitoring an Archiving Run There are various system administration tools available to monitor archiving runs:
. Background processing tools
. Joblogs
. Spool lists (if created)
. System monitoring tools
. Data Archiving Monitor in the CCMS monitor sets
A log is created during an archiving run. If the application creates a specific log, this is used; otherwise, the standard log is used. The standard logs contains the number of archived data objects, the affected tables, the number of processed table entries, and the file sizes. The contents of the archiving can be stored to document level in application-specific logs.
You can trace the process of an archiving run with the monitoring of the background work processes using the transaction Simple Job Selection (transaction code SM37).
By choosing Job Overview, you can move directly from the initial screen of transaction SARA to transaction SM37. By choosing Management (after you have maintained an appropriate archiving object on the initial screen of transaction SARA), you can display a short log file of an archiving run from transaction SARA.
Since job logs can become large, it is advisable to set under Spool Parameters that the log is not immediately output on the output device. The selection options are the same as the standard background printing parameters.
Monitoring an Archiving Run There are various system administration tools available to monitor archiving runs:
. Background processing tools
. Joblogs
. Spool lists (if created)
. System monitoring tools
. Data Archiving Monitor in the CCMS monitor sets
A log is created during an archiving run. If the application creates a specific log, this is used; otherwise, the standard log is used. The standard logs contains the number of archived data objects, the affected tables, the number of processed table entries, and the file sizes. The contents of the archiving can be stored to document level in application-specific logs.
You can trace the process of an archiving run with the monitoring of the background work processes using the transaction Simple Job Selection (transaction code SM37).
By choosing Job Overview, you can move directly from the initial screen of transaction SARA to transaction SM37. By choosing Management (after you have maintained an appropriate archiving object on the initial screen of transaction SARA), you can display a short log file of an archiving run from transaction SARA.
In addition, there is a specific data archiving monitor (monitor Data Archiving in the monitor set SAP CCMS Monitor Templates) in the CCMS monitor sets (transaction RZ20). It is intended for system administrators, so that they can monitor archiving runs in their familiar environment, the CCMS monitor. You can use the Data Archiving monitor to obtain an overview of the archiving objects in the system for which there are already runs. You can use the cross-archiving object Customizing to activate or deactivate it.
