Doing a Full install from BI 4.0.6+ to BI 4.1.6 and Retaining FULL content & Settings

Major Benefits:

  • Save an average of 5-8Gig per SP/FP applied to your original install
  • Installing NEW features of BI 4.1.6 with any corruption to your BI4 install
  • Consistent built of all DLL and library files, no mixed versions of DLL’s
  • Opportunity to cleaning up OS build and optimize base server Pre BI 4.1.6
  • Upgrade from Windows 200x to 2012 with FULL content retention
  • Move your install from Drive C: long name to any Drive with shorter path
    • D:\SAP BusinessObjects\
  • NO need for Promotion Manager to move any objects
  • NO need to re-configure any BI4 Server, all settings fully retained
  • No Size &/or Objects limit for FRS restore (restored up to 50Gig)

High-Level Steps:

  • The CMS database MUST be the correct version prior to connecting to BI 4.1.6
  • Do complete back-up of existing BI 4.0.6+ Server, including
    • CMS and Audit database
    • BOBJ Administrator password should be complicated
    • Reset / Validate Cluster Key password
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
    • Any other special customization done
    • Originally running on Windows 2003 Ent 64bit
  • Upgrade the current BI 4.0.6+ environment to BI 4.1.6
  • Upgrade any additional options being used such as:
    • BI 4.1.6 Explorer
    • Analysis 1.4 w/ SP13 BIP Add-In
    • Design Studio v1.5 Add-In
    • Lumira v1.0.27 BIP Add-In
  • All other options should be installed after BI 4.1.6 Cluster has been reinitialized

post_01.PNG

Our Restore Example:

Server Name:          PS01

CMS Name:             PS01

Administrator:         <Confirm password is complex>

Cluster Key:            Confirmed password

CMS_DB:                XI4_CMS (MS SQL Server 2012)

Audit_DB:               XI4_AUDIT (MS SQL Server 2012)

ORG BI4 ver:           BI 4.0 w/ SP2

  • Upgraded to BI 4.0 w/SP4
  • Upgraded to BI 4.0 w/SP6
  • Upgraded to BI 4.1
  • Upgraded to BI 4.1 Patch 02
  • Upgraded to BI 4.1 w/SP4
  • Upgraded to BI 4.1 w/SP6

New Windows 2012 RC2 64bit Install

FACT: You will save disk space when doing NEW full install

  • Using real world experience from supporting 50+ BI 4.x installs. With every patch upgrade BI4 Platform install directory increases in size.
  • The current clean-up processes after a patch is very poor, older files are NOT removed.
  • Clean move from Windows 2003/2008 to Windows 2012 with full retention
  • In install example, customer started with NEW Bi 4.0 w/SP2 install
    • Upgraded to BI 4.0 w/SP4 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.0 w/SP6 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 Patch 02 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 w/SP4 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 w/SP6 (Added ~ 7Gigs of overhead)
    • Approx. added 40+ Gigs of overhead to your install

FACT: Move from Windows 200x to 2012 with full retention

This is an excellent opportunity to move your BI 4.1.6 install from Windows 200x to Window 2012 as long as the server name stay the same.

FACT: Repointing a newer BI 4.1.6 to an older Repository BI 4.xx is NOT valid

Starting with BI 4.x the CMS database now has full version signature.  You can’t take an older BI 4.0.6 CMS database and connect it to a BI 4.1.6 install, this will corrupt you install.


post_02.PNG

post_03.PNG


Step 1: Back-up Current BI 4.0.6 Environment

Complete Back-Up Process includes:

  • BOBJ Servers Image back-up by IT
  • CMS and Audit database
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
  • Any other special customization done

Step 2: In-Place Upgrade to BI 4.1 W/SP6

In-Place Upgrade involves:

  • NOTE: Confirm Administrator password is complex; otherwise you will have issues with SIA when doing FULL Install.  See NOTE – 2188271
  • We need to upgrade the current BI 4.x install to BI 4.1.6 in order to have the CMS database updated. 
    • Upgrade all the CMS Server in parallel
    • Next upgrade ALL the Applications servers within the cluster

post_04.PNG

post_05.PNG

Update – SAP Explorer to BI 4.1 w/ SP6 (Optional if installed)

Update – Analysis Add-On for BIP ver 1.4 w/ SP13 (Optional if installed)

Update – Design Studio 1.5 for BIP Add-On (Optional if installed)


Update – LUMIRA BI Platform add-on ver 1.27 (Optional if installed)


Step 3: Back-up In-Place Upgraded BI 4.1.6 Environment

