Failover CMS Datasources

[Former Member]

I would like to perform a failover test in my BOXI R3. Here is my situation:

Our production environment is BOXI R3 installed in windows server(Win A), its CMS datasource is in oracle in unix (Unix B). We have a DR site, we have already installed another BOXI R3 in another windows server(DR Win C) and its CMS is point to the oracle in DR unix (DR unix D). We are using tnsnames.ora to connect to oracle. Normally, the DR Win C and DR Unix D is down.

For fail over test, we need to test:

1. The production windows(Win A) down while the production unix(Unix B) is still alive. Then, the DR Win C is up manually and the tnsnames.ora in DR Win C is point to Unix B oracle.

After DR Win C is up and start the Tomcat & BO SIA server manually, I discover all the job server, destination server ...etc cannot start up. The host name of those job servers & destination servers is change to Win A so I guess the BO in DR Win C can connect to the oracle in Unix B. But I don't why the job servers and destination servers cannot start up.

Please kindly advise. Thank you in advanced.

I still have two other situation, that is

2. both Win A & Unix B fail over to DR Win C & DR Unix D

3. Only Unix B fail over to DR Unix D while Win A still up.

Please kindly advise if you have an reference. Many thanks.

[denis_konovalov · Accepted solution]

At least once you need to have A and C running at the same time, connected to same B DB.

This way the cluster is set, and you see 2 nodes in CMC. Node A and C.

In a normal situation, you will have node A running and node C not.

When A is down and B is still up, you simple bring node C up and you be up and running.

If both A and B are down, provided DB is replicated to D correctly , C will be up and serving requests.

When only B fail over to D, you'll just need to temporarily stop A while you change tnsnames.ora....

In all of this you forgot about FRS store.

Do A and C point to the same FRS location ?

How is FRS DR organized ?

[Former Member · Accepted solution]

Hi Dennis, thanks for you ans.

Currently, we copy the FRS store in Win A every night and replicate to DR Win C, and we also replicate the BO CMS & Audit database from Unix B to DR Unix D every night.

We have a question:

when we setup the DR Win C, DR Win C CMS is already connect to the oracle in DR Unix D, how can we change the datasource to Unix B? Using the "Specific CMS Datasource" in CCM? It is appreciate you could explain in details.

Or we need to connect to Unix B when we setup DR Win C? Then, how can we switch to DR Unix D when Unix B down?

Thank you in advanced.

[denis_konovalov · Accepted solution]

when we setup the DR Win C, DR Win C CMS is already connect to the oracle in DR Unix D, how can we change the datasource to Unix B? Using the "Specific CMS Datasource" in CCM? It is appreciate you could explain in details. 

Admin guide fro XI3 has details on how to connect to different data sources.

Basicaly, you need to create new SIA on C pointing it to B. Delete original SIA on C.

Or we need to connect to Unix B when we setup DR Win C? Then, how can we switch to DR Unix D when Unix B down?

you just point tnsnames.ora on C to D and sia on C will be able to connect to CMS DB .

You wil still see noda A in CMC, but allit's servers will be stopped.

Essentialy, you need to create a cluster with 2 nodes: A and C.

C will be disaster recovery node and not run when A is running.

[Former Member]

Hi Denis,

Glad to do that,. Where can I log the incident?

[denis_konovalov]

https://websmp107.sap-ag.de/support

[Former Member]

I discover when one of the CMS is down, the user need to logout and login again, otherwise the user cannot view the instance histories

[denis_konovalov]

That last part sounds like it needs proper investigation - can you please log a support Incident for it ?

[Former Member]

when I switch off the CMC of Win A, I discover the DR Win C cannot retrieve the instance history

[Former Member]

Hi all,

I setup everything and put the FRS in a shared path. Both Win A & DR Win C FRS point to that shared drive. Everything seems work fine. However, when I switch off the CMC of Win A, I discover the DR Win C cannot retrieve the instance history. Did anyone have the idea what is the problem? Suppose they shared the same FRS and DR Win C can retrieve the instance from the shared drive even Win A is down.

Thank you in advanced.