Storage Software
cancel
Showing results for 
Search instead for 
Did you mean: 

Polyserve upgrade from 3.1 to 3.7 backout or plow ahead?

Tom Nieman
Occasional Advisor

Polyserve upgrade from 3.1 to 3.7 backout or plow ahead?

HP Services performed an upgrade from 3.1 to 3.7 but failed to reinstall SLES10r2 per HP advisory before the 3.7 bits. We currently have poor performance and inconsistancy of the data.

First Question: Can/should we backout the PServe upgrade?

Second Question: Can/should we re-image the OS and install PServe 3.7 over the top of a clean OS image? Would full blown customer image of SLES10r2 work, or must it be HP SLES10 image? etc.

Third Question: Does anyone have a project plan or checklist, etc. for any of the work mentioned above? At least something to use as a template?

Fourth Question: How can we preserve the luns and groups through any of the above work?

currently 2 node linux cluster fronting 4 XP24000's. will obviously scale to more cluster nodes... Should we get a new node and make it a migration node? etc. Any great ideas?

Additional Opinions?
God Bless America
1 REPLY
Emil Velez
Honored Contributor

Re: Polyserve upgrade from 3.1 to 3.7 backout or plow ahead?


if the systems are blades or proliant systems you want to use the HP Sles 10 software since that will have the drivers for FC cards and other fixes specfic to the hardware although it should work with the commercial sles image.

Version 3.7 of polyserve finally has dynamic volume recovery which allows you to recover your dynamic volumes (import your volume with data intact)