Moving disk images from SCSI to SAS controllers.

[Adrian Clint]

Or moving from last generation of blades to next.... can I migrate an image or would it be best to run a new scripted install.

Specifically I mean taking an image that used to be deployed on say a BL20P G3 6i Controller based blade with SCSI drives and then deploying this same image on a BL20P G4 e200i Controller with SAS drives?

When moving from 5i to 6i controllers I know the process was to run the install for the 6i drivers then apply a reg key so that it now booted from the 6i controller.

Anyone know if the process to go to the e200i array controller is similar?

Are the array configurations files compatible?

I'm assuming that I have to also install the drivers for Chipset, NICs etc.

[Adrian Clint]

Might be able to answer part of my question myself.

From the e200 quickspecs - regarding compatability ....

Features:
All Smart Array products share a common set of configuration, management and diagnostic tools, including Array Configuration Utility (ACU), Array Diagnostic Utility (ADU), and Systems Insight Manager. This software consistency of tools reduces the cost of training for each successive generation of product and takes much of the guesswork out of troubleshooting field problems.

So hopefully an array config file for a 6i should do the same thing when deployed to a e200i.

[Steven Clementi]

Adrian:

"can I migrate an image or would it be best to run a new scripted install."

If the hardware is different, then it might be easier to deploy a new scrpited install.. otherwise... just an updated image might do. Deploy the image to an older model, update drivers and registry entries and whatever else is needed, grab new image. I don't think you can modify the image directly.

You will need to make sure the image contains the proper registry entries for all the Smart Array's that you will use, as well as proper drivers.

For instance, moving from a DL380 G3 to a G4 was easy. On the G3 system, you load the 6i registry key, update your drivers and the disk/image would boot on a G4. (as you stated)

The same should be true for SCSI to SAS conversions. You may need to build a box first, then extract the correct registry key(s) in order to import them... or maybe someone has done it already and will post.

The only major change you might need to make is to your Array config file. That is, or should be, easy too. Just do a manual config and grab it with RDP to a new file.


Steven

[Edward Latzko_1]

Try using the new HP Proliant Essentials server Migration Pack - Physical to Proliant Edition (you must purchase a license. Here is a link that explains what it does. http://h18013.www1.hp.com/products/servers/proliantessentials/valuepack/migrate/index.html

ope it helps.....

[Edward Latzko_1]

Try using the new HP Proliant Essentials server Migration Pack - Physical to Proliant Edition (you must purchase a license. Here is a link that explains what it does. http://h18013.www1.hp.com/products/servers/proliantessentials/valuepack/migrate/index.html

Hope it helps.....