Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NIM mksysb Backup Problem 1

Status
Not open for further replies.

khalidaaa

Technical User
Jan 19, 2006
2,323
BH
Hi all,

I have a problem with NIM mksysb backup! I do a weekly mksysb backup of my LPARs to a NIM master disk (then do a whole mksysb of this NIM master into tape that will be taken off-site) Last few weeks I been recieving this failure message of my test LPAR:

Code:
Creating information file (/image.data) for rootvg.

Creating list of files to back up ...
Backing up 32315 files
0512-005 savevg: Backup Completed.
        The backup command completed with errors.
        The messages displayed on Standard Error contained additional
        information.
0042-001 nim: processing error encountered on "master":
   0042-001 m_mkbosi: processing error encountered on "test2":
   warning: 0042-175 c_mkbosi: An unexpected result was returned by the
        "/usr/sbin/mount" command:
       
nfsmnthelp: nimaster: Error -1 occurred.
mount: giving up on:
        nimaster:/export/images
Error -1 occurred.
cannot open /tmp/462872.mnt0/test2_20070505: Read-only file system
Please mount volume 1 on /tmp/462872.mnt0/test2_20070505
... and press Enter to continue


test2 System backup ended UN-SUCCESSFULLY at Sat May  5 08:30:50 SAUST 2007.

I have a little experience with NIM and i'm not sure what's wrong! But i can feel that it is something simple that i'm missing!

Any help is appreciated.

Thanks

Regards,
Khalid
 
Khalid
it looks like your client test2 cannot mount via nfs
/export/images from the nimmaster

log on as root on test2 and issue
mount nimmaster:/export/images
likely as not it will not mount

either the filesystem was not exported on the nimmaster OR
the client cannnot do reverse name look-up

usually, try to resolve the NFS mount problem sometimes
going so far as placeing the nimmaster into the clients /etc/host file and then using a /etc/netsvc.conf
with 1 line
hosts=local,bind4

hope that this helps
 
Thanks masrolyat for your helpful comment!

Now the message changed to this!?!?

Code:
Creating information file (/image.data) for rootvg.

Creating list of files to back up ....
Backing up 32309 files
0512-005 savevg: Backup Completed.
        The backup command completed with errors.
        The messages displayed on Standard Error contained additional
        information.
0042-001 nim: processing error encountered on "master":
   0042-001 m_mkbosi: processing error encountered on "test2":
   cannot open /tmp/532586.mnt0/test2_20070507: Read-only file system
Please mount volume 1 on /tmp/532586.mnt0/test2_20070507
... and press Enter to continue


test2 System backup ended UN-SUCCESSFULLY at Mon May  7 21:55:10 SAUST 2007.

But it appears that the comment on changing the /etc/netsvc.conf worked on another test lpar that had similar (but not the same) error!

Just to add to this problem! There is a log that being updated while i'm trying to backup the lpar! it is /tmp/clstrmgr.debug with the following errors!

Code:
Mon May  7 21:52:41 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:52:56 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:53:11 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:53:26 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:53:41 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:53:56 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:54:11 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:54:26 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:54:41 DoMainLoop: smuxp_doit returned -1
Mon May  7 21:54:56 DoMainLoop: smuxp_doit returned -1

test2 is just a cluster node running hacmp with test1 (test1 was backuped successfully) but not test2!

Regards,
Khalid
 
Khalid,
Do you want to backup /tmp ?
If not use the "-e" flag with the savevg/mksysb and exclude it.
cheers
Benno

...it really does get worse than this !!
 
Thanks Benno.

I just did what you told me but the problem is still there!

Code:
0042-001 nim: processing error encountered on "master":
   warning: 0042-175 c_mkbosi: An unexpected result was returned by the
        "/usr/sbin/mount" command:
        
nfsmnthelp: nimaster: Error -1 occurred.
mount: giving up on:
        nimaster:/export/images
Error -1 occurred.
rc=175
0042-175 c_mkbosi: An unexpected result was returned by the "/usr/sbin/mount" command:
nfsmnthelp: nimaster: Error -1 occurred.
mount: giving up on:
        nimaster:/export/images
Error -1 occurred.

rc=1
0042-001 m_mkbosi: processing error encountered on "master":
   0042-175 c_getlevel: An unexpected result was returned by the "/usr/lpp/bos.sysmgt/nim/methods/c_stat" command:

0042-154 c_stat: the file or directory "/export/images/test2_20070509" does not exist


test2 System backup ended UN-SUCCESSFULLY at Wed May  9 13:57:48 SAUST 2007.

Any more suggestions?

Regards,
Khalid
 
masrolyat!!! You were absolutely right! I think it is a reverse lookup problem!

for this test2 host, i'm using the local hosts file but for some reason it doesn't resolve the IP when i do nslookup from the nim master!

Code:
# nslookup
Default Server:  cdc01.company.to
Address:  129.168.1.200

> test2
Server:  cdc01.company.to
Address:  129.168.1.200

*** cdc01.company.to can't find test2:Server failed
>

It should be something simple! I know if i put the name in the DNS it will work but i don't want to!

masrolyat star deserved!

Regards,
Khalid
 
Well, I don't know what i was thinking! That's right for the nslookup coz it will query the DNS that is located in the /etc/resolv.conf! So it is fine!

When i use the host command, it returns the correct IP from the /etc/hosts file!

Code:
# host test2
test2 is 129.168.1.222,  Aliases:   test2.company.to

# host 129.168.1.222
test2 is 129.168.1.222,  Aliases:   test2.company.to

Do I have to define my server in the DNS for this to work?! strange! I thought i could do this without using the DNS!?!

Any thoughts?

Regards,
Khalid
 
I don't know where is every body! I used to have alot of helpers! :)

Any way, Just to update this problem. I tried to stop the cluster and take the backup while the cluster was down and it was successful!?!?

The cluster is using IPAT via aliasing. So could that be because of the service IP address on that cluster? I'm registering the Machine on the NIM master using the persistance IP address of each node of the cluster so it shouldn't matter whether the cluster is up or down!

Any idea?

Regards,
Khalid
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top