cancel
Showing results for 
Search instead for 
Did you mean: 

BusinessObjects not working after vMotion event

keithfisherdsc
Participant
0 Kudos
271

Hi all,

We have a SAP BusinessObjects 4.2 SP6 single server implementation that runs on VMware server. Every time vMotion is used to move the server to a new host, the system becomes unstable and needs to be restarted. It appears to be losing connection to the database, and recording transport errors.

Looking about for help I cannot see anyone else reporting such problems, has anyone experienced the same thing or can anyone suggest where we start troubleshooting?

thanks

Keith

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member198540
Participant
0 Kudos

try to do a vmotion but with sap bi stoped firts.

denis_konovalov
Active Contributor
0 Kudos

Sounds like you need to review what exactly vMotion does and how it affects BOBJ.
Looks like its not transparent.

keithfisherdsc
Participant
0 Kudos

Thanks for the reply Denis - vMotion is VMware's way of moving servers around hosts without affecting services to the end user, only in BOBJ's case it does affect those services. Anecdotally the move process seems to affect the connectivity to the CMS database, but instead of entering a waiting phase until connectivity is restored BOBJ cannot auto-recover from a momentary lapse.

I was wondering if anyone else had experienced the same thing as the technology is probably widely used.

Are you aware of any documentation about best-practices for BOBJ in a virtual environment - I found a white-paper from 2013 but the technology has moved on somewhat since then.

We'll be testing vMotion and BOBJ in dev environments to see if we can get more information on what exactly happens.

thanks

Keith

denis_konovalov
Active Contributor
0 Kudos

I'm not aware of any new docs on the virtual deployments.
And not aware of any issues in Vmware deployments for BOBJ like you describe. If BOBJ is losing connectivity to CMS DB during this process, then the process is not working correctly or the lapse is not momentary.

What happens here is probably what is described in KBA https://launchpad.support.sap.com/#/notes/2823760
And in these threads : https://answers.sap.com/questions/5829228/having-a-problem-with-netweaver-systems-on-vmware.html
https://answers.sap.com/questions/8710713/vmotion-impact-on-a-running-sap-instance.html