[CSCoutts]

We have created a dual VIO configuration on a P570 Server.
There are both internal SCSI interfaces and FC cards configured to both VIO servers.
The objective is to take existing LPARS with dedicated resources and create a NIM backup then restore the LPAR as a VIO Client. As dedicated resource LPARS, they have SCSI cards with mirrored rootvg's.
Since they are only using approx 12GB of the space and low CPU/Network resource utilization, they are perfect candidates.
Using the IBM Best Practices, we wanted to restore the NIM backup to a 20GB rootvg on the FC/SAN.
When we get to the point of restoring from the NIM Backup, we are told that the Disk allocation is too small. We try changing the parms to tell it to restore anyways, but it continually tells us the rootvg does not have enough space.
1) Using a NIM backup of 12GB of used space, can we be restoring into a more reasonable sized rootvg of 20GB on the SAN/FC?
2) Since the NIM backup was created from an internal mirrored disk volume does it have to be restored to the same?
3) Are there any special considerations for restoring a NIM Backup from a non virtual LPAR to a Virtual I/O Client?

Let me know, thanks.

[gbarth]

can you not -

1) copy the image.data from your source LPAR to you NIM master.
2) make required changes to this file to ensure this will fit etc. on your target environment
3) define this amended file as a NIM image_data resource
4) include this NIM resource when setting up the installation on the NIM master

[CSCoutts]

Excellent suggestions, Thanks.
We were able to step back and redo the NIM backup with File Mapping turned off and then went into NIM server and update the file.
Once this was completed, we were able to restore the LPAR into a right sized LPAR.
After moving the initial candidate into the Virtual World, we continued with the next candidates.