Skip to Content

Start BO Services on a new box with an existing server snapshot


We took a backup of an existing production system and placed it on another server. I want this new system to be used as a DR when needed. I changed the CMS connections and started to start services but it failed. So I had to recreate a new node and it always asks me the cluster ID and I am worried if it would cluster with the existing environment.

What is the best way to go from here.?

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    Posted on Aug 25 at 05:57 AM

    Hi Sriharsha akkineni,

    You can use the same service account, there would be no issues with it.

    Also, if you want to restore the server configuration to your DR system, you can take the BIAR from the CCM.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 20 at 02:01 PM

    Hi Sriharsha,

    Yes, it might create a virtual cluster.

    Refer to KBA and perform all the steps mentioned in the restore.

    The DR system product version should be exactly same as the source. ( BI 4.1 SP01)



    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Sharvari,

      I did follow the steps listed but it looks like it got clustered again.

      I did change the CMS connection, i changed the cluster name and when i checked the new CMS the table was empty and the my production CMS tables had new entries. Any idea why that is happening?

      fyi we use sybase as our CMS

  • Posted on Aug 20 at 02:05 PM

    From past experience, I believe it will cluster with the existing environment if the servers are on the same network. Here's the process I've found that works when I'm setting up a DR BOBJ environment for my clients:

    1. On a clean server, install a new BOBJ system. For the CMS database, I would use the database that's going to be overwritten when restore the db from production into the DR environment. Also, use the same cluster key as prod.

    2. Configure the servers - split the APS, set the file store location, etc. Also configure the logon for the SIA, do Tomcat configuration, etc.

    3. Test to make sure that everything is working

    4. In the CCM, export the server config to a .biar file.

    Now, when you need to restore to the DR, you'll just need to do the following:

    1. Restore the Database and Filestore from production.

    2. In the CCM, restore the server config that you exported in step 4 above. This will overwrite the production server configuration in the restored database, ensuring that you're not clustering into your production system.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 21 at 12:30 AM

    I identified what was causing the issue. I changed the sql.ini file which was pointing to my prod cms and gave new server details and it worked without clustering it. The only difference i see is my reports are all old and I need to configure the service account.

    Quick question about the service account: If I use the same service account i use in prod will it cause any issues in this server?

    Question 2: Do i still need to take a BIAR copy form the prod CCM and update it here?

    And I am not trying to understand what happened to my reports since i see reports way back from 2015 though the backup team got the updated FRS copy.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.