Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Requesting an SAP ERP system copy service

SAP ERP system copy is the process of duplicating an SAP system. A system copy can be either homogeneous or heterogeneous. During a homogeneous system copy, you use the same operating system and database platform as the original system. Conversely, during a heterogeneous system copy, you can change the operating system, the database system, or both. Heterogeneous system copy is a synonym for migration.

The SAP system that contains the original database is known as the source system and the system to which the database copy is to be imported is known as the target system. During SAP ERP system copy, certain SAP parameters may change. When you perform a system copy, SAPinst installs all the instances again, but it uses a copy of the source system database to set up the database.

This section contains the following topics:

Before you begin

Ensure that you have completed the following activities before requesting the service offering:

  • Create or update the SAP user DDIC in every client of the source and target system with the same password.
  • Create or update the SAP user CLMADM in every client of the source and target system with the same password.
  • Verify that there is an authorization role with access to the SAP transaction ZBDLSMAINTAIN and activity BDLS in the authorization object ZBMC_SCAPA.
  • Maintain the SAP logical system pair using the SAP transaction ZBDLSMAINTAIN.

Overview of the process to initiate an SAP ERP system copy

Several BMC Server Automation BLPackages work together to initiate a system copy on a target virtual machine. The target virtual machine is provisioned through BMC Cloud Lifecycle Management.

BMC Cloud Lifecycle Management:

  1. Executes a file deploy job SAP_ERP60_EHP5_NW702_ABAP_RHEL64_ORA11203_FSC_v1.0 on the target machine to create the file system that is required for SAP.
  2. Copies ASP media to the target machine with the BLPackage SAP_SYSCOPY_ERP60_EHP5_NW702_ABAP_RHEL64_ORA11203_MEDIA_v1.0.
  3. Performs the prerequisite check on the target machine with the BLPackage SAP_ERP60_EHP5_NW702_ABAP_RHEL64_ORA11203_PRC_v1.0.
  4. Creates OS users and groups for SAP with the BLPackage SAP_ERP60_EHP5_NW702_ABAP_RHEL64_ORA11203_UGRC_v1.0.
  5. Installs the Oracle database with the BLPackage SAP_ERP60_EHP5_NW702_ABAP_RHEL64_ORA11203_DBI_v1.0.
  6. Takes a backup of the Source ERP system and stores it in a shared location with the BLPackage SAP_SYSCOPY_ERP60_EHP5_NW702_ABAP_RHEL64_ORA11203_SB_v1.0.
  7. Restores source system backup and performs postconfiguration with the BLPackage SAP_SYSCOPY_ERP60_EHP5_NW702_ABAP_RHEL64_ORA11203_SYSCOPYE_v1.0.

To request an SAP ERP system copy service

  1. Log on to the Cloud Portal.
  2. Navigate to Service Instances.
  3. Click the Service Catalog tab. 
  4. In the Request Service section, click System Copy ERP 6.0.

    1.jpg

    The SYSCOPY ERP60 EHP5 ABAP based on NW702  RHEL/Oracle screen appears.

    2.jpg

  5. In the Parameters section, enter the appropriate parameters in the respective fields as described in the table below:
     

    Label 

    Parameter used

    Description

    Database Backup Host 

    STORAGE_LOCATION

    • Enter the host name where the databse backup can be stored.

    Source SAP System Database Hostname 

    SAP_SOURCE_HOSTNAME

    • Enter the host name of the database host.

    To find out the host name, enter the command hostname on the database host.

    Source SAP System ID (SAPSID)

     

    SAP_SOURCE_INST

    • This ID is the identifier for the Source SAP system.

    Target Central Instance Number 

    SAP_INSTANCE_NUMBER

    • This number is the technical identifier for internal processes.

    • The instance number consists of a two-digit number between 00 and 97.

    • AIX: Do not use 01 or 02 and 39 as instance number.

    • HP-UX: Do not use 02 and 75 as instance number.

    • Windows: Do not use 43 and 89 as instance number.

    Target SAP System ID (SAPSID) 

    SAP_INST

    • This identifier applies to the SAP system.

    • The ID is unique throughout your organization.

    • The ID consists of exactly three alphanumeric characters.

    • The ID contains only uppercase letters and the first character must be a letter, not a number.

    • Reserved IDs cannot be used.

  6. Click Next.

    The second section of the SYSCOPY ERP60 EHP5 ABAP based on NW702  RHEL/Oracle screen appears.

    3.jpg

  7. Enter the appropriate values in the following mandatory fields:
    • Quantity
    • Instance Name Affix
    • Username
    • Password

    • Confirm Password

      Note

      The Username must be root. The quantity must be always 1.

  8. Click Next.

    The last section of the SYSCOPY ERP60 EHP5 ABAP based on NW702  RHEL/Oracle screen appears.

    4.jpg

  9. Verify the information that you entered and click Submit.

    After you submit the request, it takes a couple of hours to complete the SAP ERP system copy provisioning.
     

Limitations

The following limitations pertain to SAP ERP system copy provisioning:

  • The disk space required for backup for a system copy is not checked. BRBACKUP displays an error message if the storage space for backup is insufficient.
  • The file system space requirement is not calculated or provisioned during the system copy process.
  • The <SAPSID> is not validated for restricted <SID>.
  • There is no option to enter the Master password. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*