BODS 4.2 Upgrade

[Former Member]

We have successfully upgraded our test system from BODS 3.2 to 4.2 and in the next two weeks, we'll be upgrading our production system.

The difference between the test and prod servers is that our production server is high availability server.

Are there any additional steps for the upgrade in the high availability server? Or it will be the same with how we do it in the test system?

Is there anything we have to do in the cluster level?

Thanks!

[chethan_lingaraju]

cluster installation will be little different from normal installation. Hope you tried cluster installation in your test server.

[Former Member]

Hi Chethan,

Would you site examples of the difference in the normal installation? We haven't tested the cluster installation in our test server as our test server isn't High availability server.

[chethan_lingaraju]

Hello Jerome,

Consider four servers, A, B, C, D

A & B -> CMS clusters

C & D -> Job servers

1. In A & B,
   • Configure ODBC for CMS & Audit DB. Same DB details in both server.
   • Install
     • IPS Package
     • Data services package - Console Component only
   • In server B installation, you will have to enter server A details which links them up.
2. In C & D, install Data services package excluding console component.

For production, if its virtual servers, risk-less way would be to install BODS on new server. Once the server is ready, migrate old repositories to new server. Decommission old servers.

[former_member224495]

Hi Chethan,

In this case if we register repository details or User details in one server CMC will reflect in another server CMC and vice versa.

And also we can use either one Console from both the servers to monitor/Execute the job.

Please correct me if I am wrong.

Thanks,

Sagar T

[chethan_lingaraju]

If you login to BODS from either of cluster server, both will look alike.