Migrating Archive Administration Data

The migration of archive administration data (transaction SARA) is the transfer of a data archive (SARA archiving sessions) and all related archive files from an PI system (or client) in which archiving has already taken place to another PI system (or client), regardless of whether archiving has taken place there or not.

The processes described below refer to PI archive files (archive object BC_XMB) that have been created using the Archive Development Kit (ADK). Any statements referring to different systems also apply to different clients.

• The archive files are at one of the following locations:
  • In the file system (exchange directory) of the source system

    The archive files are to be migrated to the file system of the target system.

  • In the storage system of the source system

    The storage system is also connected to the target system.

• There is an RFC connection between the source system and the target system.

To transfer data archiving sessions from a source system to a target system so that it is technically possible to access the data in the target system, proceed as follows:

1. Use transaction SM59 to create a remote connection in the source system to the target client of the target system.
2. In archive administration in the source system, select the archiving sessions of the archive object BC_XMB that you want to migrate.
3. Migrate the selected archive files physically from the source to the target system:
   1. Make sure that all archive files for all archiving sessions are available in the source system.
   2. Copy the archive files to the directory in the target system.
4. Migrate the archive administration data from the source to the target system.
5. If you want to archive the administration data of the migrated sessions in the source system following migration, use the archive object BC_ARCHIVE, or add a comment that this session has been migrated to another system.
6. Check the result in the target system.

   After migration to the target system, there are two types of data archiving session:

   • Regular data archives (data that has been archived in the target system)
   • Migrated data archives (data that has not been archived in the target system)

Migrating Archive Administration Data

To migrate your archive administration data, proceed as follows:

1. In the Integration Engine menu, choose Administration → Schedule Archiving Job, then Archive Migration.
2. In the Archiving Session field, enter the numbers of the archiving sessions to be migrated.

   If you do not make an entry, all archiving sessions of the archive object BC_XMB are migrated.

   Note

   The session numbers are in archive administration under Management.

3. In the RFC Destination (Target Syst.) field, enter the name of the RFC connection to the target system to which the archives are to be migrated.

   The destination must exist in the source system.

4. In the Logical File Path (Optional) field, enter the logical path of the archive file, if this path is to be set explicitly in the target system.
5. If you want a comment to be visible in archive administration in the target system, enter the comment in the Comment in Target System field.

   You can enter a comment for each archiving session. The comment is then visible in the target system together with the number of the session to be migrated. If this field is left empty, the original text from the source system is used.

6. If you do not want to reset the reference to the storage system of the session to be migrated in the target system, deselect Reset Repository Status. The checkbox is selected as the default.
7. To migrate invalid archiving sessions as well, select Including Invalid Sessions. The checkbox is deselected as the default.
8. Choose Execute.

   The system displays a list of old and new session numbers.

Checking the Result in the Target System

Perform the following checks in the target system:

1. First check archive administration. The migrated session should be displayed with the new session number.

   However, this does not necessarily mean that you can access the archive files, since you may still have to transport the files in the file system to the target directory.

2. Choose Evaluate or use the archive file browser to test whether you can access a migrated session.
3. If necessary, rebuild the index of the migrated session in the target system.

   During migration, the index status of the archiving sessions to be migrated is reset to No Index Exists in the target system, even if an index had been built in the source system.