BusinessObjects Administration – File Repository Capacity planning

This is the continuation of my previous blogs BusinessObjects File repository servers here.

Business Objects Administration – File Repository Servers

BusinessObjects Administration – File repository store capacity planning Considerations

Let us see the capacity planning process for FRS step by step

Capacity planning for Input FRS

Below factors need to be considered for Input FRS disk space requirement

     A. Number of Users

     B. Number of reports per user’s personal folder (Favorites & Inbox)

     C. Average Report Size in User’s personal folders (MB)

     D. Number of Report Templates  in public folders

     E. Average Report Size in public folders (MB)

     F. Number of Universes

     G. Average Size of the universe (MB)

Considering all the factors above we can estimate the Input FRS space requirement as below

  And the final Input FRS server sizing would be

        IFRS size =  [ A * B * C ]  +  [ D * E ]  + [ F * G ]    in MB

Capacity planning for output FRS

Below elements needs to be considered for output FRS disk space requirement

          H. Total Number of Scheduled Reports 

          I.  Number of report instances created in a month                                

          J. Average Scheduled Report Size       

We can estimate the output FRS space requirement as below

And the final output FRS server sizing would be

        OFRS size =  = [ J ]  * [H + ( I * 6 )]   in MB      * 6 is used for counting instances created in six months of duration

Note :

     –  The Capacity planning process is specific to a simple BusinessObjects environment with the existance of reports like Crystal and WebI. You may need to add/incorporate certain parameters if you are using tools like Explorer etc. so as to accomadate the space required for them.

     – I have Considered only reports and Universes in capacity planning. You may required to add if you have something.

Hope you find this Blog is interesting.  Thanks for reading.