BOBJ 4.2 SP8 PL3 Migration from one machine(SLES12) to new mahcine(SLES15)

[saxenashubham012]

Hi All,

Our Current Deployment: we have 3 BOBJ servers, 2 are running on OS SLES 12 and the third one is on Windows Server only hosting AO for office with version 4.2 SP8 Patch 3

Requirement: Move from machines SLES12 to SLES 15. So, we need to migrate BOBJ to new machines which are running on SLES15.

We are struggling with finding right approach to do this. Below we are thinking:

1. ---> One approach we are thinking to follow SAP Note 1275068 but it states is only designed for disaster/recovery purpose

2. ---> One we are thinking if we can add two new nodes(running on SLES 15) in the existing CMS cluster(running on SLES 12) and then copy File system database from existing to new nodes and then finally deleting old nodes. Not sure if I can add new nodes running on SLES15 to existing CMS cluster which is on SLES12

Kindly suggest me how I can migrate from SLES12 to SLES15 machine without any loss of data. And also, In any of the approach to move BOBJ from one linux machine to another, how to deal with my AO for office server which is running on Windows server.

I am posting this hoping to get some guidelines or suggestion. May be some of you have already done this migration and guide me with right steps.

Thanks,

Shubham

[saxenashubham012]

As per section "When not to use Promotion Management?" in "SAP BusinessObjects BI Pattern Guide"(URL: https://assets.cdn.sap.com/sapcom/docs/2017/03/ea02bd5e-b17c-0010-82c7-eda71af511fa.pdf) if we want to change OS of the SAP BusinessObjects BI Platform, Simply adding a node to the existing cluster by ‘expanding’ the cluster during installation (using the new OS) and retiring the old node (on the old OS) is recommended instead of using Promotion management.

Could you check the same and confirm if it can be followed because in our case also we want to change OS from SLES12 to SLES15.

[saxenashubham012]

Thanks for your response Denis and Manuel..

Is it really possible to add another node which is on SLES15 to existing CMS cluster which is on SLES12. As per admin guide section 11.7 Clustering Central Management Servers below is recommended for new node:

>Install the same operating system, including the same version of operating system service packs and patches.

If you think yes and we add a new node(SLES15) with a different name than the existing obviously so can I move FS data from existing Server(SLES12) to this new node. Is not it the case that the node name should be same while moving FS.

Thanks,

Shubham

[denis_konovalov]

There are many ways to do it, you'll need to find one that you're comfortable using.
this assumes CMS DB is on a central server
1. Add new node to existing cluster on SLES 15 (SLES 15 SP2+ are not yet supported)
2. Stop old nodes, move FRS to new
3. add as many nodes as needed. no need to do anything with win node.

Or
build new env separately, migrate content to it using PMW, re-add win node.

Or combination of the 2.

Or - more risky approach - upgrade current nodes OS in-place.

[mamartins]

There is a tool to export all data/configuration from a BOBJ from an old system to a new one. Please check the documentation here: Upgrade Paths | SAP Help Portal.

One possible approach is (obviously needs to put to test, because each case is a different one):

1. Create a new BOBJ installation on SLES15
2. export the data from the old system and import on the new one
3. Test, test and test the new system
4. If OK, decomissioning the old nodes on SLES12
5. Add the extra nodes as required to the new cluster.