Cloning with Ignite-UX

[Sandeep.M.S]

Hello Members,

I have recently installed a client using cloning from Ignite Server. The recovery image of the source system was used for installing HPUX 11.31 OS on the target system using Ignite-UX (C.7.11.444). After installation of the client, we noticed that secondary swap on the target system had used a SAN disk and not the root disk that was mentioned at the time of installation. All other logical volumes including the primary swap on the target system has used space only from the root disk.

I also noticed that source system had two internal local disks from which the primary and secondary swap space were configured and whereas the target system had only one local disk. Since, the target system did not have another local disk, I suspect SAN disk might have been used for the secondary swap here . Please let me know if this is a known issue with this Ignite version and also let me know if this could have been controlled.

[Patrick Wallek]

Yes, you can control what disks are used.   When going through the Ignite/UX interface you can specify which disks are part of VG00.  You can also modify the logical volumes and add or remove, if necessary.

[Sandeep.M.S]

Thanks Patrick. I agree with you. Only one local disk was selected for vg00 during the installation. I'm not sure how the SAN disk was automatically choosen and added to vg00 during the installation.

[Patrick Wallek · Accepted solution]

One thing that I recommend, if you are installing to local disks and not SAN disks, is to unplug the fibre cables.  If the fibre is unplugged there is no chance of it picking up an incorrect disk.

[Sandeep.M.S]

Good Idea Patrick. We will disconnect the fibre cables before installing the OS. Also, please let me know if there is an option available in Ignite to disable SAN disks from being used during the installation.