(DTERP-2302) How to copy/refresh production archive over to quality archive

Owned by SNP
Feb 10, 2023
2 min read

There are two options. They both require different efforts. Our recommendation would be option A. The options work with the assumption all Outboard related /DVD/* tables are refreshed from production to QA.

Option A: Adjustment of connection customizing & manual copy of documents within the Azure

  1. After the refresh you need to perform the typical drill – change of connection configuration from productive storage to the QA one (RFC destination, Settings in the Storage Management (/DVD/SM_SETUP), Content repository, etc.). The scale of the changes required depends on what you refresh.

  2. Copy & paste data from the productive storage to the QA one. The copy must be 1:1, retaining the names of files as well as containers. If you want to copy only certain specific files then you can identify corresponding ones using the following relationship:

    • Doc. attachments: TOA01*-ARC_DOC_ID = /DVD/CRP_SMCCMAP-DOC_ID; /DVD/CRP_SMCCMAP-SM_CONTAINER_ID is a folder (or a container) name while /DVD/CRP_SMCCMAP-SM_PACKID is the file name. At some storages is /DVD/CRP_SMCCMAP-SM_STORID a parent folder.

      * System might be utilizing also other link tables depending on customizing of respective document types (transaction OAC3), those tables can be TOA01, TOA02, TOA03, and TOAHR.

    • AKD arch. files: ADMI_FILES-ARCH_DOCID = /DVD/CRP_SMCCMAP-DOC_ID; /DVD/CRP_SMCCMAP-SM_CONTAINER_ID is a folder (or a container) name while /DVD/CRP_SMCCMAP-SM_PACKID is the file name. At some storages is /DVD/CRP_SMCCMAP-SM_STORID a parent folder.

Copying data between prod. and QA storage is either a manual copy/paste effort or there are tools that simplify it. For example, the copying of data between Azure storages can be simplified with Azure Data Factory provided by Microsoft.

Option B: Definition of a new Content Repository & migration

  1. After refresh you keep the connection to productive storage.

  2. Create a new content repository and set up a new source ID with the necessary configuration in the Outboard to point to the QA Azure Blob Storage.

  3. Migrate desired data between content repositories using the migration tools provided by Datavard.