[locky]

Here is my problem: there 3 AIX 5300-07 clients on my VIO server 1.4.1.1. After updated to ioslevel 1.5.1.1 my VIO server crashed. Unfortunately I don't have a backup. I install VIO server again with existing profile from HMC. is it any way let me remap all 3 AIX clients under local disk1 (disk0 is VIO server).
Thanks

[ross.mather]

What are you trying to do? remap a volume group that was on hdisk1 to the VIO clients?

If so import the volume group and relink the lvs to the clients.

If not can you clarify what you are trying to do?

[locky]

Thanks Ross,
VIO server is created on local disk#0, 3 AIX clients are created on hdisk#1.
Like I said, my VIO server was crashed, so I have to reinstall from scratch. I knew that on hdisk#1 still keeps the LVs of 3 AIX clients. My question is how I can get these info and redo mapping to the LVs so I can connect back these clients again.
thanks

[ross.mather]

The data should still be on the 2nd hard disk so you can:

importvg datavg hdisk2

Then you'll need to reconnect the appropriate disks to the correct LPAR in order to get them working again.

And when it does - start making backups :-)

[cdelgadop]

Hi

As Ross said you need to importvg from hdisk1 so VIOS ODM gets updated with Logical Volumes that actually are your Virtual clients images.

Your LPAR profile have the SCSI Virtual Server adapters you have assigned to each client and you can draw those connections with the Virtual SCSI client slots in the LPAR profiles of each client. Next you can use the lsdev command in VIOS to check for each of those Virtual SCSI adapters.

If you issue the lsmap command at VIOS you should see all those Virtual SCSI adapter without any link to a Logical Volume or disk. All those vhost adapters have an address and that address is the link between the server and the client. Then you can use the mkvdev command to link Logical Volumes with a vhost and it should work.

Did you only configure LV to serve as root Voluem Groups for your clients ?? or data VG as well ??

Hope this helps

[locky]

Thanks all for helping me. But I don't know exactly VG and LVs name which were created? how do I find out these info on the second disk?

[ross.mather]

When you import the vg the logicalvlume names are available - unless you import a VG where the Logical volume names are already in use - unlikely in this situation unless you import another rootvg.

If you want a different volume group name then exportvg it and importvg it again to get a different name - its a reference not a binding requirement.


Please reading the varyonvg, importvg and exportvg manual pages on a regular AIX partition before you do this to avoid potential errors.

[cdelgadop]

Hi

I wouldn't care about names of the VG. Name it whatever you want. What's really important is that you can actually importvg the VG from disk.

You can go to an AIX pure session by running:

oem_setup_enviroment

and use the lquerypv command (man lquerypv) in order to check what's inside that disk.

[locky]

Got these when tried to import:
$ importvg -vg rootvg_clients hdisk1
************************************************** *****************************
The command's response was not recognized. This may or may not indicate a probl
em.
************************************************** *****************************
importvg: Unable to import volume group from hdisk1.

[locky]

I don't know why but after reboot VIO server, I was able to importvg from hdisk1, and saw all LVs created:
# lsvg -l vg00
vg00:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
rootvg_aix01 jfs 320 320 1 closed/syncd N/A
rootvg_aix02 jfs 320 320 1 closed/syncd N/A
rootvg_aix03 jfs 320 320 1 closed/syncd N/A

So the next step that will link these to Vhosts?
thanks