On Dec 1, 2006, at 10:54 AM, Dennis, Melburn IT7 wrote:
I have a user that has been testing out a TSM restore of a
fileserver in
case of a disaster, and he's been getting reports that out of the
471,871 files that were selected to be restored only 463,133 files
were
actually restored. The remaining 8,738 files are being skipped.
According to the dsmerror.log report, it is saying the the files
already
exist on the target server and were skipped for that reason. Now
how is
this possible if the user is restoring the files to an alternate
location (other than the original server) which is an empty drive?
TSM Server 5.3.3.1
TSM Client 5.3.4.0
Mel -
That's very scant, second-hand information...not enough to act on.
The server log or accounting file or evan Activity Log ANE mesages
will tell you whether or not there was perhaps an initial restore
attempt that was terminated and then reattempted, which would leave
some files there. If Unix, you can use 'ls -alc' to see when those
questioned files were actually established in the file system,
compared with the time period when the restoral was supposedly run.
If Unix, a df command should reflect an inode count which matches the
restored objects count.
Beyond that, pursue the details... What is the client type? What
was the full syntax of the restoral attempt? What is the type of the
skipped objects (files, directories, other)? What are the actual
error messages (which may turn up something in a TSM Support Page
search)?
Not that we don't implicitly trust users...
Richard Sims
