Skip to Content

Business Objects Enterprise Update from 4.0 SP08 to 4.2 SP05 contingency planning


We are planning to update our current business objects enterprise platform from BO 4.0 SP08 to BO 4.2 SP05 and creating a contigency plan for this.

As I understand it, the update process updates the binaries and the cms metadata database thus if needed to revert to earlier version for any reason, could run uninstall from the install media and ask database team to revert cms database to as was before software update activities commened.

As all schedules would be paused and users out of system before any update activity commenced, I don't believe the actual filestore would be updated in any way - is this the case?

We have backups of filestore and cms metadata database in addition to sever database but as contigency plan would be looking for quickest way to revert to as was if required.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Apr 23, 2018 at 03:52 PM

    Is your BO servers are physical or VM? If it is VM, you can request Infrastructure team to take snapshot, so in case of revert, they can easily restore the previous snapshot fo the VM, so you don't need to worry about the binariries of BO installs. Evwn for physicals also , you can request ghost image of the server.

    You can follow below link if you have to do it manually.

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 23, 2018 at 03:56 PM

    Thanks for update . One physical server which presented to us as 1 virtual servers.

    Am I right in thinking the filestore is untouched by the update process if no users logged in and all scheduled instances pause along with services other than ifrs/ofrs and cms stopped?

    Add comment
    10|10000 characters needed characters exceeded