[cowens]

Hello
When doing a mksysb backup of a client from the NIM master at the end of the backup I reciece a error mesage as shown below:
# nim -o define -t mksysb -a server=master -a location=/nim_mksysbs/jdistjunx958 -a mksysb_flags=-e -a mk_image=yes -a sou>
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 1223668 (1195 MB) Available = 4903260 (4789 MB)

Creating information file (/image.data) for rootvg..
Creating list of files to back up..
Backing up 33770 files..............................
31893 of 33770 files (94%)
33770 of 33770 files (100%)
0512-038 savevg: Backup Completed Successfully.
0042-001 nim: processing error encountered on "master":
0042-124 c_ch_nfsexp: NFS option sec=sys is NOT supported
rc=0
0042-124 c_ch_nfsexp: NFS option sec=sys is NOT supported

Is there somting wrong with how my export is setup. The backup seems to finish okay and I have executed a Bare Metal Restore and it work ok. Any suggests would be appreciated.

[Mark Taylor]

This can happen if you have NFS exported a filesystem/directory that is also a NIM resource. Un-export the filesystem/directory and try again to see if the error still exists.

HTH
Mark Taylor

[cowens]

Thanks Mark
I discovered this out late yesterday. Being new to NIM, I wasn't aware of all the little thing it will do on it own. Then remove it after use.


Thanks for the reply.

[snakernetb]

I was wondering if this will actually keep from doing a mksysb restore? I noticed that it said that you had completed one. Mine fails eveytime! It boots the kernel on the remote machine and then just reboots. I have all of my resources setup correctly, and I see where it is making mounts by using showmount -a. This is really causing me issues. I am trying to set up a NIM environment that was never used. It has just been sitting for a year. But the last admin set it up to run all kinds of scripts that use NFS. I was told this wasn't Prod, then when I started changing things, other machines started throwing errors and hanging up. Very messy. But I am getting the same NFS error codes, even when I compare my mksysb to my SPOT.

[cowens]

What I had done was setup a nfs mount to the box from the NIM master to the box I was trying to backup. I didn't realize at the time was that NIM will create the mount then remove it once it was finished. What I beleive was happening was, after the backup completed it was trying to remove the mount but couldn't. I not sure what is happening with your environment.