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

[former_member692700]

Hello,

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.?

[former_member692700]

forgot to add details

It is a windows server with SAP BO 4.1 Sp01 with Sybase as CMS. OS is Windows 2012 Datacenter

[former_member185603]

Follow my blog, it should applies to you as well.

https://blogs.sap.com/2019/08/14/bi-4.x-server-migration-from-2008-to-2016-and-how-to-get-the-conten...

[former_member263415 · Accepted solution]

Hi srisri.sap333,

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.

Regards,

Sharvari

[DellSC]

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.

-Dell

[former_member692700]

I would have done the same way, but we are testing DR this week and i have been trying to figure out a solution for it making changes to the existing backup on the DR server

[DellSC]

I understand, but I've found that this is really the only way to get it to work if the DR server is on the same network as the cluster. If you just use a restored backup of the original server, it's always going to re-connect to the cluster, even if you're pointing it to a different database.

-Dell

[former_member263415]

Hi srisri.sap333,

Yes, it might create a virtual cluster.

Refer to KBA https://apps.support.sap.com/sap/support/knowledge/en/1275068 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)

Regards,

Sharvari

[former_member692700]

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

[former_member692700]

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.