Joe,
Testing the V4.1 Mac client we came up against a similar problem
- the client established then closed the connection. Tivoli logged
this under an already-existant APAR IC27847 which states:
" Data backed up with the 3.1 client can not be restored with the
3.7 client. Client reports 'Error reading data.' With a
Return code of 268435556."
But the real problem was that the data channel could not handle a
tcp_ip WAIT signal when the server tried to restore from tape.
Anyway, the problem was corrected in the lates 4.1 Patch for Mac
4.1.2.15 - IP22153_15.hqx. It doesn't look as though this was
corrected at 3.7 though :(.
Regards
Ian Smith
--------------------------------------------------------------------------------
Ian Smith - HFS Backup / Archive Services
Oxford University Computing Services
--------------------------------------------------------------------------------
>MIME-Version: 1.0
>Date: Thu, 10 May 2001 17:53:03 -0700
>From: Joe Faracchio <[EMAIL PROTECTED]>
>Subject: mac client restores failing + mountret
>Comments: cc: Joe Faracchio <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>
>I just had a weird problem brought to my attention and it got weirder.
>I plan to call this in to IBM support tomorrow. ASAP.
>
>A user called to say he was trying to do a restore on a Mac and it
>failed with connecting to server. Suspecting the mac restore problem
>I said try a new folder backup to see if you can connect. It worked.
>
>I was about to say: sounds like the bad mac client ... upgrad ..
>When they said that a subsequent restore attempt started to work.
>Kinda. It was looping or restore requests giving me 6 mount requests
>in the queue.
>
>I changed mountret to something greater than zero and it restored the
>file!
>
>This shouldn't be! That you can have mountret at zero and it causes
>all restore requests to fail on timeout of mount wait.
>
>There's more than one problem here? Any experience like this?
>Suggestions?
>
>thanks .... joe.f.
>
>
>Joseph A Faracchio, Systems Programmer, UC Berkeley
>Private mail on any topic should be directed to :
> [EMAIL PROTECTED]
