4.1 to 4.2 upgrade - moving to new servers

[Former Member]

We have a 2 node Business Objects system running 4.1 SP7. The servers are Windows Server 2008 R2. We need to upgrade the OS to Windows Server 2012, and we would like to upgrade BO to 4.2 SP03 at the same time. We were planning on setting up new servers with the newer OS and BO 4.2, then using the Upgrade Migration Tool (UMT) to move all data to the new servers. We used this process when going from 3.1 to 4.1, but it appears this won't work when going from 4.1 to 4.2. When we tried using the UMT on our Test systems, it failed and gave us this message – "Version check failed. The source system or source BIAR file must be of an older version. The destination system must be of the current version. (UMT 20012)."

Research reveals that the UMT is happy to move data from a 3.x to 4.x system, but not 4.x to 4.x. I see that we can use an option to turn off the version check in the UMT. The switch is “-internal_use_only_noversioncheck”. But I see people saying this option has been removed from 4.2 (plus they say, "use at your own risk"). So my ultimate question is, what is the right way to move to new servers?

One idea we've tossed around is to setup our new 2012 servers with the same version we are currently running (4.1 SP7). Then use the UMT (with the "no version check" option turned on) to move the data to the new servers. Then upgrade the BOE application to 4.2 SP03 at the end.

Anyone have some good advice for us in this scenario?

[Former Member]

We are now looking at the possibility of setting up the new servers with the same version of BO that we are currently live with, and then using the Central Configuration Manager to "copy" the data from the current production server to the new servers. The steps in the Admin guide look like this:

1. Open the Central Configuration Manager (CCM) and stop the Server Intelligence Agent (SIA).

2. Right-click the SIA and choose Properties.

3. Click the Configuration tab, and then click Specify.

4. Choose Copy, then click OK.

5. Select the database type for the source CMS database, and then specify its database information (including host name, user name, and password).

6. Select the database type for the destination CMS database, and then specify its database information (including host name, user name, and password).

It's interesting that nobody has suggested this option. Is there any reason that this isn't a good idea?

[denis_konovalov]

that's because this option only works when cloning CMS DB between 2 identical versions of the BOE.

and since your goal is to upgrade to 4.2 as well - other choices should be better.

[denis_konovalov · Accepted solution]

UMT is not designed to move content between same version 4.1 and 4.2 is a same version tree.
Using UMT is a very bad idea in your scenario.

Your options are - install 4.2 on win12 servers, then use CLI command line to move content from 4.1 servers.
(this assumes, you're changing CMS DB as well).
If you're keeping CMS DB then you should install same 4.1 version as current servers on new boxes, pointing that install to the same CMS DB (clustering them in) then removing original nodes. then upgrade new servers to 4.2

[Former Member · Accepted solution]

Since we are not keeping the same CMS DB, then we would need to go with the first option you describe. I guess it's time to learn about "CLI command line". I think I've seen something about that, but I've never studied it.

[denis_konovalov · Accepted solution]

its fairly easy and fairly reliable too.
Details are in the Admin guide and also in this KBA

https://launchpad.support.sap.com/#/notes/1969259

[Former Member]

The functionality was removed from 4.2. See here: https://ideas.sap.com/D32956

[former_member587449]

Alternatively:

How to disable version check in Upgrade Management Tool

http://bukhantsov.org/2016/05/how-to-disable-version-check-in-upgrade-management-tool/

[former_member185603]

Always make sure the servers in the cluster has same OS versions.

Since this thread is already closed, it is better to start new thread.

[former_member418791]

I am planning to upgrade to BI 4.2 with same CMS DB as BI 4.1,I have seen below suggestions in your comments.Can you please elaborate on this.That will be helpful.

1) If you're keeping CMS DB then you should install same 4.1 version as current servers on new boxes, pointing that install to the same CMS DB (clustering them in) then removing original nodes. then upgrade new servers to 4.2

or

2)

1. Suppose A and B servers are windows 2008. C and D are windows 2012

2. Install same version 4.1 SP7 on C and D, make it a part of cluster of A and B (use same CMS DB, IFR, OFR, audit DB etc, have C or D as a CMS and later as a normal processing node)

3. Remove the nodes A and B from the cluster.

4. Upgrade C and D to New BI4.2

Thanks

[CdnConnection]

Greg,

Here is another interesting document that may help. It explains step-by-step how to upgrade you BI4 server and fully retain your content. I wrote this atricle to help users move from Win2003 to Win2008/2012 and fully retain your content.

https://blogs.sap.com/2015/09/06/doing-a-full-install-from-bi-406-to-bi-416-and-retaining-full-conte...

Regards,

Ajay

[former_member190982]

Hi Greg,

You can install 4.2 SP03 on windows server 2012 and then migrate contents from 4.1 Sp07 to 4.2 SP03 using Promotion managment(if there are less that 1000 objects) or use CLI to migrate contents as Dennis said.

Regards,

RVS

[Former Member]

We have a lot more than 1000 objects - so it sounds like CLI is what is being recommended.

[former_member185603]

4.2 Promotion management much improved. You can still use GUI based. Assuming there is no timeout issues. In that case use CLI

[former_member316829]

Hi Greg,

I took the below steps in a similar case:

1. Suppose A and B servers are windows 2008. C and D are windows 2012

2. Install same version 4.1 SP7 on C and D, make it a part of cluster of A and B (use same CMS DB, IFR, OFR, audit DB etc, have C or D as a CMS and later as a normal processing node)

3. Remove the nodes A and B from the cluster.

4. Upgrade C and D to New BI4.2

Also make sure you take appropriate Backup of the CMS DB, IFR, OFR etc before the activity. Thanks

[Former Member]

Since we need to also upgrade our CMS DB Server, this does not accomplish that part.

[former_member472687]

So this is basically the approach we are taking. In my case, I am also dealing with an installation where FRS and CMS DB are placed on one of the Clustered servers...which just about nullifies one of the reasons for the Cluster.

So here is the method we are taking. Updating the current setup (4.1 SP6) to SP9. We will then be migrating the CMS and Audit DB's to their own SQL Server...then migrating the Input and Output FRS to their own dedicated SAN Storage. The migration of the DB's takes us to the 2012 R2 server (unfortunately Windows 2016 was not ready with our group). SP9 also allows us to use 2016 SQL Server. We then will add (2) 2012 R2 Servers to the Cluster by installing 4.1 SP9. Once done we will turn off the 2008 Servers....Then we are open to upgrade to 4.2..

So I think the answer may be to update first to SP 9 which will handle the Server OS and SQL Server you want to run...then adding the new servers to the cluster, etc.

I do however have one question to the community...when going from 4.1 SP9 to 4.2 SP4...do I need to run the Upgrade files or the Install files?