DI JOb Server on virtual Environment

Hi,

We currently have the BODI 11.5 Job server running a physical machine. We are planning to P2V this machine (Physical to Virtual) using VMWare. And the virtual image will be hosted on a new hardware. I know DI Job server is node locked. But I have a few questions here.

  1. Will the same job server work on the new virtaul environment? If not, should I need to rehost the license?

  2. Even If I rehost my JOb Server license can I use the new license on the Virtual Environment?

  3. Rehosting of license means re configuring the job server. correct?

Please let me know any other complications of this scenario?

Thanks
raj


Raj_Konig :india: (BOB member since 2007-07-19)

You will need to make your MAC address static as the licensing is based on the physical host ID. I know in VMware, if you use vmotion, the MAC is usually dynamic. We have not seen any performance issues.

Chris


cfachris :us: (BOB member since 2003-09-03)

Thanks for the quick response chris. So rehosting of license worked?

Do you need to re-configure the Job Server again or just rehositng of the license had the Job Server defaulted to old configuration?

thanks
raj


Raj_Konig :india: (BOB member since 2007-07-19)

We just made sure the old server was off, and then brought up the new server with the static MAC address. These worked without reconfiguring anything for our development boxes. You may want to get a new license key if you are significantly updating the OS (which we did with production) and you need a new hostid with it. But we don’t have issues if Ops needs to move the server to a new physical host since the hostid that the license key expects does not change.

Our Ops guys were more involved with the specific technical details, so unfortunately I would not be the best source for those.

Chris


cfachris :us: (BOB member since 2003-09-03)

BTW, we found VMware performance to be pretty poor on very intensive ETL jobs. And it would clobber other virtual guests on the same underlying physical server. Maybe it was a tuning problem with the VMware stack… But personally I’d never use this in production. Dev/test only…


dnewton :us: (BOB member since 2004-01-30)