Page tree
Skip to end of metadata
Go to start of metadata

Purpose

SAP recommends that you perform a system copy to create test, demo and training systems. Also, if you need to change your operating system and/or database, you have to perform a migration of your SAP system.

Overview

System copy enable you to create consistent copies of your SAP systems, flexibly adapted to your needs - be it an SAP system distributed to several hosts, a high-availability system or a system on a rather exotic operating system/database combination. Also, the procedure is offered for ABAP, Java and dual-stack systems.A system copy can be either homogeneous or heterogeneous.

Homogeneous or Heterogeneous System Copy

Homogeneous System Copy :

  • Both operating system and database system stay the same
  • Performed in most cases with database -specific procedure (database - independent procedure could optionally also be used)

Heterogeneous System Copy :

  • One of the following is changed during the system copy:
  1. Operating system (in this case, system copy is called OS migration )
  2. Database system (in this case, system copy is called DB migration )
  3. Operating system and database system (in this case, system copy is called OS/DB migration )

Use of system copy procedures

The system copy procedure is useful in case of : 

  • Create test, demo and training systems as copy of existing systems.
  • Change your operating system and/or database by migrating your system.

Action plan for system copy procedure

  1. Download the software provision manager tool (SWPM)
  2. Download the documentation for latest version of system copy guide from SAP Support Portal at: http://support.sap.com/sltoolset --> System Provisioning
  3. Plan
    1. See product availability matrix of SL Toolset in SAP Support Portal at: http://support.sap.com/pam

    2. Check latest information in following SAP notes :
      1. System copy of systems based on SAP NetWeaver 7.0x: SAP Note 1768158 

      2. System copy of systems based on SAP NetWeaver 7.1x and higher: SAP Note 1738258

  4. Prepare
    1. Perform preparation tasks as described in system copy guide
    2. Unpack the Software Provisioning Manager 1.0 or 2.0  ( For unpacking the software use SAPCAR tool , please see SAP note 212876 - The new archiving tool SAPCAR )

      1. Use the command : SAPCAR –xvf <download directory>/<path>/<Archive>.SAR -R <unpack directory>
  5. Execution
    1. Start the sapinst tool ( \sapinst.exe OR ./sapinst )
    2. Execution EXPORT phase 
    3. Execution IMPORT phase
  6. Follow Up activities

System Copy Guides

  • System copy guide based on Software Provisioning Manager 1.0

    • System Copy - Target Database SAP HANA . Please refer LINK
    • System Copy - Target Databases Other than SAP HANA . Please refer LINK

  • System copy guide based on Software Provisioning Manager 2.0

    • System Copy Guides - Software Provisioning Manager 2.0 . Please refer LINK

Related Documents

  • SAP WIKI on system copy details : WIKI
  • Migration to SAP HANA

  • Best Practice Guide - Classical Migration of SAP NetWeaver AS ABAP to SAP HANA → LINK 
  • FAQ - System Copy and Migration: → LINK
  • Overview - System Copy and Migration with Software Provisioning Manager 1.0 → LINK
  • Technical Details - System Copy and Migration Process with Software Provisioning Manager 1.0 → LINK
  • SAP Support Portal at: http://support.sap.com/sltoolset

Related SAP Notes/KBAs

SAP Note 1738258 - System Copy for Systems Based on SAP NetWeaver - Using Software Provisioning Manager 1.0

SAP Note 1680045 - Release Note for Software Provisioning Manager 1.0 (recommended: SWPM 1.0 SP 23)

SAP Note 2568783 - Release Note for Software Provisioning Manager 2.0 (recommended: SWPM 2.0 SP 00)

SAP Note  212876 - The new archiving tool SAPCAR

 

  • No labels