• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 640
  • Last Modified:

installing a vioserver on a different hardware..


suppose I have a vioserver-IVM  installed on a blade (ps700 or js43) and the hardware crashed and it's changed to a new one and different like the original. As I have a mysysb backup on my nim server, I restored the mksysb image to the new blade but I didn't worked again or I wasn't able to get the vioserver running again. Finally I had to install again the vio. So my question is:

-How can I restore a vioserver from the nim with all lpars, mappings, etc etc to a new hardware? Is it possible?

NOTE: A part of mksysb backup in our vioservers-ivm we make a bkprofile backup to TSM.

  • 4
  • 3
1 Solution
Which way did you create the mksysb?

If you use "backupios" for this purpose you must keep in mind that
this command doesn't include profile data in the backup.

You wrote that you run "bkprofdata" and save the result to TSM, so after a successful mksysb restore
you must get the profile data back from TSM and run a "rstprofdata" against them.

Another important thing with "backupios" is that it doesn't save data needed for "recover devices".

This has the advantage that you can clone to any partition, but the disadvantage is that you would have to recreate your network setup and several more things (I don't have a complete lineup, sorry).

So it is indeed a good idea not only having "bkprofdata" at hand, but also "viosbr -backup", to be able to run "viosbr -restore" after the mksysb restore.

       viosbr -backup
       backs up all the device properties and the virtual devices
       configuration on the Virtual I/O Server. This includes information regarding logical devices,
       such as storage pools, file-backed storage pools, the virtual media repository, and PowerVM
       Active Memory Sharing (AMS) paging devices. It also includes the virtual devices, such as
       Etherchannel, shared Ethernet adapters (SEAs), virtual server adapters, and server virtual fibre
       channel (SVFC) adapters. Additionally, it includes the device attributes, such as the attributes
       for disks, optical devices, tape devices, fibre channel SCSI controllers, Ethernet
       adapters, Ethernet interfaces, and logical Host Ethernet Adapters (HEAs).

Additional IP addresses (besides the one you configured for net boot and restore) are lost and must be re-added.

The default location for viosbr output is /home/padmin/cfgbackups, the filename must be specified on the command line using the "-f" flag.
viosbr can also set up a cronjob on your behalf. See the manpage.

So only the combination of mksysb (backupios), viosbr and bkprofdata makes a full recovery possible.


sminfoAuthor Commented:
wmp, sorry the delay... one question..
I reinstalled  the vioserver from scratch and I saw the vio  kept some data somewhere like:
 lshwres -r virtualio --rsubtype eth --level lpar

Also it kept the slot I created some weeks ago.. does the vio saves information in the firmware?
Why if I installed from zero it ketp this data?
sminfoAuthor Commented:
So, reading your post again..

I don't use backupios, I make the mksysb from NIM server like other LPARs. It works because I have tested before but ONLY on the same hardware.

Must I have to use backupios or can O use mksysb method from NIM?

I have added viosbr to the same script backup-bkprofdata to have both on TSM.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Did you reinstall by booting just the IVM LPAR from mksysb? If so the LPAR settings from firmware will be reused, as opposed to booting the whole real machine from mksysb, where you will loose all LPARs and also the IVM LPAR settings.

As for the different hardware: If its different in number and location of slots you will have orphaned mappings, which you will have to redo.

Sorry, I'm far away from my machines so I can't give more detail right now.

sminfoAuthor Commented:
No problem at all wmp.

OK, I reinstalled the VIO from DVD.  But once it finished it loads the data from the original vioserver. It's something strange, don't you think? I don't know if I had to format the hdisk0 before beginning to install again.

BTW, I got lpar2rrd working and it's really nice. :-)

To close the post, are my backup method right?

1- Backup the vio from NIM server using mksysb. ( like I do with others AIX)
2- backup with bkprofdata and viosbr to TSM.

In the 1) I don't know if I MUST use the backupios from the vio OR use the was I do from NIM?
I assume that /usr/ios is left unchanged when installing from DVD without specifying "Complete Overwrite".

1) You can use NIM as with your other machines, no problem.
backupios is meant for people who either don't want to break out of IOSCLI or people who don't have a NIM server - the mksysb created via backupios can be restored using the NIMOL (NIM on Linux) which is part of the HMC. But trying this is just a hard job - I never got it to work nicely.

2) bkprofdata and viosbr are useful for restoring the VIOS setup alone, without the need of restoring the full mksysb - and for installing on different hardware, as we could see.

lpar2rrd is cool, isn't it? I really like it.
It's sad that Pavel Hampl stopped its development.
Moreover, since a few weeks he's giving professional support only against a paid maintenance contract. Money rules.


sminfoAuthor Commented:
ok wmp..

lpar2rrd is really good tool.. I installed on a test environment and show to one of our client and he was amazed because he didn't know the use of CPU after the migration of lpars  to the new hardware on  blades js43 and ps700. :-)


Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now