Complete Back-Up Process includes:

  • BOBJ Servers Image back-up by IT
  • CMS and Audit database
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
  • Any other special customization done
  • Take NOTE of:
    • System DNS named and configuration
    • 64-bit Database drivers
    • Any other 3rd party software configuration
  • We will need the BI 4.1.6 signature upgraded CMS database & FRS as a SET to attached to NEW install.

Step 4: Doing NEW FULL-Build Install of BI 4.1 w/SP6

  • Get IT to do NEW installed Windows 2012 RC2 Server with same name as previous BOBJ server, in our example its “PS01”.  If running a BI4 Cluster, you will need IT do NEW installs of Windows 2012 with same name as previous server (SERVER_xx).

post_01.PNG

  • Install 64-ODBC Drivers required and configure properly. In our example it 64-bit MS SQL 2012 Native Client / Admin tool.
  • Configure the System ODBC-64bit with same names as original BOBJ server.  In our example XI4_CMS / XI4_AUDIT
  • Integrate other options, such as:
    • Joint NT Domain controller using proper NT Service Account
    • Integrate SAN / NAS as required
    • Install SUN JRE / JRK as required, set-up proper parameters
    • Install HTTP / JAVA Application as required
    • Install latest Windows Security updates, including .NET 4.5
    • Other miscellaneous application &/or configuration
  • Have IT take fully IMAGE / SNAPSHOT of system prior starting BI 4.1.6 NEW Install. Taking a full back-up of the NT Server PRE_BOBJ will come in handy in the future.

Install BI 4.1.6 w/SP6 NEW install

post_14.PNG

post_16.PNG

/wp-content/uploads/2015/09/post_17_784393.png

post_18.PNG

post_21.PNG

post_22.PNG

post_23.PNG

post_24.PNG

post_25.PNG

post_27.PNG

Install BI 4.1.6 w/SP6 Explorer Add-On (Optional):


Install Analysis 1.4 w/SP13 – Add-On for BIP (Optional):

Install Design Studio 1.5 w/SP00 – Add-On for BIP (Optional):

Install Lumira Server v 1.0.27 for BIP (Optional):

Validate NEW BI 4.1.6 CLUSTER Install with SAME Add-On’s

post_38.PNG

post_39.PNG

For a BI 4.1.6 Cluster, continue install of other servers

  • Install other CMS Servers within Cluster
  • Next install all other Application servers within Cluster
  • NEW base BI 4.1.6 Cluster is fully ready and on-line

Step 5: Doing Server Restore of ORIGINAL System:

Complete Restore Process includes:

  • STOP Tomcat & SIA
  • Restore CMS Database and Audit Database
    • In our sample it’s XI4_CMS & XI4_AUDIT
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
    • Any other special customization done

Server Restore Process Step-by-Step:

post_40.PNG

post_41.PNG

post_42.PNG

post_44.PNG

post_47.PNG

post_48.PNG

post_50.PNG

post_52.PNG

post_53.PNG

post_54.PNG

post_56.PNG

For more details on FULL restore, please refer to SCN post

How to Restore BI4 from FRS & CMS Backup

  • Continue installing any NEW add-on options as required to fully working cluster
To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Aaron Benner

    Very interesting article.  Can you comment on the potential to reclaim space even if you did not need to upgrade –

    eg if you are at Bo 4.1 SP5 patch 5 and wish to recover space wasted by several upgrades in the past, could you simplify the process by just fully reinstalling directly SP5patch 5 and importing settings?

    Aaron

    (0) 
    1. Ajay Gupta Post author

      Aaron,

           You can do this with any build, if you follow the above process.  You would do same process of taking the back-up of CMS with current BI 4.1 w/ SP5 + Patch 5.  Then doing a NEW install as suggest above of Windows2008 and then do a fresh install of BI 4.1/SP5 plus Patch 05.

      Ajay

      (0) 
  2. Gavin Lange

    AMAZING article,

        This has saved me well over 50Gigs per server.   This is something that SAP Support should be aware of.  I don’t think anyone at SAP Support know how to this.   They tell me do new install and migrate content, that’s NOT realist solution !!

    The best feature is that will help all those companies running Windows 2003, which ends support Dec 31st 2015 and fully retail all your content

    Keep up the GREAT Work !!.   Hope to see you at SAPPHIRE

    GL

    (0) 
  3. Syed Peerzade

    Hi Guys

    Can we replicate BI on a lower environment from production, say quality? If yes, then does the hardware has to be similar?

    My concern is we want to bring our entire production content to Quality and then update the quality system from BI4.1 SP5 to BI4.2 Sp3, since in Qa the there is one CMS and one tomcat servers and in Prd we have two CMS and two tomcat servers, is this possible? If not, what is the best way to do this?

    Thanks

    Syed

     

    (0) 

Leave a Reply