Skip to Content

BusinessObjects Content recovery and Disaster recovery – BO XI 3.x

This is the continuation of my previous blog ‘Business Objects Administration- Backup and Recovery’ and this blog is all about BI content recovery and failover recovery.

Content recovery

Consider a situation where you accidentally deleted a folder with business critical reports inside it. Some of the approaches to recover the reports and the folder.

  1. Recover the contents from a BIAR backup
  2. Recover the contents from another system  (If you are in Prod. recover from QA)
  3. Restore CMS and FRS backup in a temporary server and use the Import Wizard to get the desired reports that are deleted.

Let us discuss each method one by one

1. Recover the contents from a BIAR backup

     Recovering contents from BIAR file is straight forward and you should have a appropriate .biar file in hand before restore. We will be using Import wizard to restore the contents.

2. Recover the contents from another system

   

     We can do the report migration from another environment. If you are in Production environment and you have deleted some reports, we can still recover the reports from QA server. Again we will be using Import wizard to restore the contents.

    We need to ensure that the reports in both environments are in sync and no change is made to reports in Production environment alone (Proper SDLC cycle).

3. Restore CMS and FRS backup in a temporary server

 

     Sometimes we may need to restore our Business Objects environment back to a given point in time but still keep the original system up and running.This will enable us to investigate and export selected BI content back to the original environment to avoid complete restore. We need to have temporary Business Objects environment setup, FRS and CMS database backups as prerequisites. The recovery sequence would be

·       

  • Restore the CMS database and FRS directories to a temporary database and temporary Filestore.
  • Log on to the restored CMS database and run the following

              Delete from CMS_INFOOBJECTS6 where ParentID=16 

                    (to delete any reference to original Business Objects environment )

  • In CCM stop the SIA and Go to Properties -> Configuration tab. Change the data source to point to the restored CMS database and change the cluster name to different to the cluster being restored.Change Cluster name for Input and Output repository servers to same as for CMS.
  • Start the SIA and use the Import Wizard to copy the deleted contents directly to the original environment.

Disaster recovery

    For disaster recovery we need to follow the approach which is similar to Approach-3 with some addition steps.

 

  • Restore the CMS database and FRS directories
  • Delete all the references to the original server in Disaster recovery CMS database as follows

              Delete from CMS_INFOOBJECTS6 where ObjectID= 4  (to delete cluster entries)

              Delete from CMS_INFOOBJECTS6 where ParentID=59  (to delete SIA entries)

              Delete from CMS_INFOOBJECTS6 where TypeID= 16    (to delete server entries)             

              Delete from CMS_INFOOBJECTS6 where TypeID= 17    (to delete server group entries)

              Delete from CMS_INFOOBJECTS6 where ParentID=16  (to delete any BO service if remaining)

 

  • In CCM select “Add Server Intelligent Agent”, Use the Name and Port number of existing SIA (default port-6410) and 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”

                                            /wp-content/uploads/2013/03/1_122013.jpg

  • Assign a port to the CMS (by default 6400) and select the restored CMS database.

                                            /wp-content/uploads/2013/03/2_122014.jpg

  • Once SIA is created, go to SIA > Properties > Configuration and modify the ClusterName of the restored environment to be different from the production environment and start the SIA

                                            /wp-content/uploads/2013/03/3_122015.jpg

 

  • To Delete the Old SIA (node), Go to the CCM
  • Create a new SIA, give the name of the SIA you want to delete and use a different port (i.e. 6411)
  • Select “Create no servers on the new node” and “Recreate Server Intelligent Agent on the local host if it is already exist in the CMS System database”

          /wp-content/uploads/2013/03/4_122016.jpg

  • The SIA running is the one coming up

        /wp-content/uploads/2013/03/5_122017.jpg

  • Provide the Username/password associated and finish the configuration

         /wp-content/uploads/2013/03/9_122055.jpg               

 

  • After few minutes the system get back to the CCM. Now delete the new SIA created using the Newly created running SIA credentials.

        /wp-content/uploads/2013/03/7_122028.jpg

        /wp-content/uploads/2013/03/8_122054.jpg

        The old SIA is completely removed and your Business Objects DR Server is ready to use now.

        Hope the blog is Interesting. Keep reading!

