BOBJ DR Plan for Distributed Environment with Windows and MS SQL Server

[Former Member]

Hi Experts ,

We are going for BOBJ DR Setup for one of our Client and we have 2 APP Server and One database and we would like keep DR server for this with One database with One Apps , Please provide me the detaild Plan with documentation and i have already go through the link

Thanks

Kiran.GVL

[former_member185603]

You mean 2 app servers means 2 BO servers right?

Follow the same link you reviewed, you should be good.

if your DR server has same name as Production server and isolated to dedicated network which will not interfer with production network, than you should be good.

Otherwise, Check this KB.

1842055 - How to setup a disaster recovery environment using production backup on BI4 platform ?

[Former Member]

Hi Jawahar ,

I have already check it and it is saying note not released and i need the good plan to present to the client.

Thanks

Kiran.GVL

[former_member185603]

We need to get more details as i mentioned in my earlier post.

Does the DR server has same name as production server?

Does the DR server is in isloated network?

Is your CMS DB copy of the production CMS DB?

[Former Member]

Hi Jawahar ,

Does the DR server has same name as production server? No

Does the DR server is in isloated network? Yes

Is your CMS DB copy of the production CMS DB? not yet copied we will do before we proceed with Setup.

Thanks

Kiran.GVL

[former_member185603]

Follow these steps:

Preferably, Shut down all production Server intelligence agent or SIA Nodes in the Production cluster before doing this operation (yes this is best done over production down time) -- OR --
Alternatively, on the Sandbox server, Change the etc "hosts" file to ensure that the production host and FQDN are mapped to the Sandbox IP Address.
127.0.0.1 localhost
<SANDBOX_IP> <production hostname> <production fully qualified domain name or FQDN>
<SANDBOX_IP> <sandbox hostname> <sandbox FQDN>
NOTE: This way Sandbox thinks it is production when connecting by host or fqdn as it maps back to sandbox IP.
This is to ensure that the sandbox doesnt get crosswired into production cluster using the running Central management server (CMS) on the production server.
(because the Sandbox SIA can get the IP & connect details for production from within the restored CMS database backup)
2. Using Central configuration manager or CCM - add a SIA node with SAME Node name as one that already exists in the production CMS Database (use temporary cms)
- This may fail in first attempt as cms wont connect - but it will leave an orphan CMS server
- (Optional) Without killing the orphan Central management server or CMS, try to recreate the same SIA with running cms on this server
- This time it works and creates the node.
3. Using CCM, Change the cluster name eg: DisasterRecovery
4. Optionally Validate your Production Integrity - (if your production environment has been running all along) - Validate the integrity of your production BI4 repository by checking the CMC > Settings
a. check Database connection and
b. Cluster Information
NOTE: This is to ensure that everything is still valid on your production system and no unnecessary cross-communication has occurred with sandbox.
5. The current SIA may not start or work properly. So create a new Node on the sandbox (name it more relevant to sandbox cluster) with default options using temporary cms . (kill any orphan cms processes before running this). A new node and SIA should get created.
6. Restore the Filestore location in Sandbox server to the backup from production by copying the File repository folders from a backup or by mapping to a backup of the same.
[Note: Do not use the same File repository that production is "currently" using]
7. Start the newly created DisasterRecovery Node and local Apache Tomcat Application server and ensure that CMS and rest of default processes are started.
8. Using the CCM, Delete the older Production specific node using directions from Kbase 1339944 as this node may not be needed anymore,as well as it prevents any further cross-wiring or corruption with Production environment.

9. Login to CMC on the local Tomcat server and ensure that Input and Output File Repository Servers are pointing to the correct Filestore
folders (i.e. the backup from production)
10. Stop the DisasterRecovery SIA and local Apache Tomcat Application Server
a. Change etc "hosts" file to remove any production specific entries (essentially undo changes from step 1).
b. Delete the .businessobjects folder which contains clusterinfo.1400.properties file which will have corrupt entries treating the sandbox
node as part of Production cluster. This folder is located in the current user HOME folder
Example: "C:\Documents and Settings\<userid>\" Note: you may need to enable to view hidden or system/OS files to see this folder.
c. Restart the SIA and Tomcat server
11. Validate the Sandbox system Integrity - On a fresh browser session, validate the integrity of your SANDBOX environment by checking the
Sandbox CMC > Settings
a. check Database connection and
1842055 - How to setup a disaster recovery environment using production backup on BI4 platform ?
Version 2 Validity: 03.04.2013 - active Language English
b. Cluster Information
c. Ensure that they still have production specific information and valid
Your Disaster Recovery (DR) environment is now ready with production backup data (objects) on the Sandbox server running parallel to your existing production environment.