Show TOC

Background documentationILM-Specific Enhancements to Archive Administration

 

If you activate the ILM Business Function, the system enhances the archive administration by ILM-specific functions and fields.

Features

Archiving Session Overview

The system lists the complete archiving sessions for the data intended for destruction as well as the snapshots in a separate category, which in turn has the following subcategories:

  • Delta Runs from File Conversion

    Sessions resulting from ILM archive file conversion with archive files for all data objects to which no ILM rules applies and for which follow up activities are required.

  • From File Conversion

    Sessions resulting from ILM archive file conversion with archive files for all data objects to which at least one ILM rule applies. If a valid ILM store is specified in this ILM rule, then the archive files for this session can be stored.

During ILM archive file conversion, the system transfers existing notes to the new archive files. ILM archive conversion creates new archive files in which data objects are grouped according to the ILM rules.

ILM-Specific Details about the Archive File

  • Stored via

    Identifies the interface with which the archive file was stored (ArchiveLink or WebDAV)

  • URI

    Uniform Resource Identifier (address) of the resource (archive files) or collection (hierarchy nodes) in the ILM store.

  • XML DAS Connection

    Identifies the name of the HTTP connection to the XML DAS through which the WebDAV Server is connected.

  • Archive Store

    Identifies the memory area within a storage system for the collections and resources.

  • Expiration Date

    Names the expiration date that Information Retention Manager (IRM) has determined for this file.

  • Compulsory Destruction Date

    Identifies the date as of which the resource has to be destroyed. The system calculates this date from the maximum retention period specified in the IRM for this file. The system specifies the earliest maximum retention date for all objects contained in this file.

  • Archive File Is Invalid

    The archive file has been marked as invalid in the store browser and is therefore no longer available for further processing.

Legend

The legend in archive management contains the following relevant entries for ILM:

  • Delta Runs from File Conversion

    The session was created during ILM file conversion and contains all the data objects to which no ILM rules applies. Follow-on activities are required before the corresponding archive files can be stored.

  • From File Conversion

    The session was created during ILM file conversion and contains all the data objects to which at least one ILM rule applies.

  • Data Destruction Runs

    The session was created for data destruction. After completion of the delete phase, the files created as a result were automatically deleted by the system.

  • Snapshots

    The archiving session contains a copy of data from the database. The data is not deleted from the database.

  • Some or all Archive Files Destroyed

    At least one archive file was destroyed for this archiving session during data destruction. You can expand and display the remaining files in archiving sessions for which not all files were destroyed.

Invalid Resources

You can identify those resources (archives files) in the archive hierarchy that are not to be used because they contain errors or are not needed as invalid in the ILM store browser. Invalid resources are exclude from use for evaluation purposes in audit packages.

You can see that an archive file is invalid if it has the status Archive File Is Invalid with the corresponding symbol in the details for the file in archive management. In manual archive selection, the system displays invalid archive files and archiving sessions that contain invalid data with a lightning icon. The prerequisite for this is that you select the For Stored Files checkbox in Customizing under Start of the navigation path Cross-Archiving Object Customizing Next navigation step Technical Settings Next navigation step Check Access for Archive Selection End of the navigation path. If the checkbox is not selected, then there is no check and the affected sessions and files can be selected as normal.

If an invalid archive file is opened for a sequential read access (during read, delete, convert, reload, and during the ILM file conversion), then the system skips the contents of this file. If a session consists of multiple archive files, of which at least one is invalid, when they are accessed the system only processes the contents of the valid files. If a session contains only invalid files, then an exception is triggered which results in the system terminating the read of the data objects and closing the file. The Archive File Browser is a technical tool for analyzing problems during archiving. You can use it to display the contents of invalid archive files. Search functions are also supported here.

Removing Invalid Status

Setting archive files to invalid is an exceptional action that should only be used if absolutely necessary. You can remove the invalid status for an archive file, however, this is only useful in certain circumstances. All sequential operations that process archive files and change the file status or the status of the archiving session (delete, convert, reload, convert ILM file in update mode) also perform these status changes for invalid archive files. If you remove the invalid status after one of these operations, then these archive files cannot be processed again due to the status already being set. Depending on the operation this has the following consequences:

  • Delete: The data objects contained in the file were not deleted from the database during processing, but the file has the status Delete Completed.

  • Convert: All files (including the invalid files) have the status Converted after the session and can no longer be processed by read accesses. The data objects that were contained in the invalid files for this session were not processed and therefore are not included in a new session.

  • Reload: All files (including the invalid files) have the status Reloaded after the session and can no longer be processed by read accesses. The data objects contained in invalid files for this session were not processed. Therefore they were not written to the database and they are not contained in a new session.

  • ILM File Conversion: All files (including the invalid files) have the status Converted after the session and can no longer be processed by read accesses. The data objects contained in invalid files for this session were not processed. Therefore they are not in a sorted new run nor in any delta archiving sessions that may be created.

ILM-Specific Properties of Archiving Sessions

In archive administration, you use the ILM-specific properties of archiving sessions as follows:

  • For information, such as the ID and client of the original system in which the archiving sessions was executed

  • As a filter for displaying archiving sessions

  • As search criteria for archiving sessions and archive files