topic Re: Ignite-UX cloning to new hardware and LTU in Operating System - HP-UX

Ignite-UX cloning to new hardware and LTU

Denver Osborn — Thu, 18 Mar 2010 18:31:59 GMT

Has anyone run into this one before...

I've been told that if I plan to clone a system from an Ignite-UX archive the source and target node have to have the same OE LTU. For example, I can't legally recover from an archive where the O/S was installed with DCOE to a server with VSEOE. Uninstalling the software which will not be licensed on the target node would not suffice.

Thanks for the feedback.

-denver

Re: Ignite-UX cloning to new hardware and LTU

Tim Nelson — Thu, 18 Mar 2010 19:07:37 GMT

If you take an image if a DCOE install and copy it to another server, the other server needs to be licensed for DCOE.

If you did the other way around I do not think there would be an issue as you would then be paying for DCOE and only using VSOE features which are already included in DCOE..

Re: Ignite-UX cloning to new hardware and LTU

Patrick Wallek — Thu, 18 Mar 2010 19:28:11 GMT

From a strictly legal licensing perspective, this makes perfect sense. HP wants you to be licensed for the OS level you will be using on the "new" system.

None of the servers, or the OS, has any checks built in to verify your license, at least as far as I know, so this is on the "honor system."

If you were to do this in a DR situation, where the original system is completely hosed, then I feel fairly confident that no one would say much.