32 Comments
You must be Logged on to comment or reply to a post.
  • Manikandan,

      Could you please give me the link to the ‘Business Objects Administration- Backup and Recovery’ blog that you refer to in this blog. I could not find it.

    Thanks

    S.

  • Hi Mani,

    Could you please provide the similar DR steps at Linux environment?

    Much appreciate your help… Thank you…

    Best regards,

    Karthik

  • We need to do a DR and I have not done this before. We have servers in another location and I need to do the install to get the box up and running. Do I create a new schema in prod so that I can do the initial install or do I set the new server up as a part of the existing prod cluster?

    • For performing DR:

      No Need to change or create anything in existing BO PROD environment & PROD CMS DB.

      No Need to create new schema in PROD. ( Not suggested to do directly in PROD).

      Have a new CMS DB . Install BO in the new servers by using new CMS DB.

      Once installation completes, start performing ur  DR process.

      Let me know if you need any additional details.




    • Hi Danielle,

      DR Site will be a independent deployment which doesnt going to share/Utilize from the existing production deploymeny. This system will be used only when the Production goes out of action.

      For DR preparation you should have below in hand during DR process

      – Have a independent BusinessObjects deployment

      – Have a dedicated database schema

      – FRS folders backups from Production deployment

      – Backup of CMS database from production system

      Regards,

      Mani

  • Hi Mani,

    Thank you for sharing the information with us.

    I’m trying to restore couple of folders from the backed up CMS database and FRS repositories and Im stuck…:(

    In your third approach to restore, in the third point, you mentioned the cluser name in the SIA must be changed to the a different cluser and as well the same cluster should be for the Input & Output File repo’s as well…

    1. So, can I keep the cluster name of the test box which Im using to recover the missing foldrs?

    2. If it is needed to be a different cluster name, then when should it be changed in the I/O Repo’s? As I cannot login into CMC once I make changes to the SIA. Should I/O Repo’s be changed first and then CMS information in the sia?

    Please advise.

  • Hi Mani, great article on BusinessObjects Content recovery and Disaster recovery. Do you have a version of it for BO 4.1? Could you share it with us?

  • How will this process be different, if restoring to the same application Tier? e.g I have a web/application tier, and a data tier.  If my Application Tier is lost, but Data Tier is intact (CMS/Audit/FRS), Could I just reinstall Business Objects on the same server, using same SIA name as before, and use existing CMS DB? what process will change?

  • Manikandan,

    Thank you, this is the exact process we need to restore a folder full of reports (option #3).  The question I have is, if we delete the rows you suggest from CMS_INFOOBJECTS6, it removes the server entries from the CMC tab.  Yet your notes seem to imply that I should still see those, as I need to point the input and output FRS servers to the restored FRS copy.  And I am not able to add any new servers to the temporary node location, because my temporary SIA now points to the restored CMS database, which refers to the environment I am trying to pull content off of (from the backed up CMS/FRS).  Without these input/output frs servers, I don’t see how I can run the Import Wizard.  I am not hopeful of a response because this thread is very old, yet one would be so valuable to us and much appreciated!  Thank you.

  • Hi Manikandan,

    I am having an issue with the restore.

    My Environment

    OS : RHEL6

    BO : 4.1 – SP4

    DB : DB2

    1.I have cross-restored the DB from PRD to TST. (its an inplace restore and not as an extra DB)

    2.Restored the FRS-Folders from PRD on TST

    3.deleted the CMS_INFOOBJECTS7 where ParentID=16  … With and without this option: results are same

    4.Updated the data source settings. (If i dont execute this step, the system is not ready to start)

    After that i have tried out the following two options

    A. Created an extra temp SIA and CMS on different ports and started.

    B. Used the existing SIA and CMS

    Both these options are going against the same DB.

    But i still do not see the contents of PRD on TST.

    I definitely am missing something but i don’t know what. Hopefully you could give me any answers.

    Kind regards,

    Haroon