Skip to Content

As a part of SAP Business objects Administration, Sometimes BO admin needs to replicate the BO environment.

Example: PROD environment will be having more no of reports (more than 2000) and users (20000) and currently it is in BI4.0 SP3, As per the business requirements they have to upgrade all the BO environments to Higher Service Patch level of BI4.0.

Users would like to check PRODUCTION reports in BI4.0 SP7, without upgrading/disturbing the existing environment.

We can refer this document to replicate the BO environment from PROD to a Temporary server.

1)     In New servers:

Installing BI 4.0 SP3 in the BRAND new servers and Copy and configure the CMS DB and FRS from PROD to the newly installed servers. Later install SP7 on top of SP3.

2)     Mirroring the servers:

PROD server Installations and Physical hard disk needs to be mirrored to other servers which are having different host name and different IP address. In the same way CMS DB needs to be mirrored to other Database.

Let us discuss each method one by one

Replicating in new servers:

  • Install BI4.0 SP3 in the Temp server.
  • Copy the FRS from PROD server to TEMP server.
  • Copy the PROD CMS DB and place it in new Temp DB.
  • The below steps needs to be done on the TEMP server (not on the PROD servers). 

Login to TEMP server

Go to the CCM, stop the SIA.

/wp-content/uploads/2013/08/1_258437.jpg

go to SIA > Properties > Configuration

/wp-content/uploads/2013/08/2_258454.jpg

Click on CMS System Database configuration Specify.

/wp-content/uploads/2013/08/3_258467.jpg

Update Data source settings

/wp-content/uploads/2013/08/4_png_258468.jpg

Click on OK

Update your new Temp CMS DB details .(make sure that you are using new Temp CMS DB User Name and Pwd)

/wp-content/uploads/2013/08/5_258476.jpg

In next step Update the Cluster key ( as we have copied CMS DB from PROD, Please enter the PROD Cluster Key). Click on Apply and OK

Modify the Cluster Name of the TEMP environment to be different from the PROD environment.

/wp-content/uploads/2013/08/6_258478.jpg

Modify the Cluster Name of the TEMP environment to be different from the PROD environment.

Login in CMC with ADMIN ID. Go to servers and Nodes.

/wp-content/uploads/2013/08/7_258482.jpg

Then start SIA.

CMS.exe service has to be running in the Task manager.

Make sure that CMS is started completely.

Login in TEMP CMC with ADMIN ID (as we have copied PROD CMS DB, we need to use PROD Admin PWd ) .

Change the Admin Pwd.

Go to servers and Nodes.

Delete all the servers referring to PROD environment. (Do not delete the running Central Management server which is pointed to TEMP SIA.)

All the services are deleted in CMS, now we need to delete the PROD NODES from TEMP CMC.

Note down the CUID’s of all the PROD nodes and login to NEW TEMP CMS DB.

Execute the below SQL statement

‘DELETE FROM CMS_INFOOBJECTS7 where SI_CUID = ‘CUID of the PROD NODE’ and commit the changes.

Run the same command for all the PROD nodes and make sure that all the services/Nodes are deleted except Temp server.

Now all the nodes and services are deleted from TEMP CMC.

Restart the Temp SIA.

Now we will be having only CMS is running. We need to have other servers to run the report.

We need to create a new node in the Temp server.

Login in to TEMP server and go to CCM.

In CCM select “Add Server Intelligent Agent”.

Create a new SIA, give the name of the SIA and use a different port (i.e. 6411)

/wp-content/uploads/2013/08/8_258483.jpg

Click on Add node with Default servers and next

/wp-content/uploads/2013/08/9_258484.jpg

Click Use existing Running CMS

/wp-content/uploads/2013/08/10_258488.jpg

Change the CMS port to 6401. ( default CMS will be using 6400, Hence we can use 6401)

Specific the new CMS DB Details with the cluster key.( recently changed Temp server cluster key  needs to be used)

