Show TOC

  Step 1: Creating (the First) Archive Files

In step one, the write program creates an archive file. The data to be archived is then read from the database and is written to the archive file in the background. This process continues until one of following three events occurs:

  1. All the data is written to an archive file

  2. Archiving is not complete, but the archive file reaches the maximum size specified in archiving object-specific Customizing

  3. The archiving is not yet finished, but the archive file contains the maximum number of data objects specified in Customizing.

    Note Note

    If in cases 2 and 3 there is still data to be archived, the system will create another archiving file.

    End of the note.

If event 2 or 3 occurs, then archive management continues with the delete step (assuming that the following indicators are marked in archiving object-specific Customizing: Start Automatically and Delete Before Storage ).

Note Note

Write jobs can be scheduled outside Archive Administration (transaction SARA ) using an external job scheduler. This enables you greater flexibility when coordinating data archiving processes with the other processes in your system environment. For more information, see Scheduling Write Jobs Outside Archive Administration .

End of the note.

Virus Scan

As with all electronically stored data, data records in the database can also be infected with viruses. It is possible, although highly unlikely, that these viruses are spread through the archiving of the infected file. You can therefore run a virus scan on the data to be archived during the write phase of your archiving session. During this check, the system scans all data objects that contain records with fields in which the type XSTRING (variable string of bytes) or X (byte string) appear. Only these data types of byte strings are potential carriers of viruses.

The ADK virus scan is integrated in the SAP NetWeaver Virus Scan Interface and can be activated and used as described there. The virus scan profile is called /SARC/ARCHIVING_ADK and is set by default to inactive. When the profile is activated the message “Virus Scan with Virus Scan Profile /SARC/ARCHIVING_ADK active” appears in the job log of a write job. This message is always issued, even if the scan did not identify any potentially infected data objects. Performance is not significantly affected by the virus scan.

If an infected data object has been found, ADK issues the following message: “Virus <Name> in Object <Structuretype> <Component> found”. The write program is terminated with a system exception and the affected session is treated like any other terminated session in Archive Administration (for example, errors due to technical reasons). Archive files that are not infected and that have been completely written and correctly closed at the time of the program termination, remain intact.

Write Run Followed by Event

After all archive files have been completely created for an archiving session, the Archive Development Kit (ADK) triggers the system event SAP_ARCHIVING_WRITE_FINISHED. By reacting to this system event, you have the option of scheduling archiving jobs automatically. This includes the rebuilding of indexes or input help, archive file backup before deletion, and so on. The event parameter is, in each case, the number of the archiving session.

To further automate the archiving process, you can transfer the archiving session number to function module ARCHIVE_GET_FILES_OF_SESSION. This determines, on a platform-independent basis, the names and paths of the archive files that were written in an archiving session.

You can define new jobs in transaction SM36. You maintain events in transaction SM62 .

See also:

Creating Archive Files

Archiving Object-Specific Customizing