« Snapshots Make File Recovery a Snap | Main | A Smart Admin's NIM »

December 02, 2008


Thanks again Rob. Always useful stuff here!

I had a need today to migrate an LPAR from AIX 5.3 to 6.1. My NIM server was at 5.3 and I wasn't going to be able to migrate it to 6.1 first.

Using your (various) tips on file-backed VIOS devices, I was able migrate the LPAR to AIX 6.1 using the virtual optical device and the virtual media library containing the AIX 6.1 DVD iso images.

BTW, I was able to create the iso images using dd i.e.

dd if=/dev/cd0 of=/cg/AIX61DVD1.iso bs=1m

Keep the tips coming!


Hello Rob/Chris,

Any idea whether this VirtualOpticalDisk method could be used to do a VIOS migration from 1.5 to 2.1 in a dual VIOS setup. I have a CSM server at 5.3 which also acts as a NIM server and this CSM server could not yet be migrated to 6.1 to support VIOS 2.1 (with AIX 6.1 kernel)!


Hi Harsha,

I'm pretty sure that this is not an option for VIOS migration. A VIOS can't be the client of another VIOS.

Let's see if Rob has any experience to the contrary.



The documentation

states that you can use the HMC or the built in DVD drive for the VIOS migration. Hope that helps.


Hello Rob/Chris,

Thanks for your helpful comments.


I learned a few other techniques that we can all benefit from. For instance, in my VIO server, I tried creating a file-backed virtual disk (obviously on this test box I was using rootvg; if this were a production machine I'd create another volume group and use that instead):

Great read!

I also just read Chris' post on installing via mksysb ISO from a VIO Server FBO device.

I have a couple questions before I attempt an install of this fashion.

First, my mksysb was large enough that it resulted in multiple volumes after the mkcd was run. Will the install prompt for loading each successive volume in order?

Second, with an installation of this fashion, can the initial/source LPAR be up and running at the same time, or will I have the opportunity to change the IP address, hostname, etc. so there are no conflicts?

Thanks in advance!

Doug, you can use the mkdvd command for DVD-sized images. Still, if the mksysb goes over one ISO file, when you run the mksysb restore, on the console you will be asked to load CD (ISO image) number 2. You can log onto the VIO server and run:
unloadopt -vtd vtscsi1 (to "eject" cd 1), then
loadopt -vtd vtscsi -disk mksysb_2.iso

Then press enter on the console.

The network settings have to be done after the mksysb restore (unlike when you build using NIM). However, if you select Restore devices when going through the boot menus for the mksysb restore, you'll get all the original devices, including IP addresses etc. You should usually only recover devices when you're restoring to the same configuration on the same physical server as you backed up.

One last thing: a smaller mksysb is always more manageable. This may mean moving user-created file systems into other volume groups, or at least running mksysb with the -e flag and excluding directories using /etc/exclude.rootvg
I suspect you already know about this.


The comments to this entry are closed.