/wp-content/uploads/2013/08/11_258489.jpg

/wp-content/uploads/2013/08/12_258490.jpg

Give temp BO server admin Id and Pwd and click on Next.

/wp-content/uploads/2013/08/13_258497.jpg

After few minutes new node will be created in the  CCM.


1.       First node will be having only CMS with PORT no 6400, SIA PORT 6410

2.       Second node will be having all the services including CMS with port no 6401, SIA PORT 6411.


After few minutes new node will be created in the  CCM. start the newly created SIA. make sure that all the services are running.

Now we need to delete the SIA which was created initially ( SIA with only CMS).

Stop the Old SIA  and Now delete the OLD  SIA using the Newly created running SIA .

/wp-content/uploads/2013/08/14_258498.jpg

Now the Old SIA is deleted and system is ready to use with the new SIA node ( CMS PORT: 6401,SIA PORT:6411)

/wp-content/uploads/2013/08/15_258499.jpg

same port numbers can be used for login. change it to CMS port:6400 and SIA PORT:6410, To avoid the change in web application server properties.

Temp server is ready with the PROD objects and users.(with SP3)

we need to upgrade this Temp server from SP3 to SP7 to release to the users for the initial testing.

Few of the steps are similar to the Manikandan Elumalai Blog.

http://scn.sap.com/community/bi-platform/blog/2013/03/23/business-objects-content-recovery-and-disaster-recovery


I will be sharing the Mirroring the server’s method and few of the best practices in my next Blog.

Hope the blog is Interesting. Keep reading!






We can refer this document to replicate the BO environment from PROD to a temporary server


To report this post you need to login first.

23 Comments

