cancel
Showing results for 
Search instead for 
Did you mean: 

Data Archiving - very urgernt

Former Member
0 Kudos

Friends

Could anyone send me the details on Data Archiving

Methods, its pros and cons. - v. urgent. Will Reward with points.

bpremah@rediffmail.com

Thanks in Advance.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Mahe,

You can use transaction SARA (Data Archiving).:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/8d/3e4d70462a11d189000000e8323d3a/frameset.htm

Data Archiving removes from the database application data from closed business transactions that are no longer relevant for the operational business. The archived data is stored in archive files that can be accessed by the system in read-only mode.

Data Archiving – a service provided by SAP NetWeaver – removes mass data that the system no longer needs online, but which must still be accessible at a later date if required, from the database.

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.

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).

Step 2: Storing Archive Files

Once the write program has finished creating archive files, these can be stored.

There are several ways of storing archive files:

• Storage Systems:

If a storage system is connected to mySAP Business Suite: At the end of a successful write job, a request is sent to this system to store the new archive files (provided the appropriate settings were made in Archiving Object-Specific Customizing. You can also store archive files manually at a later point if you do not want them to be stored automatically. Storage is carried out by the SAP Content Management Infrastructure (which contains the ArchiveLink/CMS interface).

• HSM Systems

If you use an HSM system, it is sufficient to maintain the file name in Customizing (Transaction FILE). You do not then need to communicate with the storage system using the SAP Content Management Infrastructure, because the HSM system stores the files on suitable storage media according to access frequency and storage space.

• Existing Storage Media

Once the delete program has processed the relevant archive file, you can manually copy archive files to tape.

Step 3: Running Delete Programs

After closing the first archive file, Archive Administration creates a new archive file and continues with the write process. If the settings were made accordingly in archiving-object-specific Customizing (see Settings for the Delete Program), a delete program is started automatically in parallel for the previously created archive file, to read the data in the archive file and then delete it from the database. This procedure guarantees that only data that has been correctly saved in the archive file is deleted from the database.

You can also schedule the delete program manually, for example, so that you can save the archive files before deletion, or because the next available time window is not sufficiently long to also include deletion. The following scenario may also be a reason to manually schedule the delete program:

You create an archive file by starting a write program. The data records are written to an archive file, but the system terminates processing before the delete program starts to run. In this case you must delete the archived data manually in a separate step.

If you do not carry out deletion until after the data has been stored, you can make a setting in Archiving Object-Specific Customizing so that the system will read archive files the from the storage system during deletion. In this way, you can detect errors in good time which might arise when transferring or saving the archive files in the storage system.

When the last archive file is closed, a delete program starts to run for this file. The graphic shows that several delete programs are running simultaneously for previously created archive files. Because, unlike the delete program, the write program does not generally carry out any transactions that change data in the transactions, the write program creates new archive files faster than they can be processed by the delete program. This decreases the total archiving runtime because the database is used more efficiently.

Reward points if it helpful

Regards,

Govind.

Former Member
0 Kudos

Hi,

Mail sent to u r ID

<b>Reward Points if it is usefull</b>

Regards

jiteshmehta
Active Contributor
0 Kudos

Hi

you can refer http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARC/CAARC_INTRO.pdf

Introduction to Data Archiving

Regards

Jitesh