Date: 28-10-20  Time: 14:51 PM

Author Topic: VIO mksysb Image wth NIM  (Read 12429 times)

0 Members and 1 Guest are viewing this topic.


  • Registered
  • *
  • Posts: 1
  • Karma: +0/-0
VIO mksysb Image wth NIM
« on: April 23, 2009, 09:44:42 AM »

In the end of the 2008 we changed our strategie and moved our dedicated server to 2 p570 with vio - boot from san - virtual fcs etc. I had a lot of new problems with the vio 2.1.
Now every server is running .... :) For the LPAR Backup I still can use a cronjob, a script which makes a mksysb on a nfs share on the nim server.

Now i've got the problem to backup the VIO. Is it also possible to backup the vio server with a cronjob on the nim or is this a bad idea? I didn't find a solution on the redbook.

Has someone a good experience to make VIO Backup?

Thank you


  • Administrator
  • Hero Member
  • *****
  • Posts: 1268
  • Karma: +0/-0
Re: VIO mksysb Image wth NIM
« Reply #1 on: April 23, 2009, 11:57:00 AM »
I found a document that addresses this, and I'll do an update later.

Note: it is possible to run oem_remote_management to make a vios an official nim client and you should be able to use the nim master to make a nim_mksysb in a normal way - however, a vios requires a specific spot (that is made from the mksysb image). BUT!! this is not a solution path that is acceptable to IBM support (in case somethings goes wrong).

IBM support "requires" that you use the padmin command: backupios and create a resources.tar file that has the resources needed to restore the vios from tape, ...., and nim.

An except from the link below:
Backing up the Virtual I/O Server to a remote file system by creating a nim_resources.tar file

The nim_resources.tar file contains all the necessary resources to restore the Virtual I/O Server, including the mksysb image, the file, the network boot image, and SPOT resource.
The NFS export should allow root access to the Virtual I/O Server, otherwise the backup will fail with permission errors.

To backup the Virtual I/O Server to a filesystem, the following steps must be performed

As we no longer permit clickable URL's you will have to copy this to your browser: (Word doc)