Seems like the Windows client ran into a Windows error code it wasn't
programmed to handle. See if there is a Windows Event Log entry for that
timestamp which may yield further perspective. Beyond that you may have to
contact TSM Support. To aid them in diagnosis, see if you can narrow down a
position in the file system where the problem is incited, by inspection of the
schedule log's progress; and see if it's repeatable by invoking backup on thus
the containing directory.
Richard Sims http://people.bu.edu/rbs/
On Apr 29, 2010, at 7:42 AM, Lee, Gary D. wrote:
> 04/29/2010 02:53:08 Return code 653 unknown