You must be Logged on to comment or reply to a post.

  1. Denis Konovalov

    much simpler process is to build new server with latest patch and use promotion management to move reports that needs testing from existing to the new server.

    Maintain this test server as the sand box env for all the new patches testing..

    (0) 
    1. Patrick Perrier

      Agree with Denis.  This is over complicating the problem and the solution is not simple.

       

      (see, we can agree in things )

       

      If you truly want to mirror an environment, you could use the UMT with the switch -internal_use_only_noversioncheck to move objects from SAP BI 4.x to SAP BI 4.x which I was told at SAP TechEd Amsterdam is now officially supported.

       

      See: http://scn.sap.com/thread/3414235

      (0) 
  2. bhanjakishore Mohapatra

    Hi

     

    I am following your blog to replicate prod data in sandbox.

    I am using BI4.0 sp5 in both the environments.However my prod is a cluster environment with windows Ruth where as sandbox is a single system installation with enterprise auth.

     

    I am successful till the Add node step where i can add a node but the default services are not getting added.I assume it requires further changes which are not mentioned in this blog.Could you please let me know what is required to restore content of a cluster environment to a sandbox.I am following the below steps.

     

    1.restored the DB in temp server

    2.Deleted all the ,nodes and services

    3.changed the cluster name

    4.restarted SIA.

    5.Added a new SIA node with CMS. When logged into the SIA i can not see any services.

    6.I can log in to cms and view the folders and reports are available but can not use them as difault servers are not available.

     

    Regards

    Kishore

    (0) 
    1. PRASAD JRK Post author

      Create one More SIA in the same node with the ref of initial node using other ports.(SIA and CMS)

       

      once second node is up and running, you can remove the first node.

      (0) 
  3. John Clare

    Can you please change this blog to include a step to add entries in the host file on the new temp environment which points the production servers back to the temp server. Otherwise people will run the risk of affecting the production environment. Better still build the temp environment on a different network.

    (0) 
  4. Ian Gillan

    Hi, I have followed the steps shown to the letter however I get the following while trying to remove the Temp SIA; Failed to locate a node with name … in the CMS. Verify your CMS conection information.

     

    I suspect that the step where you state:

     

    Now all nodes and services are deleted from TEMP CMC actually requires the node relating to the Temp SIA.

     

    Please get back to me on this.

     

    Plus more detailed instructions of each and every step would certainly help.

     

    Cheers

     

    Ian

    (0) 
  5. Narendar Mamidi

    Hi Prasad,

     

    We have followed the same steps to replicate one of our system for which Single sign on is enabled and CMS.Visible=false for BI launchpad.

     

    When we are launching temp BI Launchpad and CMC, its pointing to Original system CMS instead of newly created one as we haven’t updated cms.default of BIlaunchpad and CmcApp property files with new system names and new port.

     

    Thanks

    Narendar

    (0) 
  6. Dhiraj Wamanacharya

    Hi,

    Which among these 2 is a preferred method of doing a system copy ( Our requirement is copy a development server to a sandbox system ) ?

     

    1. The one mentioned above in the blog by Prasad

    2. One mentioned by Patrick Perrier –  i.e (you could use the UMT with the switch -internal_use_only_noversioncheck to move objects from SAP BI 4.x to SAP BI 4.x )

     

     

    If method 2 is the preferred method, do we need to do a DB copy as well  (taking a Oracle level backup / restore )

     

    Kindly confirm

     

     

    Regards

    Dhiraj Wamanacharya

    (0) 
      1. Dhiraj Wamanacharya

        Hi Jawahar,

         

        Thanks for your response. However Patrick also mentions ” I was told at SAP TechEd Amsterdam is now officially supported.”

         

        Is the UMT method still not supported ?

         

        Regards

        Dhiraj Wamanacharya

        (0) 
        1. Denis Konovalov

          UMT noversion switch was never and will never be supported. It was created for testing purposes and does not properly work in 4.1 to 4.1 scenarios.

           

          Do not use it. Period. UMT does not moves all the metadata in such cases.

          (0) 
  7. Chris James

    I ran into a problem changing the CMS Cluster Key name,  my DEV system reports it failed to change the cluster key, it connected to my PROD CMS and said its need to be stopped to change the cluster key.  How do I change the cluster key without affecting PROD?

    (0) 
    1. Jawahar Konduru

      Follow below steps to change the cluster key

       

      1. To launch the CCM, go to Programs > SAP BusinessObjects Enterprise XI 4.0 > SAP      BusinessObjects Enterprise > Central Configuration Manager.

      2. In the CCM, right-click the Server Intelligence Agent (SIA) and choose Stop.

         Caution: Do not proceed to Step 3 until the SIA status is marked as “Stopped”.

      3. Right-click the Server Intelligence Agent (SIA) and choose Properties. The “Properties” dialog box opens.

      4. Click the Configuration tab.

      5. Click Change next to “CMS Cluster Key Configuration”. A warning message is displayed.

      6. Click Yes to continue. The “Change Cluster Key” dialog box opens.

      7. Enter the same eight-character key in both the “New Cluster Key” and “Confirm New Cluster Key” fields.

      (0) 
      1. Chris James

        I get an error message after step 7.   “Failed to change cluster key. Reason: Operation requires all CMS(s) in the cluster to be stopped. Please stop CMS xxxxx.CentralManagmentServer (id: 853). (FWB 00065).”

         

        Should I create a new SIA?

        (0) 
  8. Joby Mathew

    HI JRK,

     

    Could you please update me on how to do a Mirroring of Windows Server (other than FRS & DB restore).  Or is there any link to explore that procedure.

     

    Thanks, Jo

    (0) 
  9. Syed Peerzade

    Hi Guys

    Can we replicate BI on a lower environment from production, say quality? If yes, then does the hardware has to be similar?

    My concern is we want to bring our entire production content to Quality and then update the quality system from BI4.1 SP5 to BI4.2 Sp3, since in Qa the there is one CMS and one tomcat servers and in Prd we have two CMS and two tomcat servers, is this possible? If not, what is the best way to do this?

    Thanks

    Syed

    (0) 

Leave a Reply