Skip to Content

BO 4.1 System Copy


i have to do a system copy for our BO Systems.

Actually we had two BO Systems after that we would like to have 3 System. The production System will be our starting system but all systems have to migrate to new hardware.

I have read the section 14 in Admin Guide but i'am not happy with that.

Is there anybody how has done such an system copy in the last time.

At the moment i think we have to do the following:

- Install the new Target System with the same SP and Patchlevel as the old source system.

- Backup DB and Filestore, also other thinks like Monitoring and LCM DB

- Restore DB and file store to new environment

- Create new SIA pointing to the restored DB.

- Changing Cluster name

But what is with the name of the SIA. I know i cannot change them only if i create a new SIA but i would like to use my old Server configuration.

Our new QA and new prod system shall run at the same time and it is not an option for my to have the same sia name in booth system.

Is there anybody how can explain it a little more in detail?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Feb 07, 2017 at 07:23 PM

    Hi Carsten,

    The steps mentioned in SAP Note 1275068 is designed for disaster/recovery purpose. However you can use it to copy BI4.x system. But let say sap support will not be responsible for the generated issues if it is not for recovery purpose. But I do see several SAP BI customers using this methodology to more content from 1 BI4.x to another Bi4.x system.

    The major porblem is after you recover system, SIA is same for source BI4.x and target Bi4.x because it is sytem copy, so SIA node is same. you need to manually create a new SIA on target Bi4.x for a differnt name otherwise LCM promotion job will fail.


    Add comment
    10|10000 characters needed characters exceeded

    • Hey,

      thanks for your reply. Ok that´s exactly my experience. The problem is that if i create a new SIA all the customizing in the different services / servers are not available. Also i think there is a lot of manual work after this system copy. If you use the productive environment as source for your test system then mostly you have to manually adjust the authorizations, single-sign-on, connections and so on.

      What i had done now is a new installation and transport only the used content. In this case we can adjust some old mistakes and get a new clean system.

      Thanks all for your help.

  • Feb 02, 2017 at 09:26 PM
    Add comment
    10|10000 characters needed characters exceeded

  • Feb 03, 2017 at 06:58 AM

    Hey thanks Denis,

    i know this KBA but as you can read in the top it`s only for desaster recovery.

    Can I use it for my purpose, too?

    Thanks in advance


    Add comment
    10|10000 characters needed characters exceeded

  • Feb 08, 2017 at 03:37 PM

    Here's what I have done successfully:

    - After installing the software on the "target" server, configure all of the server processes in the Servers section of the CMC.

    - In the CCM, back-up the server configuration to a .biar file.

    - Restore the DB and FileStore.

    - In the CCM, connect the SIA to the new database but do not start it.

    - Restore the server configuration .biar file using a - this will overwrite the server config from your backup with the one that is specific to this server.


    Add comment
    10|10000 characters needed characters exceeded