NLS Data

The purpose of this document is to explain to the end-user the process of installing, using, and updating DataVard's OutBoard – a data lifecycle management application for Near Line Storage (NLS) of SAP BW data.
This document is aimed primarily at SAP system administrators and BW consultants who should primary work with OutBoard.
What is NLS?
Nearline storage (contraction of near-online) is used to describe an intermediate type of data storage that represents a compromise between:
• online storage → supporting frequent, very rapid access to data
• offline storage / archiving → used for backups or long-term storage, with infrequent access to data
Both archiving and Nearline allow a reduction of database size ⇒ that results in improved speed of performance (online system). However, accessing archived data is more complex and slower than is the case with Nearline storage, and can also negatively affect the performance of the main database (In case of data reload into that database).
NLS in the Context of ILM for SAP BW
Relevant data ⇒ BW Accelerator
Irrelevant data ⇒ Offline Archive
Potentially relevant ⇒ NLS storage (compressed data management)

_{ILM in SAP BW System}

_{Data flow in BW ILM with Outboard NLS}

NLS Writer for OutBoard by DataVard

NLS Writer for OutBoard is enhancement of standard SAP process for loading and activation in SAP BW. NLS Writer enables loading (for InfoCubes) and activation (for Data Store Object) of data within a locked period and the subsequent moving of data to OutBoard archive.
Normally, when data is loaded into SAP BW and part of this data is archived by OutBoard, the request will fail, because of the locked period. However, there are some scenarios there may be the need for old data to be loaded into the system on a frequent basis. To avoid failed load requests due to archived data in Outboard, the NLS Writer was developed.
The NLS Writer extension solves this particular issue in the following way:
1. Data Store Object:

1. Before data activation, NLS Writer recognizes whether records are from a locked area.
2. In case these records are in a locked area, the NLS writer loads records with corresponding key from NLS to an active table
3. Locked data check is suppressed, and the request is activated in a standard way by SAP.
4. After activation, locked records from active table are moved back to NLS archive.

2. InfoCube:

1. During data load (Data Transfer Process or InfoPackage), NLS Writer recognizes if loaded records are from locked area.
2. In case that records are in a locked area, NLS archive is updated with this data.
3. Locked records are removed from data load.
4. Only non-locked data is loaded into InfoCube using standard way.