Skip to Content
avatar image
Former Member

BOXI R2 to BO 4.0 Migration

Hi All,

Currently i am working on BO migration project, as i am from EIM platform i have few queries in BO migration, anyone could please help me by clarifying the below queries.

The current version of system is BO XIR2, migrating to BO 4.0 version. For this we are using SAP provided Upgrade Management tool with BO 4.0. We have very less BO content (i.e. Universes, WebI & Crystal documents, Users, Folders, etc.). Apart this BO reporting content, we have some flat files (CSV) in three folders of around 65 GB. So we planned this migration in two phases, first to move all content excluding the three above said folders which contains flat files. Second we are planning to move all the CSV files by incremental model (5 or 10 GB at a time). This about the all what we are planning to migrate to new BO 4.0 Dev system from current BO XIR2 Production system.

Here i have few queries about the migration process and upgrade management tool:

1. In order to migrate the whole BO XI R2 reporting content from Production to BO 4.0 Development system, is it mandatory to take the downtime of BO XI R2 Production system? (As per the best practices, it is better to take the downtime, in order avoid any changes in repository during migration)

2. Is it mandatory to take the downtime to move the CSV files from BO XIR2 Production to BO 4.0 (as these files are not accessible by anyone at any time, we are using those three BO folders to store the files purpose only)

3. During Live-to-Live migration, is Upgrade Management / Import Wizard tool locks both the source and target BO system?

4. Do we have any size limitations to migrate in Upgrade Management / Import Wizard Tools (e.g. at a time max only 10 GB data will migrate)?

Could anyone please help me out here!

Thanks & Regards,

Ramakrishna Kamurthy

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Nov 24, 2011 at 01:08 PM


    please find some answers below.

    1. A Downtime would be better. Otherwise you could create a "code freeze" time. That f.e. starting on Date X the Rel.2 System is Read Only. If the Users have only read Access during the process of the Migration with the UMT nothing should happen.

    You could apply this by setting all Groups to the "View" right on Folder and Universe Level

    2. Also a Downtime would be good here. But i think if the Files are only getting accessed by Read operations, you can copy them to the new Server. Only copying should work. Moving not cause they are possibly locked by some of the Rel.2 Services like WebI and CR

    3. Not as far as i know. This wasnt the case in XI 3.1 with the IW. Until now i didnt heared that they changed that for the UMT

    4. If you say that your Objects in the Rel.2 are not that much i dont think you get into trouble. The huge part of 65 GB are the .CSV Files and you dont migrate them because they are the Datasource and somwhere on that Rel.2 Server or on a remote location

    ...Or did i get this wrong and you uploaded those .CSV files into InfoView? Than the UMT will take them aswell.

    Hope this helps.



    Add comment
    10|10000 characters needed characters exceeded