ADSM-L

Re: [ADSM-L] NFS mount backup failing after upgrading to 6.2.2

2011-01-06 15:12:24
Subject: Re: [ADSM-L] NFS mount backup failing after upgrading to 6.2.2
From: Graham Stewart <graham.stewart AT UTORONTO DOT CA>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 6 Jan 2011 15:08:45 -0500
We've seen the same problem with the Linux 6.2.2.0 client (with the
server(s) at these levels: 6.2.2.0, 6.2.1.0, 5.5.1.1). Same results with
64 bit and 32 client and with SSL enabled or not.

The client reports this from dsmc:

tsm> i /some/nfsmounted/filesystem

Incremental backup of volume '/some/nfsmounted/filesystem'
ANS1228E Sending of object '/some/nfsmounted/filesystem' failed
ANS4021E Error processing '/some/nfsmounted/filesystem': file system not
ready
ANS1802E Incremental backup of '/some/nfsmounted/filesystem' finished
with 1 failure

... and this in the error log:

01/06/2011 14:54:33 ANS3417W nfsd: A system call psCollectMountTableInfo
failed with code 6201 - Invalid server name. Need format 'server:/volume'.

01/06/2011 14:54:33 ANS3402W psGetHostName(): A system call
gethostbyaddr() failed with code 1.
01/06/2011 14:54:33 ANS5250E An unexpected error was encountered.
   TSM function name : nsGetNasVolumeInfo():
   TSM function      : dmMapNfsVolume() failed to map remote volume for
path: </some/nfsmounted/filesystem>.

   TSM return code   : 6201
   TSM file          : snapcommon.cpp (378)
01/06/2011 14:54:34 ANS1228E Sending of object
'/some/nfsmounted/filesystem/*' failed
01/06/2011 14:54:34 ANS4021E Error processing
'/some/nfsmounted/filesystem/*': file system not ready
01/06/2011 14:54:34 ANS1802E Incremental backup of
'/some/nfsmounted/filesystem/*' finished with 1 failure


With everything identical (dsm.sys, dsm.opt, NFS mount parameters,
paths) and the client at 6.2.1.1 the NFS backups work perfectly.

Haven't got around to contacting IBM yet.

--
Graham Stewart          graham.stewart AT utoronto DOT ca  416-550-2806
Network and Storage Services Manager, Information Technology Services
University of Toronto Libraries
130 St. George Street
Toronto, Ontario, Canada M5S 1A5




On 11-01-06 02:53 PM, Zoltan Forray/AC/VCU wrote:
FWIW, further testing narrows the problem down to 6.2.2.0 specifically. We
went back to 6.2.1.1 and it works fine from that level and older.
Zoltan Forray
TSM Software&  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html



From:
Richard Sims<rbs AT BU DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
01/06/2011 12:13 PM
Subject:
Re: [ADSM-L] NFS mount backup failing after upgrading to 6.2.2
Sent by:
"ADSM: Dist Stor Manager"<ADSM-L AT VM.MARIST DOT EDU>



Hi, Zoltan -

This sounds like a DNS lookup failure to me, as though the client is
attempting to verify some aspect of the mount.
Naturally, the programmer didn't bother including the lookup name in the
error message, to make pursuit easier.  You may be able to deduce that
based upon mount inspection.

     Richard Sims

On Jan 6, 2011, at 11:32 AM, Zoltan Forray/AC/VCU wrote:

We have been updating Linux clients to 6.2.2.0 due to the recently
reported vulnerabilities.

One client that has been backing an NFS mount just with 6.1, is now
failing.  We get the following errors:

01/06/2011 10:22:30 ANS3402W psGetHostName(): A system call
gethostbyaddr() failed with code 1.
01/06/2011 10:22:30 ANS5250E An unexpected error was encountered.
    TSM function name : nsGetNasVolumeInfo():
    TSM function      : dmMapNfsVolume() failed to map remote volume for
path:</var/echo360>.
...