John D. Bonam Disaster Recovery Architecture Session # 2841

Transcription

1 John D. Bonam Disaster Recovery Architecture Session # 2841

2 LEARNING POINTS Understand the known Traditional approach to Backup Recovery of the BusinessObjects Environment Understand the need for Disaster Recovery and how Clustering can help in meeting the needs of Disaster Recovery in minutes and with very little Technical Knowledge

3 Disaster Recovery Requirements As with Insight, many companies require to have a disaster recovery process in place so that they are able to stand up the BusinessObjects environment with the least amount of loss in time and data. The application needs to be deployed in a different physical location than the current Production environment Disaster Recovery is used to restore acceptable levels of business operations in the event of an unplanned disruption (i.e. natural or man-made)

4 Traditional Backup and Recovery Taking a backup on the Production machine 1. From the Central Configuration Manager (CCM), stop the SIA 2. Take a backup of the CMS database 3. Take a copy of the entire FileStore Input and Output folders (by default, under product installation folder) 4. Restart the SIA Note: On BI 4.x you must know the cluster key at the time the backup was taken to be able to connect a CMS to the restored database.

5 Traditional Backup and Recovery Restoring the backup to the Test machine 5. From the CCM, stop the SIA 6. Rename the existing FileStore folder (e.g.: FileStore_Old) 7. Copy the FileStore backup taken in step 3 into the Test machine's installation folder 8. Restore the CMS database 9. Delete references to the original server as follows

6 Traditional Backup and Recovery Restoring the backup to the Test machine 10. From the CCM, select "Add Server Intelligent Agent" or "Add Node" When details are requested, use the name and port number of the existing Test SIA (SIA port number is 6410 by default). For XI 3.x, make sure to select "Create default servers on the new node" and "Recreate Server Intelligence Agent on the local host, if it already exists in the CMS system database" For BI 4.x, make sure to select "Recreate node"

7 Traditional Backup and Recovery Assign a port to the CMS (by default 6400) and select the restored CMS database of point 7. Enabling Auditing is optional at this stage and can be configured later On BI 4.0 it will now ask for the cluster key - this is required to decode information from the restored database content DO NOT START THE SIA YET 11. When the SIA is created, go to SIA > Properties > Configuration and modify the ClusterName of the restored environment to be different from the production environment 12. Start the SIA

8 Traditional Backup and Recovery With the Traditional approach, you can restore only up to your last backup of FRS and CMS Database. Even if you have replication enabled for your CMS Database and the FRS, you would still have to recreate the servers within a new SIA. This process could take hours, if you have created custom servers such as splitting of the Adaptive Processing Servers.

9 Insight Disaster Recovery Architecture

10 Insight DR explained The Disaster Recovery application servers are installed as nodes within the BusinessObjects Production application. The DR nodes should be configured exactly the way production nodes are configured The FRS, CMS Database and other Data sources are mirrored to the DR location

11 Insight DR explained In order to avoid duplicate clusters with same name conflict, we will do the following steps during DR configuration. Add the following to the Hosts file Prod Servers located at C:\Windows\System32\drivers\etc Prod Server Prod Server 2 Add the following to the Hosts file DR Servers located at C:\Windows\System32\drivers\etc DR server DR server 2 This will prevent accidental communication between the Prod Servers and the DR servers at a time when they are both turned on at the same time.

12 Steps during Disaster Recovery 1. Prerequisites: Before BO can be started, the following applications should be up and running in DR. SQL Server Databases at the DR location. SAP BW DR System: which also needs to authenticate for the same system as Production. Active Directory for Service Acct 2. Start SIA on the two BOE DR Servers 3. Start the Web server (Tomcat) 4. Once the Services have been started, you can validate the application by logging into the BI Launchpad.

13 KEY LEARNINGS By using the Clustered approach to Disaster Recovery, we were able greatly simplify the Disaster Recovery process. At the time of a disaster; We can get the DR environment up and running in a matter of minutes, by simply starting the DR SIA and Tomcat services. The process itself is so simple that it does not require only the BusinessObjects Admin to be available to start the application and validate. Anyone with access rights can simply start the services.

14 STAY INFORMED Follow the ASUGNews team: Tom Chris Craig

15 SESSION CODE 2841